You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have windows and/or linux node sets included with modules when they support the given platform. For Example, It doesn't make sense to have linux node sets with a module that will only ever work on windows and it's not really feasable and/or maintainable to add the exclusion of all the nodesets to the module's .sync.yaml. I propose we do the following which is what puppetlabs is currently doing in their modulesync configs
It is a good idea to clean this up and only apply nodesets that actually work. I'm not sure about the best way to do this. My main concern is described in #187. The puppetlabs approach would add another list of modules that we need to maintain.
It would be nice to have windows and/or linux node sets included with modules when they support the given platform. For Example, It doesn't make sense to have linux node sets with a module that will only ever work on windows and it's not really feasable and/or maintainable to add the exclusion of all the nodesets to the module's .sync.yaml. I propose we do the following which is what puppetlabs is currently doing in their modulesync configs
https://github.com/puppetlabs/modulesync_configs/blob/d1f5f9caf0607e707eeed4e95f6a957e6dcaa8df/config_defaults.yml#L1-L46
The text was updated successfully, but these errors were encountered: