Jira (PUP-11023) Make trlinkin-noop a fully supported feature

[Reid Vandewiele (Jira)]

Title: Message Title

Reid Vandewiele created an issue   Puppet / PUP-11023 Make trlinkin-noop a fully supported feature Issue Type: New Feature Assignee: Unassigned Created: 2021/04/07 10:57 AM Priority: Normal Reporter: Reid Vandewiele The Forge module trlinkin-noop has been used heavily by customers for years. However, it is extremely finicky to use due to a bit of a hack of an implementation. This makes it difficult to base higher-level use cases on. See reidmv-change_risk, which provides some customers with an ability to better control when Puppet is permitted to enforce certain kinds of changes on systems, while continuously enforcing other configuration. We should provide an in-product noop() function which can be called directly, affecting class scope, or with a block, affecting that block's scope. These implementations should be more predictable and less brittle than the trlinkin-noop module's implementation. They should work at least as reliably and predictably as tags. class example1 { noop()   notify { 'I am no-op': } } class example2 { notify { 'I am op': }   noop() || { notify { 'I am no-op': } } } Add Comment   This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.394534.1617818266000.3574.1617818280158%40Atlassian.JIRA.