Bolt should use a configuration inheritance model similar to the one used by 'git' about bolt HOT 3 CLOSED

@trevor-vaughan I think Alex has already talked to you about this, but just for visibility: There are some other features we'd like to add around this before implementing it so that users aren't blindsided by having configuration applied that they aren't sure where it's coming from (like a global config). We'll leave this open since long term we plan to address it, but we don't have immediate plans or fixing.

https://tickets.puppetlabs.com/browse/BOLT-795

from bolt.

@lucywyman fwiw, I have the same request as @trevor-vaughan. I want to be able to commit a bolt.yaml to my e.g. control-repo in Puppet, to capture project-level configuration settings. However, I can't commit user-level configuration for ssh, winrm, and so forth to this file.

I need configuration stacking in order to use Bolt on a team level rather than an individual level.

from bolt.

👍

The winner-takes-all nature of bolt.yaml files seems unusually restrictive when both users and projects can have good reasons to define their own settings. This behavior will seem even stranger if system configuration files are implemented for #759.

As things stand, it doesn't make much sense to invest important settings in ~/.puppetlabs/bolt/bolt.yaml, because none of them will work from any project directory—even if the only thing the directory's settings do is rename site-modules/.

FWIW, there have recently been similar requests in the puppetcommunity Slack:

• https://puppetcommunity.slack.com/archives/C7GP57T50/p1572033515064900
• https://app.slack.com/client/T0AQJ2CTU/C7GP57T50/thread/C7GP57T50-1571323080.293400
• https://puppetcommunity.slack.com/archives/C7GP57T50/p1571212261234100

from bolt.