Jira (PUP-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6474 Incorporate gettext_setup gem into puppet Change By: Geoff Nichols Sprint: i18n, Client 2016-07-27, Client 2016-08-10, Client 2016-08-24, Client 2016-09-07 , Client 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Moses Mendoza commented on FACT-1502 Re: acceptance: mount a tmpfs directory and check the fact merged to facter/master at https://github.com/puppetlabs/facter/commit/e5e39cfc7fdc145c2a3a35503eb6064ff4bd3127 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-147) Add validation to the ZFS type
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-147 Add validation to the ZFS type Change By: Geoff Nichols Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-266) Allow puppet to manage owner & group file settings
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-266 Allow puppet to manage owner & group file settings Change By: Geoff Nichols Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-266) Allow puppet to manage owner & group file settings
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-266 Allow puppet to manage owner & group file settings Change By: Geoff Nichols Priority: Major Normal Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-266) Allow puppet to manage owner & group file settings
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-266 Allow puppet to manage owner & group file settings Change By: Geoff Nichols Fix Version/s: PUP 4.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6614) Puppet 4.6.0 Error transactionstore is corrupt
Title: Message Title Ethan Brown commented on PUP-6614 Re: Puppet 4.6.0 Error transactionstore is corrupt Curtis Ruck - thanks for the ticket. This was a known issue in Puppet 4.6.0 and Puppet 4.6.1, and should be fixed in Puppet 4.6.2 (shipped in puppet-agent 1.6.2 at https://downloads.puppetlabs.com/windows/puppet-agent-1.6.2-x64.msi / https://downloads.puppetlabs.com/windows/puppet-agent-1.6.2-x86.msi) Have you tried updating to that version Curtis Ruck / could you verify if this issue is resolved for you? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6708) Agent does not save local copy of last_run_report.yaml if submission to report server fails
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6708 Agent does not save local copy of last_run_report.yaml if submission to report server fails Change By: Geoff Nichols Sprint: AP Triage 2016-10-19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6119) environment returned from ENC makes site.pp not be included
Title: Message Title Robert Brooks commented on PUP-6119 Re: environment returned from ENC makes site.pp not be included Hi Henrik Lindberg, I'd love to move us up to Puppet 4.x, I just wish the upgrade path was a little less significant. As it is we live with a bunch of 3.x annoyances Consider my arm twisted, I will look again at what it will take. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6708) Agent does not save local copy of last_run_report.yaml if submission to report server fails
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6708 Agent does not save local copy of last_run_report.yaml if submission to report server fails Change By: Geoff Nichols Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1467) Add Windows computer_sid fact
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1467 Add Windows computer_sid fact Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6702) Windows service in Paused state cannot be managed
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6702 Windows service in Paused state cannot be managed Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6699) Leading zero with cron resource is not handled as expected.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6699 Leading zero with cron resource is not handled as expected. Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6330) puppet uninstall exe resource fails on windows due to missing quotes
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6330 puppet uninstall exe resource fails on windows due to missing quotes Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1504) Uptime resolver fact for Windows uses unreliable metric for uptime
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1504 Uptime resolver fact for Windows uses unreliable metric for uptime Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6716 Error when purging local users on Windows Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-2640) Use gzip compression for commands sent from the terminus
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2640 Use gzip compression for commands sent from the terminus Change By: Ryan Senior Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-3056) periodic acceptance tests broken on master and stable
Title: Message Title Rob Browning commented on PDB-3056 Re: periodic acceptance tests broken on master and stable Looks suspiciously similar: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770605 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-3056) periodic acceptance tests broken on master and stable
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3056 periodic acceptance tests broken on master and stable Change By: Rob Browning Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-3056) periodic acceptance tests broken on master and stable
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3056 periodic acceptance tests broken on master and stable Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1484) Transient - Facter fails to build on cisco-wrlinux7
Title: Message Title Michael Smith commented on FACT-1484 Re: Transient - Facter fails to build on cisco-wrlinux7 A warning (or even debug sometimes) is how we frequently treat these types of failures in Facter. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-3062) Write up end-user docs with perf recommendations with stockpile
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3062 Write up end-user docs with perf recommendations with stockpile Issue Type: New Feature Assignee: Unassigned Created: 2016/09/20 1:51 PM Priority: Normal Reporter: Ryan Senior We've accumulated a decent amount of knowledge around PuppetDB performance and how the knobs we have affect PuppetDB + Stockpile's performance. Our default performance is still better than when we were running ActiveMQ. Depending on the user's setup, they could get significantly faster processing. We should write this up in an existing PDB doc or a new one that go along with our other administration/faq pages. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-3061) Create an AMQ upgrade acceptance test
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3061 Create an AMQ upgrade acceptance test Issue Type: New Feature Assignee: Unassigned Created: 2016/09/20 1:48 PM Priority: Normal Reporter: Ryan Senior The test should run the following if upgrade_latest is true: start "old" PDB with command processing disabled run the puppet agent stop puppetdb upgrade start puppetdb query for the data from the first puppet agent run
Jira (PDB-3060) Make the concurrent-writes config "official"
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3060 Make the concurrent-writes config "official" Issue Type: New Feature Assignee: Unassigned Created: 2016/09/20 1:37 PM Priority: Normal Reporter: Ryan Senior I added a concurrent-writes knob that would constrain the number of threads that could write to the disk to the given number. This has turned out to be a useful parameter. We should make it an official parameter (with documentation) that defaults to number of cpus / 2. This should also go in our default config (commented) and the puppet module. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6457) Mount resources could handle invalid options better
Title: Message Title Kurt Wall commented on PUP-6457 Re: Mount resources could handle invalid options better After kicking this around yesterday, I'm not able to reproduce the reported errors. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1492) FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1492 FACT [OS][RELEASE][MAJOR] returns FULL version instead of MAJOR version on WIndows Server 2016 Change By: Maggie Dreyer Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1507) acceptance: test fact blocklist in config file
Title: Message Title Glenn Sarti updated an issue Facter / FACT-1507 acceptance: test fact blocklist in config file Change By: Glenn Sarti Comment: A comment with security level 'Developers' was removed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1507) acceptance: test fact blocklist in config file
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1507 acceptance: test fact blocklist in config file Change By: Maggie Dreyer Sprint: AP Triage 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1509) Add command line option to ignore fact cache
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1509 Add command line option to ignore fact cache Change By: Maggie Dreyer Sprint: AP 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1484) Transient - Facter fails to build on cisco-wrlinux7
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1484 Transient - Facter fails to build on cisco-wrlinux7 Change By: Maggie Dreyer Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1484) Transient - Facter fails to build on cisco-wrlinux7
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1484 Transient - Facter fails to build on cisco-wrlinux7 Change By: Maggie Dreyer Assignee: Branan Riley Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1484) Transient - Facter fails to build on cisco-wrlinux7
Title: Message Title Maggie Dreyer assigned an issue to Unassigned Facter / FACT-1484 Transient - Facter fails to build on cisco-wrlinux7 Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1484) Transient - Facter fails to build on cisco-wrlinux7
Title: Message Title Maggie Dreyer commented on FACT-1484 Re: Transient - Facter fails to build on cisco-wrlinux7 This shows up in at least half of pipeline runs, pulling into next sprint. This is the error, which occurs during the Facter smoke test: ERROR puppetlabs.facter - getaddrinfo failed: Temporary failure in name resolution (-3): hostname may not be externally resolvable. It is coming from https://github.com/puppetlabs/facter/blob/master/lib/src/facts/posix/networking_resolver.cc#L94 Facter still prints its output, but then exits 1, because we are logging this as an error. Should it be a warning instead? Or is there some deeper solution for this particular platform? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1484) Transient - Facter fails to build on cisco-wrlinux7
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1484 Transient - Facter fails to build on cisco-wrlinux7 Change By: Maggie Dreyer Story Points: 2 Sprint: AP 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Phong Ly commented on FACT-1502 Re: acceptance: mount a tmpfs directory and check the fact Mose I just pushed a new PR for fixing it : https://github.com/puppetlabs/facter/pull/1430 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Phong Ly assigned an issue to Moses Mendoza Facter / FACT-1502 acceptance: mount a tmpfs directory and check the fact Change By: Phong Ly Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Paul Anderson commented on PUP-6713 Re: Vim should highlight data types in a class definition Some additional investigation has been done between Tobias Wolter and myself: I wrote a quick puppet manifest to install a puppet developer environment (specifically vim, vim-puppet and puppet-lint): https://gist.github.com/hpcprofessional/03100e873b244da48f46fcd1d207bdb2 I saw some inconsistent behavior between puppetlabs/puppet-syntax-vim and rodjek/puppet-vim, and Tobias Wolter did too. A screen shot of a slightly more complicated example is attached. Notice the issue starts on line 8: Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-3059) Investigate and possibly adjust/remove memoized-resource-identity hash
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3059 Investigate and possibly adjust/remove memoized-resource-identity hash Change By: Rob Browning From a first pass, it appears that this memoization may be consuming very large quantities of RAM (30GB?), presumably for the parameters, when there are very large resources (say 150MB firewall rules). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-3059) Investigate and possibly adjust/remove memoized-resource-identity hash
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3059 Investigate and possibly adjust/remove memoized-resource-identity hash Issue Type: Bug Assignee: Unassigned Created: 2016/09/20 12:18 PM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Paul Anderson updated an issue Puppet / PUP-6713 Vim should highlight data types in a class definition Screen shots provided by Tobias Wolter Change By: Paul Anderson Attachment: Screenshot from 2016-09-20 13-28-50.png Attachment: Screenshot from 2016-09-20 13-38-20.png Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1507) acceptance: test fact blocklist in config file
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1507 acceptance: test fact blocklist in config file Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-2791) Test stockpile/store's error cases more thoroughly.
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2791 Test stockpile/store's error cases more thoroughly. Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title Maggie Dreyer assigned an issue to Phong Ly Facter / FACT-1502 acceptance: mount a tmpfs directory and check the fact Change By: Maggie Dreyer Assignee: Moses Mendoza Phong Ly Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1509) Add command line option to ignore fact cache
Title: Message Title Maggie Dreyer created an issue Facter / FACT-1509 Add command line option to ignore fact cache Issue Type: Improvement Assignee: Unassigned Created: 2016/09/20 10:19 AM Fix Versions: FACT 3.5.0 Priority: Normal Reporter: Maggie Dreyer With the addition of fact caching (see FACT-348), it would be nice to be able to force the cache to be ignored and/or refreshed via command line option. Add Comment
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title
Maggie Dreyer updated an issue
Facter / FACT-718
Allow for disabling certain facts within Facter
Change By:
Maggie Dreyer
Release Notes Summary:
This allows Some facts are blockable in groups, as described in the user fact schema. Adding one of these groups to specify in the config file a list of fact groups that element `blocklist` will not be prevented from resolving resolved the next time Facter runs is run . This is useful to block facts that are very expensive to resolve, or even completely broken, if they are not needed by the user.Example:facts : { blocklist : [ "EC2", "file system" ] }If this block is present in the config file, EC2 facts and file system facts (e.g. mountpoints, partitions) will not be resolved.This feature is currently enabled for only a small subset of facts. If a fact has a `blockgroup` listed in its description, it can be blocked with this feature, along with all the other facts in that group. Blocking only subsets of groups is not supported.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title
Maggie Dreyer updated an issue
Facter / FACT-718
Allow for disabling certain facts within Facter
Change By:
Maggie Dreyer
Comment:
Some facts are blockable in groups, as described in the fact schema. Adding one of these groups to the config file list element `blocklist` will not be resolved the next time Facter is run. This is useful to block facts that are very expensive to resolve, or even completely broken, if they are not needed by the user.Example:facts : {blocklist : [ "EC2", "file system" ]}If this block is present in the config file, EC2 facts and file system facts (e.g. mountpoints, partitions) will not be resolved.This feature is currently enabled for only a small subset of facts. If a fact has a `blockgroup` listed in its description, it can be blocked with this feature, along with all the other facts in that group. Blocking only subsets of groups is not supported.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title
Maggie Dreyer updated an issue
Facter / FACT-718
Allow for disabling certain facts within Facter
Change By:
Maggie Dreyer
Comment:
Some facts can now be blocked via a list in the config file:facts : {blocklist : [ "EC2", "file system" ]}The above block would prevent the EC2 facts and the file system facts (e.g. mountpoints, partitions) from being resolved the next time Facter runs. This is useful for blocking facts which are either expensive to collect, or whose collection causes issues on a given system, if the user does not need to use the fact values.This feature is not enabled for all facts. If a fact has a `blockgroup` field in its schema description, it can be blocked using the above list, along with all the other facts in that group. Blocking subsets of groups is not supported.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title
Maggie Dreyer updated an issue
Facter / FACT-718
Allow for disabling certain facts within Facter
Some facts can now be blocked via a list in the config file:
facts : { blocklist : [ "EC2", "file system" ] }
The above block would prevent the EC2 facts and the file system facts (e.g. mountpoints, partitions) from being resolved the next time Facter runs. This is useful for blocking facts which are either expensive to collect, or whose collection causes issues on a given system, if the user does not need to use the fact values.
This feature is not enabled for all facts. If a fact has a `blockgroup` field in its schema description, it can be blocked using the above list, along with all the other facts in that group. Blocking subsets of groups is not supported.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title
Maggie Dreyer updated an issue
Facter / FACT-718
Allow for disabling certain facts within Facter
Some facts are blockable in groups, as described in the fact schema. Adding one of these groups to the config file list element `blocklist` will not be resolved the next time Facter is run. This is useful to block facts that are very expensive to resolve, or even completely broken, if they are not needed by the user.
Example:
facts : { blocklist : [ "EC2", "file system" ] }
If this block is present in the config file, EC2 facts and file system facts (e.g. mountpoints, partitions) will not be resolved.
This feature is currently enabled for only a small subset of facts. If a fact has a `blockgroup` listed in its description, it can be blocked with this feature, along with all the other facts in that group. Blocking only subsets of groups is not supported.
Change By:
Maggie Dreyer
Release Notes Summary:
This allows the user to specify in the config file a list of fact groups that will be prevented from resolving the next time Facter runs.
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1502) acceptance: mount a tmpfs directory and check the fact
Title: Message Title
Moses Mendoza commented on FACT-1502
Re: acceptance: mount a tmpfs directory and check the fact
The merged PR has failed tests on OSX, Solaris, (and possibly cisco).
Links to example failed runs: https://jenkins.puppetlabs.com/view/agent-platform-triage/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-master/196/SLAVE_LABEL=beaker,TEST_TARGET=solaris10-64a/console https://jenkins.puppetlabs.com/view/agent-platform-triage/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-master/196/SLAVE_LABEL=beaker,TEST_TARGET=osx1010-64a/consoleFull
Output from failure:
16:53:32 Begin tests/verify_mountpoints.rb
16:53:32
16:53:32 FACT-1502 - C98163 mountpoints fact should show mounts on tmpfs
16:53:32
16:53:32 b6zcjbrmts5yy38.delivery.puppetlabs.net (solaris10-64-1) 16:53:32$ mkdir -p /tmp/tempdir
16:53:32
16:53:32 b6zcjbrmts5yy38.delivery.puppetlabs.net (solaris10-64-1) executed in 0.04 seconds
16:53:32 localhost $ scp /tmp/beaker20160919-8167-1eki1pp solaris10-64-1:mount_manifest.pp {:ignore => }
Jira (PUP-6706) Add Binary type to Puppet Serialization
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6706 Add Binary type to Puppet Serialization Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6714) PCore generation omits information about capability types
Title: Message Title Chris Cowell commented on PUP-6714 Re: PCore generation omits information about capability types Do we have an ETA on this? Alternately, could we bump it to critical? It's having a severe impact on HA testing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-3050) Implementation
Title: Message Title Karel Brezina commented on PDB-3050 Re: Implementation Ryan Senior This is just a sub-task. The main task PDB-3047 contains a bit more description with a link to the main task PE-17254. The main task has more info and a link to UX wireframes. There's even a confluence page - https://confluence.puppetlabs.com/display/enterprise/Report+on+corrective+change+events+in+the+GUI Basically, we need to differentiate between intentional and corrective changes in PE Events. To support that, we had to change aggregate-event-counts and event-counts PDB endpoints to provide intentional and corrective counts for successes (changes) and noops. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PDB-3050) Implementation
Title: Message Title Karel Brezina assigned an issue to qa PuppetDB / PDB-3050 Implementation Change By: Karel Brezina Status: Ready for CI Test Assignee: Karel Brezina qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6705) Add Sensitive type to Puppet Serialization
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6705 Add Sensitive type to Puppet Serialization Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (FACT-1508) End-to-end POC for string externalization in Facter
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1508 End-to-end POC for string externalization in Facter Change By: Geoff Nichols Sprint: i18n Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols Sprint: i18n Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-5834) Handle extended data in the catalog
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5834 Handle extended data in the catalog Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6612) Scope effort for i18n string externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Geoff Nichols Sprint: i18n AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6612) Scope effort for i18n string externalization
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Geoff Nichols Sprint: AP Triage i18n Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Craig Dunn commented on PUP-6712 Re: Arrays in resource chaining Totally agreed. <||> should imply collection, where as Resource implies reference. therefore Foo -> Bar implies referencing and setting relationships, but not collection. That way I can do: Yumrepo -> Package ... and not care if some modules are using virtualized package resources, since they won't get realized with the above syntax. I realise this is off topic from the original ticket, but this would be a really nice side effect Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title R.I.Pienaar commented on PUP-6712 Re: Arrays in resource chaining Yes if we can make it so that syntax does not realise then that would be a massive win I was saying if without them would be a shortcut to the exact same behaviour it would be more confusing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Craig Dunn commented on PUP-6712 Re: Arrays in resource chaining But Foo -> Bar would presumably be a nice way to set resource dependancies without collecting virtual resources. It's always bothered me that the two are so intertwined. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title R.I.Pienaar commented on PUP-6712 Re: Arrays in resource chaining I find the empty <||> is a nice reminder that this is in fact a find+realise and not a find. Of course the % of users who even know what virtual resources are must be single digit but might become even more surprising. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-4673) Pip installs from behind proxy can't ensure=>latest
Title: Message Title Jon Skarpeteig assigned an issue to Jon Skarpeteig Puppet / PUP-4673 Pip installs from behind proxy can't ensure=>latest Change By: Jon Skarpeteig Assignee: Jon Skarpeteig Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Craig Dunn commented on PUP-6712 Re: Arrays in resource chaining Out of interest, by definition, if the above syntax would work then could I also replace Yumrepo<||> -> Package <||> With simply; Yumrepo -> Package That would be a really nice side effect, since adding the <||> when there is no filter is tiresome. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Craig Dunn commented on PUP-6712 Re: Arrays in resource chaining Henrik Lindberg That would probably solve 99% of the use cases that I've seen - so my above example would become $fw_resources = [ Firewalld_zone, Firewalld_rich_rule, Firewalld_service, Firewalld_port, Firewalld_direct_chain, Firewalld_direct_rule, Firewalld_direct_passthrough ] Service['firewalld'] -> $fw_resources ~>
