The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
Puppet should natively support bootstrapping from scratch.
|Status:||Needs More Information||Start date:||05/22/2010|
|Affected Puppet version:||0.25.4||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
Automatically provisioning puppet clients could be really simple if we had these features.
options: —bootstrap (defaults to no) —bootstrap_environment (defaults to bootstrap)
If these options are on, the client connects to the puppet server and requests a catalog for the bootstrap_environment. If that completes successfully, then the client does another run with whatever settings, plugins, config files have been placed down by the bootstrap run.
#4 Updated by Nigel Kersten almost 5 years ago
I kind of hate it too.
What if instead we had these features:
- server can set environment of client via node classifier
- manifests can contain an instruction to the client to issue another puppet run after the current one has succeeded
Then we wouldn’t need to deal with this hacky method.