Hi all, I am trying to proof of concept an automated install of Puppet Enterprise using policy based autosign.
I have read the following documents and understand what I need to do http://docs.puppetlabs.com/puppet/latest/reference/ssl_autosign.html#policy-based-autosigning http://docs.puppetlabs.com/puppet/latest/reference/ssl_attributes_extensions.html I would like to include some vmware attributes as extensions for verification. These attributes are identified by facter. The problem arises in that the automated installer creates and attempts to contact the master as part of the installer operation. I need to interrupt the installer and update the csr_attributes.yaml file prior to the CSR is created. I can't create the file prior to PE install as I need facter. Is there a way to break this chicken/egg situation? Cheers Adam -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/009b3aea-aaff-48f0-9f37-cb2286d41a76%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
