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
Do you have any thoughts with regard to using pupistry and masterful puppet on nodes? I'm thinking about a situation where the ops team is managing masterful puppet, manifests, etc. for corporate level stuff across the enterprise, while dev teams use pupistry for their application-specific deployment and configuration to those same boxes?
Thanks,
Lance
The text was updated successfully, but these errors were encountered:
It's entirely possible, I could take many of the modules in $dayjob's (massive) Puppet masterful environment and they would just work. I've been considering using Pupistry for things like Vagrant or Docker builds for some time.
Really the only thing that won't work via Pupistry is anything reliant on exported configuration (PuppetDB) and any dynamic Hiera backends (ie not file-based) could get tricky.
Do you have any thoughts with regard to using pupistry
andmasterful puppet on nodes? I'm thinking about a situation where the ops team is managing masterful puppet, manifests, etc. for corporate level stuff across the enterprise, while dev teams use pupistry for their application-specific deployment and configuration to those same boxes?Thanks,
Lance
The text was updated successfully, but these errors were encountered: