Are there config file includes (do config file attributes get parsed when they're in yaml)

[ridilculous]

Maybe this is already possible and i just don't know how to use it.

Is there a way for a config file to include another config file, i.e. split and reuse config files partially?

Multiple config files can be configured and they are recognized when they're all passed through command line, but whatever i try, i cannot specify the same or another config file within a existing config file.

Here's what i tried:

Parser fragment:

parser.add("-cfg", "--configFile", is_config_file=True)
parser.add("-cfg2", "--configFile2", is_config_file=True)

• Works, i.e. reads both config files:
  test.py --configFile "test.yaml" --configFile2 "test2.yaml"

• Doesn't read "test2.yaml":
  test.py --configFile "test.yaml"
  test.yaml:
  configFile: "test2.yaml"

• Also doesn't read "test2.yaml":
  test.py --configFile "test.yaml"
  test.yaml:
  configFile2: "test2.yaml"

[kyduff]

I am also looking for the same functionality. Perhaps support for the !includes directive is a worthy feature? Something as in this stackoverflow example could be very useful.

[bw2]

A PR to add this would be appreciated.

[tbooth]

A PR to add this would be appreciated.

There is #261 which essentially does implement this, but was rejected as too complicated.

I have worked up an alternative solution where adding a generic tweak_value() hook to the parser classes allows for minimal subclassing by the user of the module, and demonstrated how this can make a recursive (ie. allowing a config file to be named within a config file) parser.

https://github.com/tbooth/ConfigArgParse/blob/devel/tests/test_config_parser_subclasses.py

If there is enough enthusiasm, hopefully we can get this feature merged.

[bw2]

Closed due to inactivity. If this remains an issue, please reopen or recreate it.