Issue #14311 has been updated by Haw Loeung.
Hi Kelsey, Kelsey Hightower wrote: > Haw, > > In order to help us make a better decision on accepting this, it would help > if you provided a use case. What are you trying to accomplish in your postrun > script? Why would a custom [report > processor](http://docs.puppetlabs.com/guides/reporting.html#processing-reports) > not work for you? > First of all, thank you for replying. Our current set up is that we have a live/production environment and multiple environments for each user to play and test with (e.g. hloeung, user2, user3, ...). Developers are able to apply changes on certain nodes, test, make sure it all works before these changes are then merged into the live/production environment and rolled out across the board. We also have directories such as /etc which are bazaar repositories to track changes. When the puppet run completes and adds new configuration files and such in these directories, the postrun script automatically commits them with a generic message such as "puppet auto-commit". What I would like, is to add more information to the generic auto-commit messages including the environment and the actual catalog number as provided by the puppet master (which is running on different nodes). For example, it would look like this: r100 - "puppet auto-commit hloeung r5001" r101 - "puppet auto-commit live r4980" r102 - "puppet auto-commit hloeung r5002" r103 - "puppet auto-commit user2 r4981" ... Currently, the environment is made available in the special variable $environment, but I would also like to see the $catalog.version (provided by the puppet master) made available somehow so I could pass this as an argument to the postrun script. I've tried passing last_run_summary.yaml which has the catalog.version as "config_version" but that is updated _after_ the postrun script is executed so therefore providing the catalog.version from the last run... which is incorrect. ---------------------------------------- Feature #14311: Expose catalog version https://projects.puppetlabs.com/issues/14311#change-62555 Author: Haw Loeung Status: Needs More Information Priority: Normal Assignee: Haw Loeung Category: Target version: Affected Puppet version: Keywords: Branch: Hi, Would it be possible to expose the catalog version so that something like the following in the puppet.conf would work? postrun_command=/usr/local/sbin/postrun.sh $environment $catalog.version I've tried parsing the last_run_summary.yaml file but that is only updated *after* postrun is executed. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
