Issue #20981 has been updated by Joe Wagner.
User stories… Must support initially: As Vatsan, a generalist sys admin, I want each Puppet run I trigger to have a unique ID, So that anyone on my team can later look up the run results using that ID. As Vatsan, I want to search of a Puppet run unique ID and retrieve the corresponding Puppet run results, So that I can check on a specific Puppet run and nothing else. As Gustav, a team manager, I want to locate the results of a Puppet run across a set of nodes by browsing Puppet runs that were initiated at some point between during a period of time that I've entered, So I can identify the correct Puppet run and review the push my team made if I only know the window of time in which it was triggered. Should support initially: As Vatsan, I want to add a note regarding the puppet execution I'm about to trigger, so I can provide my team with important meta information regarding the run. As Vatsan, I want to search Puppet runs by meta keyword, So that I can filter Puppet runs to a set that matches those specific meta keywords and select the Puppet run I'm interested in reviewing. As Vatsan, I want to see meta information when viewing a Puppet run's results, So that I can get additional context regarding the Puppet run. As Vatsan, I want to search on a node, class, resource, or fact that I know was involved in a Puppet run I'm interested in, So that I can filter Puppet runs to a set that correspond to those entities and select the Puppet run I'm interested in reviewing. Could support initially (should eventually): As Gustav, I want to see who triggered a Puppet run, So that I know who to talk to should I have questions or concerns regarding that run. As Gustav, I want to search Puppet runs by username, So that I can see which Puppet runs were triggered by a particular team member. ---------------------------------------- Feature #20981: Provide a mechanism to uniquely identify each agent run https://projects.puppetlabs.com/issues/20981#change-92081 * Author: eric sorenson * Status: Unreviewed * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- It's a little surprising there's not already a feature request about this, but I looked and couldn't find one. It should be possible to uniquely identify a Puppet agent run to trace actions through our wider ecosystem. For example, as a puppet administrator I would like to trigger puppet execution on a set of nodes using mcollective, then correlate any actions that happened by viewing their reports. -- 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 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-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
