Jira (PUP-6021) Tidy can not trigger resources
Title: Message Title Glen Newman commented on PUP-6021 Re: Tidy can not trigger resources Came across this issue (puppet version 6.18.0). Tidy resource cannot notify an exec resource. I noticed though, that turning the tidy into a file resource (with ensure => absent set) does work to notify the exec resource. The documentation for tidy has this note: > This resource type works by generating a file resource for every file that should be deleted and then letting that resource perform the actual deletion. I'm wondering if the "notify" attribute for a tidy resource is not preserved when the file resource is generated? 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.120354.1457449682000.3992.1647454080034%40Atlassian.JIRA.
Jira (PDB-5467) Always pass messages to tk request-shutdown
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5467 Always pass messages to tk request-shutdown Change By: Rob Browning Fix Version/s: PDB 6.20.3 Fix Version/s: PDB 7.9.3 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.439654.1646949435000.3710.1647451560185%40Atlassian.JIRA.
Jira (PDB-5467) Always pass messages to tk request-shutdown
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-5467 Always pass messages to tk request-shutdown Change By: Rob Browning Release Notes: Not Needed 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.439654.1646949435000.3709.1647451560136%40Atlassian.JIRA.
Jira (FACT-3106) No virt-what in puppet-agent 7 so is_virtual is wrong
Title: Message Title Steve Traylen commented on FACT-3106 Re: No virt-what in puppet-agent 7 so is_virtual is wrong For similar reasons requiring pciutils for lspci is also a good idea. 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.434970.1644582226000.3624.1647448980033%40Atlassian.JIRA.
Jira (PUP-11442) 17. Update Public-facing Puppet docs to include macOS 12 (x86_64)
Title: Message Title Christopher Thorn updated an issue Puppet / PUP-11442 17. Update Public-facing Puppet docs to include macOS 12 (x86_64) Change By: Christopher Thorn Sprint: Phoenix 2022- 03 04 - 30 13 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.433576.1643678327000.3539.1647445260043%40Atlassian.JIRA.
Jira (PUP-11451) Make collecting exported resources optional
Title: Message Title Nacho Barrientos commented on PUP-11451 Re: Make collecting exported resources optional Hi Charlie, Ben, Thanks for your input. Our use case is a multi tenant configuration management infrastructure based on Puppet where somebody could accidentally or maliciously export a resource to be collected by somebody else that could lead to broken or malicious configuration being applied. In our case, the usage of exported resources can normally easily be replaced by PuppetDB queries so we'd like to disable resource collection to reduce the risks. Replying to your comment Charlie, unfortunately we as admins don't have full control on the code that our masters compile and our users are not enforced (only encouraged) to implement lint checks. Ben, I understand your concerns but I don't think bad communication from the admins justify not having the functionality. In my opinion, as long as the defaults are not modified and the setting well documented, it should be okay. We cannot influence how configuration changes on the masters are communicated everywhere Anyway, thanks for your input and please let us know at your earliest convenience if you'd like us to contribute a change request. Otherwise, we'll most likely carry a local patch to disable exported resources collection. Thanks again. /cc traylenator 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
