Jira (PUP-6144) No-op runs cache catalogs, which are later enforced

[Reid Vandewiele (JIRA)]

Title: Message Title

Reid Vandewiele created an issue   Puppet / PUP-6144 No-op runs cache catalogs, which are later enforced Issue Type: Bug Assignee: Unassigned Created: 2016/04/08 4:26 PM Priority: Normal Reporter: Reid Vandewiele In the Direct Puppet run model agents retrieve a catalog when requested to do so then continuously enforce that catalog at a regular interval. A common pattern to test and see what changes Puppet _would_make if given a particular version of code has been to run something like puppet agent -t --noop --environment test_feature This is now a problem with Direct Puppet, because a catalog the user does not want to enforce (one they retrieved with a "safe" no-op run) will, possibly unbeknownst to them, be enforced on this node in about 30 minutes. Because it is now the cached catalog, which will be enforced continuously. A no-op run is no longer safe. Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.