From 8eabeafd9531e53ebfec9d256662328d3951653e Mon Sep 17 00:00:00 2001 From: "Salvador E. Tropea" Date: Wed, 17 May 2023 10:11:34 -0300 Subject: [PATCH] [DOCs] Chages propagated to README.in - Applied e8e8608a950a3384d13ecc63ab581735ccfdb4a4 --- docs/README.in | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/README.in b/docs/README.in index 1b695049..41a8fdd2 100644 --- a/docs/README.in +++ b/docs/README.in @@ -1256,6 +1256,15 @@ Another important detail is that global options that are lists gets the values m The last set of values found is inserted at the beginning of the list. You can collect filters for all the imported global sections. +Imports are processed recursively: An `import` section in an imported +file is also processed (so importing `A.yaml` that imports `B.yaml` +effectively imports both). + +If an import filename is a relative path, it is resolved relative to the +config file that contains the import (so it works regardless of the +working directory and, in case of recursive imports, of where top-level +config lives). + It's recommended to always use some file extension in the *FILE_CONTAINING_THE_YAML_DEFINITIONS* name. If you don't use any file extension and you use a relative path this name could be confused with an internal template. See [Importing internal templates](#importing-internal-templates).