Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11023 Make trlinkin-noop a fully supported feature Change By: Josh Cooper Epic Link: PA-3841 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.42535.1665030600061%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11023 Make trlinkin-noop a fully supported feature Change By: Josh Cooper Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.42533.1665030240133%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title productboard updated an issue Puppet / PUP-11023 Make trlinkin-noop a fully supported feature Change By: productboard productboard URL: https://puppet.productboard.com/feature-board/planning/features/11142283 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.5088.1639492200055%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title David Sandilands commented on PUP-11023 Re: Make trlinkin-noop a fully supported feature I would have bitten your hand off to have this feature when i was a customer I had and a number of customers like Natwest and Blackrock Andy Troup have a struggle to move the customer or certain nodes from noop to enforcement because its an all or nothing event. This creates side problems agent upgrades are harder with noop and stymie efforts to move to proper puppet enforcing. 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.106181.1628760180025%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title Beth Glenfield assigned an issue to Unassigned Puppet / PUP-11023 Make trlinkin-noop a fully supported feature Change By: Beth Glenfield Assignee: Beth Glenfield 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.71502.1625152500326%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11023 Make trlinkin-noop a fully supported feature Change By: Ciprian Badescu Epic Link: PA-3841 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.63725.1624457580601%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title Beth Glenfield commented on PUP-11023 Re: Make trlinkin-noop a fully supported feature We're looking to prioritize this work and will be tracking additional input from the wider customer base and community on Productboard: https://puppet.com/puppet-idea-portal/. Reid Vandewiele it would be good to get some time to discuss this in more depth, I'll try and find some time in your calendar for next week. 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.61003.1624290600132%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title Reid Vandewiele commented on PUP-11023 Re: Make trlinkin-noop a fully supported feature Hey Ciprian Badescu, can you add a comment clarifying what information is needed, or if it is not literally information needed, what next steps / conditions / events the ticket is now waiting on? Thanks! 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.57158.1623781380027%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title Ciprian Badescu assigned an issue to Beth Glenfield Puppet / PUP-11023 Make trlinkin-noop a fully supported feature Change By: Ciprian Badescu Assignee: Beth Glenfield 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.56756.1623766740032%40Atlassian.JIRA.
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-11023
Make trlinkin-noop a fully supported feature
Change By:
Reid Vandewiele
The Forge module [trlinkin-noop|https://forge.puppet.com/modules/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|https://forge.puppet.com/modules/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.* The behavior with regards to propagation relating to { {include()}} is the thing most important to make better compared to trlinkin-noop. { code:java}class example1 { noop() notify { 'I am no-op': }} {code}{code:java} class example2 { noop() || { notify { 'I am no-op': } } notify { 'I am op': }}{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-11023
Make trlinkin-noop a fully supported feature
Change By:
Reid Vandewiele
The Forge module [trlinkin-noop|https://forge.puppet.com/modules/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|https://forge.puppet.com/modules/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.*{code:java} class example1 { noop() notify { 'I am no-op': }} {code}{code:java}class example2 { noop() || { notify { 'I am no- op': } } noop() || { notify { 'I am no- op': } } }{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11023) Make trlinkin-noop a fully supported feature
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': }
