With Pillarstack, files are only searched relative to the directory of the stack.cfg file.
GitStack now supports defining multiple git pillar repos as pillarstack targets, but they are processed sequentially, as distinct invocation/passes.
This feature requests the option to include other pillar directories into search path used in a single stack.cfg pass.
I'd like to be able to break pillar configuration into multiple git repos that overlay on each other into a single tree that could be passed to pillarstack.
This would allow files in different directory trees to be processed by precedence within the same pass.
This would allow for greater modularity, which would support greater re-use.
With Pillarstack, files are only searched relative to the directory of the
stack.cfgfile.GitStack now supports defining multiple git pillar repos as pillarstack targets, but they are processed sequentially, as distinct invocation/passes.
This feature requests the option to include other pillar directories into search path used in a single
stack.cfgpass.I'd like to be able to break pillar configuration into multiple git repos that overlay on each other into a single tree that could be passed to pillarstack.
This would allow files in different directory trees to be processed by precedence within the same pass.
This would allow for greater modularity, which would support greater re-use.