Jira (BOLT-426) Standalone Bolt packages
Title: Message Title Michael Smith assigned an issue to Nick Lewis Puppet Task Runner / BOLT-426 Standalone Bolt packages Change By: Michael Smith Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-466) Document creating release tickets for Bolt
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-466 Document creating release tickets for Bolt Issue Type: Task Assignee: Lucy Wyman Created: 2018/04/10 4:42 PM Priority: Normal Reporter: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-334) Package core task content with bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-334 Package core task content with bolt Change By: Michael Smith Release Notes Summary: The puppetlabs-package, service, and puppet_conf modules are now available out-of-the-box with Bolt. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-334) Package core task content with bolt
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-334 Package core task content with bolt Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-334) Package core task content with bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-334 Package core task content with bolt Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-456) Plans should restrict return types to expected values
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-456 Plans should restrict return types to expected values Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-456) Plans should restrict return types to expected values
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-456 Plans should restrict return types to expected values Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8619) File Resource: error when attempting to use checksum and checksum_value to retrieve from filebucket
Title: Message Title
Jennifer Solman updated an issue
Puppet / PUP-8619
File Resource: error when attempting to use checksum and checksum_value to retrieve from filebucket
Change By:
Jennifer Solman
Describe steps to reproduce… * manifest.pp{code} file { '/Users//PUP7534/firstFile': content => 'hello world', ensure => file }{code} * bundle exec ./bin/puppet apply manifest.pp * md5 /Users//PUP7534/firstFile ** to get checksum * checksum.pp{code} file { '/Users//PUP7534/targetFile': ensure => 'file', checksum => 'md5', checksum_value => '5eb63bbbe01eeed093cb22bb8f5acdc3', }{code} * bundle exec ./bin/puppet apply checksum.pp*Desired Behavior:*specifying checksum and checksum_value properties on a file resource causes puppet to use the corresponding file from filebucket to sync the file resource*Actual Behavior:*using checksum and checksum_value properties on a file resource result in an error: 'Checksum value is ignored unless content or source are specified'*Acceptance Criteria:* * When checksum/checksum_value and content are specified ** should error compare checksum_value to file content on disk * ** if out of sync if content property * use content property value to update file content on disk else * use checksum_value to retrieve from filebucket * When checksum/checksum_value and source are specified ** this is fine ** if checksum doesn't match then look at source file (in_sync?) ** if no source fall back to file bucket * When one but not both of checksum or checksum_value are specified ** there should be a default for checksum so this isn't an issue * checksum type without value ** make sure nothing terrible happens here * source without checksum ** ?
Add Comment
Jira (BOLT-464) Publish Bolt to chocolatey.org
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-464 Publish Bolt to chocolatey.org Change By: Michael Smith On release, publish Bolt to chocolatey.org. PDK has some automation at https://github.com/puppetlabs/puppet-chocolatey-packages that we can tie start from. Publish should be tied into release jobs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-464) Publish Bolt to chocolatey.org
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-464 Publish Bolt to chocolatey.org Change By: Michael Smith On release, publish Bolt to chocolatey.org. [~Glenn Sarti] PDK has some automation at https://github.com/ glennsarti puppetlabs / ChocolateyPackages/tree/master/pdk puppet - community chocolatey-packages that we can tie into release jobs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-429) Create standalone Linux packages
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-429 Create standalone Linux packages Change By: Michael Smith Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-465) Publish Bolt to Homebrew Cask
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-465 Publish Bolt to Homebrew Cask Issue Type: Improvement Assignee: Unassigned Created: 2018/04/10 3:22 PM Priority: Normal Reporter: Michael Smith On release, publish Bolt to homebrew-cask, similar to https://github.com/caskroom/homebrew-cask/blob/master/Casks/pdk.rb. We can automate generating the PR to homebrew-cask on release. Make sure it tags team members to track completion. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-465) Publish Bolt to Homebrew Cask
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-465 Publish Bolt to Homebrew Cask Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-464) Publish Bolt to chocolatey.org
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-464 Publish Bolt to chocolatey.org Change By: Michael Smith Summary: Publish Chocolatey packages for Bolt to chocolatey.org Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-464) Publish Chocolatey packages for Bolt
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-464 Publish Chocolatey packages for Bolt Issue Type: Improvement Assignee: Unassigned Created: 2018/04/10 3:21 PM Priority: Normal Reporter: Michael Smith On release, publish Bolt to chocolatey.org. Glenn Sarti has some automation at https://github.com/glennsarti/ChocolateyPackages/tree/master/pdk-community that we can tie into release jobs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-426) Standalone Bolt packages
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-426 Standalone Bolt packages Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-439) Allow nested subgroups in inventory files
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-439 Allow nested subgroups in inventory files Change By: Michael Smith Release Notes Summary: Inventory groups can now be nested in other groups, allowing you to represent hierarchical grouping. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-439) Allow nested subgroups in inventory files
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-439 Allow nested subgroups in inventory files Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1768) libwhereami uses deprecated syntax
Title: Message Title Enis Inan updated an issue Facter / FACT-1768 libwhereami uses deprecated syntax Change By: Enis Inan Fix Version/s: FACT 3.9.6 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-439) Allow nested subgroups in inventory files
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-439 Allow nested subgroups in inventory files Change By: Michael Smith Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-431) Add Windows builds
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-431 Add Windows builds Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-430) Add macOS builds
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-430 Add macOS builds Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1737) Add "disks" and "partitions" facts on FreeBSD
Title: Message Title Geoff Nichols assigned an issue to Jonathan Morris Facter / FACT-1737 Add "disks" and "partitions" facts on FreeBSD Change By: Geoff Nichols Assignee: Scott Garman Jonathan Morris Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-463) Migration docs to include moving from mco to orchestrator
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-463 Migration docs to include moving from mco to orchestrator Issue Type: Task Assignee: Unassigned Created: 2018/04/10 1:57 PM Priority: Normal Reporter: Yasmin Rajabi we need a guide to go with the diagrams in DESIGN-2701 that incorporate the new toggles for turning mcollective off Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3808) The node_state parameter causes an error in conditional statements
Title: Message Title Kenn Hussey commented on PDB-3808 Re: The node_state parameter causes an error in conditional statements AJ Roetker please add release notes for this issue, if needed. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8606) Module-defined data types are very verbose when displayed
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8606 Module-defined data types are very verbose when displayed Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6344 metrics.time.total does not correlate to time reported in log Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8615) sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8615 sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Russell Mull commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs Agree, I think this is a bug. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Nick Walker commented on PDB-3747 Re: PDB holds summary query transactions open during long syncs Russell Mull thoughts on this? Seems like a cascading failure when sync fails and you need to re-sync you don't want to get into this situation. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-431) Add Windows builds
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-431 Add Windows builds Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-439) Allow nested subgroups in inventory files
Title: Message Title Alex Dreyer assigned an issue to Nick Lewis Puppet Task Runner / BOLT-439 Allow nested subgroups in inventory files Change By: Alex Dreyer Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3862) replace facts failing for some nodes
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3862 replace facts failing for some nodes Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1737) Add "disks" and "partitions" facts on FreeBSD
Title: Message Title Geoff Nichols assigned an issue to Scott Garman Facter / FACT-1737 Add "disks" and "partitions" facts on FreeBSD Change By: Geoff Nichols Assignee: Branan Riley Scott Garman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-451) I would like to suppress notice level run_* logging in my plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-451 I would like to suppress notice level run_* logging in my plan Change By: Alex Dreyer When writing a plan that loops over nodes running a set of tasks on them the default notice level logging can swamp intentional log messages unless they are written at the warn level. run_task, run_command, run_script, upload_file functions should accept a '_quiet' option OR we can expose functions to tell the executor whether to log step messages at notice or info. Possible solutions:- A CLI flag --quiet to log at warn level- An option to run_* to disable executor notice messages. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
Jira (BOLT-453) Use more readable log format for the console.
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-453
Use more readable log format for the console.
Change By:
Michael Smith
The log format makes sense for logging to file but is hard to read on the CLI. Now that we have separate loggers for file and console logging we should use a more succinct format for the console.What is the desired format.Only print the message. Use color to differentiate between error(red), warn(yellow), notice(green) and everything else uncolored.current:{noformat}$ bolt plan run my_app::deploy version=1.0.2 app_servers=app db_server=db lb_server=lb --inventoryfile ./inventory.yaml --modulepath=./modules2018-04-05T11:01:18.711945 NOTICE Bolt::Executor: Starting: Check load before starting deploy on ["0.0.0.0:32771"]2018-04-05T11:01:18.969123 NOTICE Bolt::Executor: Finished: Check load before starting deploy on 1 node with 0 failures2018-04-05T11:01:18.973994 NOTICE Bolt::Executor: Starting: Install 1.0.2 of the application on ["0.0.0.0:32768", "0.0.0.0:32769", "0.0.0.0:32770"]2018-04-05T11:01:19.237311 NOTICE Bolt::Executor: Finished: Install 1.0.2 of the application on 3 nodes with 0 failures2018-04-05T11:01:19.262561 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:19.413007 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32768 is ok with 7 open connections.2018-04-05T11:01:19.428637 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.553727 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.555688 NOTICE Bolt::Executor: Starting: Update application for new version on ["0.0.0.0:32768"]2018-04-05T11:01:22.697751 NOTICE Bolt::Executor: Finished: Update application for new version on 1 node with 0 failures2018-04-05T11:01:22.700624 NOTICE Bolt::Executor: Starting: Run Healthcheck for 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.784539 NOTICE Bolt::Executor: Finished: Run Healthcheck for 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.787086 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.875300 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 80): Deploy complete on Target('0.0.0.0:32768', {"connect-timeout"=>10, "tty"=>false, "host-key-check"=>false}).2018-04-05T11:01:22.878628 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.980944 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32769 is ok with 9 open connections.2018-04-05T11:01:22.985461 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32769 on ["0.0.0.0:32771"]2018-04-05T11:01:26.077658 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32769 on 1 node with 0
Jira (BOLT-455) Puppets log format doesn't match bolts
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-455 Puppets log format doesn't match bolts Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-455) Puppets log format doesn't match bolts
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-455 Puppets log format doesn't match bolts Change By: Alex Dreyer The puppet logger format doesn't match bolt's which makes is difficult to read logs that intermingle messages generated by bolt and messages logged intentionally from the the plan.Ideally users would be able to use the normal puppet log functions from their plans and have the format match bolt's log messages and get sent to the same destinations.Questions (spike) : can Can we wire the puppet logger to format messages and route them to bolts log destinationsCan we override the puppet log functions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-455) Puppets log format doesn't match bolts
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-455 Puppets log format doesn't match bolts Change By: Alex Dreyer The puppet logger format doesn't match bolt's which makes is difficult to read logs that intermingle messages generated by bolt and messages logged intentionally from the the plan.Ideally users would be able to use the normal puppet log functions from their plans and have the format match bolt's log messages and get sent to the same destinations. Questions:can we wire the puppet logger to format messages and route them to bolts log destinationsCan we override the puppet log functions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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
Jira (BOLT-453) Use more readable log format for the console.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-453 Use more readable log format for the console. Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-453) Use more readable log format for the console.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-453
Use more readable log format for the console.
Change By:
Alex Dreyer
The log format makes sense for logging to file but is hard to read on the CLI. Now that we have separate loggers for file and console logging we should use a more succinct format for the console.What is the desired format.Only print the message. Use color to differentiate between error(red), warn(yellow), notice(green) and everything else uncolored.current:{noformat}$ bolt plan run my_app::deploy version=1.0.2 app_servers=app db_server=db lb_server=lb --inventoryfile ./inventory.yaml --modulepath=./modules2018-04-05T11:01:18.711945 NOTICE Bolt::Executor: Starting: Check load before starting deploy on ["0.0.0.0:32771"]2018-04-05T11:01:18.969123 NOTICE Bolt::Executor: Finished: Check load before starting deploy on 1 node with 0 failures2018-04-05T11:01:18.973994 NOTICE Bolt::Executor: Starting: Install 1.0.2 of the application on ["0.0.0.0:32768", "0.0.0.0:32769", "0.0.0.0:32770"]2018-04-05T11:01:19.237311 NOTICE Bolt::Executor: Finished: Install 1.0.2 of the application on 3 nodes with 0 failures2018-04-05T11:01:19.262561 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:19.413007 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32768 is ok with 7 open connections.2018-04-05T11:01:19.428637 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.553727 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.555688 NOTICE Bolt::Executor: Starting: Update application for new version on ["0.0.0.0:32768"]2018-04-05T11:01:22.697751 NOTICE Bolt::Executor: Finished: Update application for new version on 1 node with 0 failures2018-04-05T11:01:22.700624 NOTICE Bolt::Executor: Starting: Run Healthcheck for 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.784539 NOTICE Bolt::Executor: Finished: Run Healthcheck for 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.787086 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.875300 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 80): Deploy complete on Target('0.0.0.0:32768', {"connect-timeout"=>10, "tty"=>false, "host-key-check"=>false}).2018-04-05T11:01:22.878628 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.980944 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32769 is ok with 9 open connections.2018-04-05T11:01:22.985461 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32769 on ["0.0.0.0:32771"]2018-04-05T11:01:26.077658 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32769 on 1 node with 0
Jira (BOLT-453) Use more readable log format for the console.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-453
Use more readable log format for the console.
Change By:
Alex Dreyer
The log format makes sense for logging to file but is hard to read on the CLI. Now that we have separate loggers for file and console logging we should use a more succinct format for the console.What is the desired format.Only print the message. Use color to differentiate between error(red), warn(yellow), notice(green) everything else uncolored. current:{noformat}$ bolt plan run my_app::deploy version=1.0.2 app_servers=app db_server=db lb_server=lb --inventoryfile ./inventory.yaml --modulepath=./modules2018-04-05T11:01:18.711945 NOTICE Bolt::Executor: Starting: Check load before starting deploy on ["0.0.0.0:32771"]2018-04-05T11:01:18.969123 NOTICE Bolt::Executor: Finished: Check load before starting deploy on 1 node with 0 failures2018-04-05T11:01:18.973994 NOTICE Bolt::Executor: Starting: Install 1.0.2 of the application on ["0.0.0.0:32768", "0.0.0.0:32769", "0.0.0.0:32770"]2018-04-05T11:01:19.237311 NOTICE Bolt::Executor: Finished: Install 1.0.2 of the application on 3 nodes with 0 failures2018-04-05T11:01:19.262561 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:19.413007 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32768 is ok with 7 open connections.2018-04-05T11:01:19.428637 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.553727 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.555688 NOTICE Bolt::Executor: Starting: Update application for new version on ["0.0.0.0:32768"]2018-04-05T11:01:22.697751 NOTICE Bolt::Executor: Finished: Update application for new version on 1 node with 0 failures2018-04-05T11:01:22.700624 NOTICE Bolt::Executor: Starting: Run Healthcheck for 0.0.0.0:32768 on ["0.0.0.0:32771"]2018-04-05T11:01:22.784539 NOTICE Bolt::Executor: Finished: Run Healthcheck for 0.0.0.0:32768 on 1 node with 0 failures2018-04-05T11:01:22.787086 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.875300 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 80): Deploy complete on Target('0.0.0.0:32768', {"connect-timeout"=>10, "tty"=>false, "host-key-check"=>false}).2018-04-05T11:01:22.878628 NOTICE Bolt::Executor: Starting: task my_app::lb on ["0.0.0.0:32771"]2018-04-05T11:01:22.980944 NOTICE Bolt::Executor: Finished: task my_app::lb on 1 node with 0 failuresNotice: Scope(/my_app/plans/deploy.pp, 47): Backend 0.0.0.0:32769 is ok with 9 open connections.2018-04-05T11:01:22.985461 NOTICE Bolt::Executor: Starting: Drain connections from 0.0.0.0:32769 on ["0.0.0.0:32771"]2018-04-05T11:01:26.077658 NOTICE Bolt::Executor: Finished: Drain connections from 0.0.0.0:32769 on 1 node with 0
Jira (PUP-8619) File Resource: error when attempting to use checksum and checksum_value to retrieve from filebucket
Title: Message Title Jennifer Solman updated an issue Puppet / PUP-8619 File Resource: error when attempting to use checksum and checksum_value to retrieve from filebucket Change By: Jennifer Solman Fix Version/s: PUP 5.5.1 Fix Version/s: PUP 5.5.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7534) Deprecate using file checksums in `content` property
Title: Message Title Jennifer Solman updated an issue Puppet / PUP-7534 Deprecate using file checksums in `content` property Change By: Jennifer Solman Fix Version/s: PUP 5.5.1 Fix Version/s: PUP 5.5.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8582) Add vendor_modules to basemodulepath
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8582 Add vendor_modules to basemodulepath Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-429) Create standalone Linux packages
Title: Message Title David Kramer assigned an issue to Nick Lewis Puppet Task Runner / BOLT-429 Create standalone Linux packages Change By: David Kramer Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-439) Allow nested subgroups in inventory files
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-439 Allow nested subgroups in inventory files Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-426) Standalone Bolt packages
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-426 Standalone Bolt packages Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Michael Smith Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-430) Add macOS builds
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-430 Add macOS builds Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: Michael Smith Assignee: Alex Dreyer Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-456) Plans should restrict return types to expected values
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-456 Plans should restrict return types to expected values Change By: Michael Smith Assignee: Alex Dreyer Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-439) Allow nested subgroups in inventory files
Title: Message Title David Kramer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-439 Allow nested subgroups in inventory files Change By: David Kramer Assignee: Nick Lewis Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-442) Bolt 0.18.2 2018-04-04 Release
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-442 Bolt 0.18.2 2018-04-04 Release Change By: Michael Smith Fix Version/s: BOLT 0.18.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7648) Fix ci:test:git pre-suite on OSX 10.11
Title: Message Title Melissa Stone updated an issue Puppet / PUP-7648 Fix ci:test:git pre-suite on OSX 10.11 Change By: Melissa Stone Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8306) Mechanism for syncing local git changes to remote testing host
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8306 Mechanism for syncing local git changes to remote testing host Change By: Melissa Stone Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8305 Git testing should consume the runtime archive rather than install system packages Change By: Melissa Stone Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-426) Standalone Bolt packages
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-426 Standalone Bolt packages Change By: Michael Smith Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Alex Dreyer commented on BOLT-454 Re: Plans should return undef without an explicit return I'd like us to have a larger conversations about what parts of the plan language belong in the bolt repo and what belong in puppet as we move toward 1.0 anyway. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8653) Agents should save all certs downloaded from the server
Title: Message Title Maggie Dreyer commented on PUP-8653 Re: Agents should save all certs downloaded from the server I walked through the existing indirector code for doing this download and drew the attached diagram. After talking with the rest of the team, the initial course of action is to separate out the key pieces of logic (e.g. URL construction and server/port selection) from the indirector classes into their own modules and build a simpler HTTP client API on top of them (possibly using the existing HTTP pool). The logic from the modules should then also be plumbed back into the indirector code, to avoid duplication. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Henrik Lindberg commented on BOLT-454 Re: Plans should return undef without an explicit return Oh - that is a bug actually - but it enables BOLT to fix that. Not sure if that is a happy path long term. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8653) Agents should save all certs downloaded from the server
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8653 Agents should save all certs downloaded from the server Change By: Maggie Dreyer Attachment: rest_terminus.jpg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8654) Agents should save all CRLs downloaded from the server
Title: Message Title Maggie Dreyer moved an issue Puppet / PUP-8654 Agents should save all CRLs downloaded from the server Change By: Maggie Dreyer Key: SERVER PUP - 2178 8654 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8653) Agents should save all certs downloaded from the server
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8653 Agents should save all certs downloaded from the server Change By: Maggie Dreyer Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8653) Agents should save all certs downloaded from the server
Title: Message Title Maggie Dreyer moved an issue Puppet / PUP-8653 Agents should save all certs downloaded from the server Change By: Maggie Dreyer Key: SERVER PUP - 2177 8653 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8656) Agents should use the CRL bundle to verify the revocation status of their master
Title: Message Title Maggie Dreyer moved an issue Puppet / PUP-8656 Agents should use the CRL bundle to verify the revocation status of their master Change By: Maggie Dreyer Key: SERVER PUP - 2180 8656 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8652) Agents should be able to use CA and CRL bundles
Title: Message Title Maggie Dreyer moved an issue Puppet / PUP-8652 Agents should be able to use CA and CRL bundles Change By: Maggie Dreyer Key: SERVER PUP - 2173 8652 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8655) Agent should use whole cert bundle to verify master's credentials
Title: Message Title Maggie Dreyer moved an issue Puppet / PUP-8655 Agent should use whole cert bundle to verify master's credentials Change By: Maggie Dreyer Key: SERVER PUP - 2179 8655 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-1974 Theme: Sensitive Data in Catalogs Change By: Owen Rodabaugh Team/s: Data Platform,Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Owen Rodabaugh Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: Users writing modules can run into this and end up thrashing around trying to understand why it's not working. Anything that makes writing modules more accessible/less confusing to users is a good thing.Given that the initial attempts at this included a significant performance impact, perhaps there is a middle ground of having a flag that tells puppet whether to rely on the dependencies entry in metadata.json or instead go for "slow mode", perhaps as a new metadata.json entry, where it scans the environment for functions. CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 3 - 25-50% of Customers Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Alex Dreyer commented on BOLT-454 Re: Plans should return undef without an explicit return :return is not caught in call_by_name_with_scope it bubbles up through the run_plan function. In order for us to handle the return value in run_plan we have to catch return there. https://github.com/puppetlabs/bolt/blob/master/bolt-modules/boltlib/lib/puppet/functions/run_plan.rb#L52 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8636 Don't prefetch if every resource using a provider is noop'd or no scheduled Change By: Owen Rodabaugh CS Priority: Needs Priority Minor CS Impact: Some resources such as selinux or mounts can be very expensive to run, taking minutes to run in some cases. Today this happens on every run even if that resource is only schedule to run a small portion of the time.This would be a nice feature for customers who have expensive resources being prefetched, potentially saving them up to minutes per puppet run. That said the schedule resource is not very commonly used. Metaparameters/filters such as schedule and tag based filtering would be suitable for this optimizationNoop still needs to prefetch check everything to determine what it will change and so would not work with this new feature. CS Severity: 2 - Annoyance CS Business Value: 2 - $$$ CS Frequency: 1 - 1-5% of Customers Add Comment
Jira (PUP-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8636 Don't prefetch if every resource using a provider is noop'd or no scheduled Change By: Owen Rodabaugh Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title Charlie Sharpsteen commented on PUP-8636 Re: Don't prefetch if every resource using a provider is noop'd or no scheduled We still have to prefectch for noop as the noop'd resource has to report what change would have been made — which requires fetching the current state of the resource. Skipping prefetches when no resources of a given type are scheduled (or selected by something like a tag filter) does seem like a useful optimization. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Change By: Charlie Sharpsteen CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8651) Augeas unknown error - Matching path expression
Title: Message Title Charlie Sharpsteen assigned an issue to Patrick Grant Puppet / PUP-8651 Augeas unknown error - Matching path _expression_ Change By: Charlie Sharpsteen Assignee: Patrick Grant Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8651) Augeas unknown error - Matching path expression
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-8651
Augeas unknown error - Matching path _expression_
Issue Type:
Bug
Affects Versions:
PUP 4.10.9
Assignee:
Unassigned
Created:
2018/04/10 7:52 AM
Priority:
Normal
Reporter:
Patrick Grant
Puppet Version: 4.10.9 Puppet Server Version: 2.6.0 OS Name/Version: AIX 7.1 This issue arose from a support ticket where a customer experiences the following error during a puppet run on one of their AIX servers.
Debug: Augeas[sshd_config](provider=augeas): Opening augeas with root /, lens path , flags 32
Debug: Augeas[sshd_config](provider=augeas): Augeas version 1.4.0 is installed
Debug: Augeas[sshd_config](provider=augeas): Closed the augeas connection
Error: /Stage[main]/Profiles::Pci_dss::Sshd_config/Augeas[sshd_config]: Could not evaluate: unknown error - Matching path _expression_ '/augeas/load/*['/etc/ssh/sshd_config/' !~ glob(incl) + regexp('/.*')]' failed
Jira (PDOC-234) remove deprecated cli options
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-234 remove deprecated cli options Issue Type: Task Assignee: Eric Putnam Created: 2018/04/10 6:32 AM Priority: Normal Reporter: Eric Putnam These emit-json options. GET 'EM OUT https://github.com/puppetlabs/puppet-strings/commit/9728d1004a6dff597fb34aa2d4c998999e4acb9d#diff-d247b2f19934e420821d364a7ff58475L19 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-454) Plans should return undef without an explicit return
Title: Message Title Henrik Lindberg commented on BOLT-454 Re: Plans should return undef without an explicit return This ticket moved to a BOLT ticket. The change needs to be made in Puppet code base (as per my first comment) - so it needs a PUP ticket to be merged... How did you see this working otherwise? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8582) Add vendor_modules to basemodulepath
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8582
Add vendor_modules to basemodulepath
Change By:
Josh Cooper
Update Append the autoloader vendored modules directory to search the {{vendor_modules}} directory when loading module content default basemodulepath visible across all environments . Pluginsync should download modules' lib directories. The compiler should be able to load types from the modules' lib directories.The vendored modules directory should have the least precedence (per-environment modulepath, global modulepath, and pluginsync libdir) should all have higher priority , so that the vendored versions can be overrridden .puppetserver: installing an updated module should override {{vendor_modules}} (from the puppet-agent package on the local host).puppet agent: pluginsynced modules should override {{vendor_modules}}puppet apply/resource: locally installed modules should override {{vendor_modules}}The modules mount must resolve files in the same way that the autoloader does so that the same type (and its respective provider) used during compilation are pluginsynced to the agent. It should be possible to remove the vendored modules directory from the either the basemodulepath or in a per-environment modulepath so that the vendored modules are ignored, eg. trying to compile a manifest should fail if the type is not installed using PMT.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8582) Add vendor_modules to basemodulepath
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8582 Add vendor_modules to basemodulepath Change By: Josh Cooper Summary: Add vendor_modules to autoloader search path basemodulepath Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8582) Add vendor_modules to autoloader search path
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8582 Add vendor_modules to autoloader search path Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8581) Extract zone type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8581 Extract zone type/provider into a module Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
