Jira (PUP-4716) Add option to pass transaction_uuid into agent

[David Lutterkort (JIRA)]

David Lutterkort created an issue

Puppet / PUP-4716 Add option to pass transaction_uuid into agent Issue Type: Task Assignee: Unassigned Created: 2015/06/09 1:40 PM Priority: Normal Reporter: David Lutterkort In some circumstances, e.g. when another tool kicks of runs of the Puppet agent, it would be very useful to predetermine the transaction_uuid and pass it to the agent on the command line, something like puppet agent -otv --transaction-uuid dead-beef Clearly, this only makes sense for onetime runs, not when starting the agent as a daemon. Add Comment

This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[David Lutterkort (JIRA)]

David Lutterkort updated an issue

Puppet / PUP-4716 Add option to pass transaction_uuid into agent

Change By: David Lutterkort Scrum Team: Client Platform

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-4716

Re: Add option to pass transaction_uuid into agent From PUP-6903, the transaction_uuid should also end up in last_summary.yaml and be queryable via puppetdb (if it isn't already).

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-4716

Add option to pass transaction_uuid into agent

Change By: Josh Cooper Labels: triaged

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper assigned an issue to Alex Dreyer

Puppet / PUP-4716 Add option to pass transaction_uuid into agent

Change By: Josh Cooper Assignee: Alex Dreyer

Add Comment

[Alex Dreyer (JIRA)]

Alex Dreyer commented on PUP-4716

Re: Add option to pass transaction_uuid into agent No we don't need to pass this through the CLI.

Add Comment

[R.I.Pienaar (JIRA)]

R.I.Pienaar commented on PUP-4716

Re: Add option to pass transaction_uuid into agent

Even if this goes into the last run summary and reports and do get stored - you still won't know what it was when triggering a run - you only find out at the end So async tools like mco will still not be able to know or find reports related to a run they triggered. Being able to pass a id explicitly means they can tell users to wait for a specific report Imagine the user request a splayed run via mco, is there another way to know in advance what this id will be when the run eventually starts?

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper assigned an issue to Unassigned

Puppet / PUP-4716

Add option to pass transaction_uuid into agent

Change By: Josh Cooper Assignee: Alex Dreyer

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-4716

Re: Add option to pass transaction_uuid into agent R.I.Pienaar ah right, I forgot about mco and the linked ticket. Makes sense to add that.

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-4716

Add option to pass transaction_uuid into agent

Change By: Josh Cooper Issue Type: Task New Feature

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-4716 Add option to pass transaction_uuid into agent

Change By: Josh Cooper Team: Coremunity

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-4716 Add option to pass transaction_uuid into agent

Change By: Josh Cooper Labels: beginner

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-4716 Add option to pass transaction_uuid into agent

Change By: Josh Cooper Labels: beginner help_wanted

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-4716 Add option to pass transaction_uuid into agent

Change By: Josh Cooper Labels: Easy beginner help_wanted

Add Comment

This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)