Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
Dumpling
-
2
-
FF 2017-05-30
-
New Feature
-
Puppet now accepts an arbitrary string as a Job identifier via {{--job-id}} that is used in catalog requests and reports.
-
Needs Assessment
Description
In order to actually thread job-id from orchestrator through the agent to PuppetDB, we need to have a facility to provide the job-id to the agent. As of PUP-7149, the code exists internally in puppet to handle job-id, but there's no way to pass it in from the outside. That ticket was contingent on a refactor of the way pxp-agent interfaces with puppet to start using the API instead of the command line. That work is deferred due to complexity, so the revised solution is to just provide a flag to set job-id on the command line.