I have a requirement where I want a Fact to be stored in PuppetDB during the manifest run and not during the initial fact gathering phase.
I know I can, in my manifests, create a file in /etc/facter/facts.d or I can write a Ruby script that will then be distributed by plugin sync. But both of these methods will only publish the fact during the initial phase of the puppet agent run. What I want to be able to do is set a fact during the manifest run portion that will then be stored in the PuppetDB without an additional puppet run. For example I'm wanting to use it to create a SSH key for the system, then to immediately publish this ssh_root_key fact. But given the way it works at the moment it would only occur during the initial phase of the puppet run, so would require two runs before that fact was available and ready for other servers to pick up using puppetdbquery. Does anyone know if this can be forced in some way? -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
