Jira (PUP-10850) Puppet facts show doesn't have an option to opt out of legacy facts
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10850
Puppet facts show doesn't have an option to opt out of legacy facts
Change By:
Josh Cooper
*Puppet Version: 7.0.1* *Puppet Server Version: -* *OS Name/Version: All*By default{ code:java noformat }puppet facts show{ code noformat }displays legacy facts, there is an option (--show-legacy) that has no effect. There isn't any way to indicate puppet to not retrieve legacy facts.*Desired Behavior:* Add option By default {{puppet facts show}} does not display legacy facts, but they may be displayed using {{puppet facts show -- no show -legacy to disable legacy facts. }}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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
Jira (PUP-10850) Puppet facts show doesn't have an option to opt out of legacy facts
Title: Message Title Josh Cooper commented on PUP-10850 Re: Puppet facts show doesn't have an option to opt out of legacy facts Ah I think part of my confusion is that virtual seems to always be emitted when showing legacy facts or not. Is that expected? $ bx facter | grep '^virtual' virtual => physical If I use a different legacy fact, then it seems to work as expected: $ bx puppet facts show | jq .swapfree null $ bx puppet facts show --show-legacy | jq .swapfree "1.09 GiB" Add Comment
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title Trevor Vaughan commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax Just found this ticket, but I also would like to be able to say X comes after all Packages without actually realizing them. Making this a set of functions might be more straightforward and non-breaking. It's not as puppet-y but I think people are pretty used to functions doing magic at this point. The only use cases that I've ever had for collectors are: Making things come before/after other things Performing resource overrides (key in many cases) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.191187.1494891335000.121336.1611259920031%40Atlassian.JIRA.
Jira (PDB-5001) PuppetDB Cli pupept-query command not respecting https_proxy environment variable
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5001 PuppetDB Cli pupept-query command not respecting https_proxy environment variable Change By: Austin Blatt Team: PuppetDB Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.384070.1611213926000.121245.1611256620244%40Atlassian.JIRA.
Jira (PDB-4934) PuppetDB does not support username@hostname auth for Azure PostgreSQL
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie PuppetDB / PDB-4934 PuppetDB does not support username@hostname auth for Azure PostgreSQL Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.375238.1603127441000.121048.1611246420028%40Atlassian.JIRA.
Jira (PUP-10371) Add metric for Puppet Agent run
Title: Message Title Adam Winberg commented on PUP-10371 Re: Add metric for Puppet Agent run Also, since splaytime is included in the calculation all config reports in Foreman have the same time stamp - HH:01. So it appears that all agents have run at the same time. ( we run puppet agents hourly and trigger the run at HH:01 with a splaylimit of 900s. ) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349708.1584344056000.120844.1611229500039%40Atlassian.JIRA.
Jira (PUP-6743) Classes should propagate schedule metaparameter to its contained resources
Title: Message Title Ruben Stein commented on PUP-6743 Re: Classes should propagate schedule metaparameter to its contained resources It is very frustrating that schedules cannot be used for any third party code where you can't dig deep enough to inject the schedule in the leaf resources. I just wanted our puppet agents to be updated only during a maintenance window, but adding a schedule to the puppet_agent resource is completely useless. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.153663.1474968853000.120788.1611220800027%40Atlassian.JIRA.
