Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pupistry and Masterful Puppet #11

Open
ljohnston opened this issue Jan 12, 2016 · 1 comment
Open

Pupistry and Masterful Puppet #11

ljohnston opened this issue Jan 12, 2016 · 1 comment

Comments

@ljohnston
Copy link
Contributor

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

@jethrocarr
Copy link
Owner

hi Lance,

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.

regards,
Jethro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants