Jira (BOLT-126) Support WinRM with Kerberos
Title: Message Title Glenn Sarti commented on BOLT-126 Re: Support WinRM with Kerberos Sounds more acceptance-y (ala Beaker) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-126) Support WinRM with Kerberos
Title: Message Title Ethan Brown commented on BOLT-126 Re: Support WinRM with Kerberos If only AppVeyor could run Linux docker containers! https://github.com/criteo/kerberos-docker Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-126) Support WinRM with Kerberos
Title: Message Title Ethan Brown commented on BOLT-126 Re: Support WinRM with Kerberos I think that you can also setup the MIT Kerberos server on a standalone Windows machine without setting up a DC, though I'm not sure of the specifics. Download: http://web.mit.edu/kerberos/krb5-1.16/krb5-1.16.html Docs: http://web.mit.edu/kerberos/krb5-1.16/doc/admin/index.html Not sure if that's any more or less painful for an automated testing scenario (not sure how a DC would work in AppVeyor for instance). I wonder if it's worth just punting on the actual Kerberos testing and assuming that the winrm gem is well-tested enough? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-126) Support WinRM with Kerberos
Title: Message Title Glenn Sarti commented on BOLT-126 Re: Support WinRM with Kerberos Josh Cooper If you want to set something up temporarily in Pooler I wrote up docs https://docs.google.com/document/d/19Vo4VaRfx7rSA5WIPbYS8cvRahW9LF6kJx6cR7uzQ6w/edit?usp=sharing I also had a module I used to create a DC for PupConf 2016 https://github.com/glennsarti/glennsarti-windows_ad You'd probably want to test performing actions against a Domain Member and a Domain Controller to see if there's any difference in behaviour. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-126) Support WinRM with Kerberos
Title: Message Title Michael Smith commented on BOLT-126 Re: Support WinRM with Kerberos My plans so far: https://blogs.technet.microsoft.com/uktechnet/2016/06/08/setting-up-active-directory-via-powershell/ Kerberos setup automatically? (magic...) Profit! Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-126) Support WinRM with Kerberos
Title: Message Title Josh Cooper commented on BOLT-126 Re: Support WinRM with Kerberos Glenn Sarti thoughts? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-257) Plan docs are totally broken
Title: Message Title Michelle Fredette commented on BOLT-257 Re: Plan docs are totally broken Fixed. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-126) Support WinRM with Kerberos
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-126 Support WinRM with Kerberos Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1790) facter should compute the correct processor facts for arm64 Linux machines
Title: Message Title Eric Sorenson commented on FACT-1790 Re: facter should compute the correct processor facts for arm64 Linux machines Richard Henwood is this something you'd be willing to dig into an put up a PR for? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (HI-558) Automate smoke-test of hiera gem release artifacts
Title: Message Title Branan Riley updated an issue Hiera / HI-558 Automate smoke-test of hiera gem release artifacts Change By: Branan Riley Sprint: Platform OS Ready for Eng. Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1790) facter should compute the correct processor facts for arm64 Linux machines
Title: Message Title Branan Riley updated an issue Facter / FACT-1790 facter should compute the correct processor facts for arm64 Linux machines Change By: Branan Riley Sprint: Platform OS Ready for Eng. Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7290) Automate smoke-test of puppet gem release artifacts
Title: Message Title Branan Riley updated an issue Puppet / PUP-7290 Automate smoke-test of puppet gem release artifacts Change By: Branan Riley Sprint: Platform OS Ready for Eng. Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-6510) selmodule provider should only list modules once
Title: Message Title Branan Riley updated an issue Puppet / PUP-6510 selmodule provider should only list modules once Change By: Branan Riley Sprint: Platform OS Ready for Eng. Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3263) Architecture Parameter for Package Resource
Title: Message Title Branan Riley updated an issue Puppet / PUP-3263 Architecture Parameter for Package Resource Change By: Branan Riley Sprint: Platform OS Ready for Eng. Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1732) Facter core dump on large integers
Title: Message Title Branan Riley updated an issue Facter / FACT-1732 Facter core dump on large integers Change By: Branan Riley Sprint: Platform OS Ready for Eng. Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1762) valid networking facts in 2.x get ignored in 3.x
Title: Message Title Branan Riley updated an issue Facter / FACT-1762 valid networking facts in 2.x get ignored in 3.x Change By: Branan Riley Sprint: Platform OS Ready for Eng. Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1779) Windows 2016 container not detected as virtual=docker by facter
Title: Message Title Branan Riley updated an issue Facter / FACT-1779 Windows 2016 container not detected as virtual=docker by facter Change By: Branan Riley Sprint: Platform OS Ready for Eng. Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3802) facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3802 facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array Change By: Jeff Yarnell Sprint: Data Platform 2018-01-17 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3702) upgrade tests broken for PDB
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3702 upgrade tests broken for PDB Change By: Jeff Yarnell Sprint: Data Platform 2018-01-17 Hopper/Triage Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3560) Uncomment file-with-binary-template test once the relevant puppet pr is merged
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3560 Uncomment file-with-binary-template test once the relevant puppet pr is merged Change By: Jeff Yarnell Sprint: Hopper/Triage, Data Platform 2017-11-01, Data Platform 2017-11-15, Data Platform 2018-01-03 , Data Platform 2018-01-17 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Jacob Helwig commented on PUP-8122 Re: I18n strings that include repeated lists of sentence fragments can be hard to translate Merged into 5.3.x in e97a37d6. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3560) Uncomment file-with-binary-template test once the relevant puppet pr is merged
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3560 Uncomment file-with-binary-template test once the relevant puppet pr is merged Change By: Jeff Yarnell Sprint: Hopper/Triage, Data Platform 2017-11-01, Data Platform 2017-11-15, Data Platform 2018-01-03 , Data Platform 2018-01-17 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3702) upgrade tests broken for PDB
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3702 upgrade tests broken for PDB Change By: Jeff Yarnell Sprint: Hopper/Triage Data Platform 2018-01-17 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3311) Improve error message on "index row size" exceptions
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3311 Improve error message on "index row size" exceptions Change By: Jeff Yarnell Sprint: Hopper/Triage, Data Platform 2018-01-03, Data Platform 2017-12-13 , Data Platform 2018-01-17 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3687) ordering on fact value
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3687 ordering on fact value Change By: Jeff Yarnell Sprint: Hopper/Triage, Data Platform 2018-01-03, Data Platform 2017-12-13 , Data Platform 2018-01-17 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3770) anonymization via the "puppet db export" command not working
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3770 anonymization via the "puppet db export" command not working Change By: Jeff Yarnell Sprint: Hopper/Triage, Data Platform 2018-01-03, Data Platform 2017-12-13 , Data Platform 2018-01-17 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3560) Uncomment file-with-binary-template test once the relevant puppet pr is merged
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3560 Uncomment file-with-binary-template test once the relevant puppet pr is merged Change By: Jeff Yarnell Sprint: Hopper/Triage, Data Platform 2017-11-01, Data Platform 2017-11-15, Data Platform 2018-01-03 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3687) ordering on fact value
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3687 ordering on fact value Change By: Jeff Yarnell Sprint: Hopper/Triage, Data Platform 2018-01-03, Data Platform 2017-12-13 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3311) Improve error message on "index row size" exceptions
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3311 Improve error message on "index row size" exceptions Change By: Jeff Yarnell Sprint: Hopper/Triage, Data Platform 2018-01-03, Data Platform 2017-12-13 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3770) anonymization via the "puppet db export" command not working
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3770 anonymization via the "puppet db export" command not working Change By: Jeff Yarnell Sprint: Hopper/Triage, Data Platform 2018-01-03, Data Platform 2017-12-13 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3802) facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3802 facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 Team: Platform Core Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8308) Streamline all package installation steps for puppet
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8308 Streamline all package installation steps for puppet Change By: Melissa Stone Team: Platform Core Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8307) Investigate ec2 testing for puppet
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8307 Investigate ec2 testing for puppet Change By: Melissa Stone Team: Platform Core Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8308) Streamline all package installation steps for puppet
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8308 Streamline all package installation steps for puppet Change By: Melissa Stone We should streamline or break apart all of the package installation utilities in puppet.Remove any unneeded or unused bits, break down what we can into atomic methods, ensure all installation happens with the newer install utilities provided by beaker (i.e., puppet5), remove any calls to old installation methods that should no longer be used.The eventual goal will be to move these to beaker-puppet so they can be reused across multiple components. This will also allow us to update only one place when we switch to artifactory being the main source for packages. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8307) Investigate ec2 testing for puppet
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8307 Investigate ec2 testing for puppet Change By: Melissa Stone Puppet has code to enable ec2 testing, but the code here is very fragile. We need to figure out where this testing happens so we know the scope in which this code needs to be able to run. A lot of our newer testing utilities are necessarily only available internally. It appears we need to keep the ec2 logic executable externally as well. We should also check to see if we can make this logic available for multiple components that require it (i.e., puppet and maybe also pxp-agent). Eventually it should be moved into beaker-puppet, but only in a form that has been deemed required. Once there, we'll be able to reuse it for multiple components. This eventual goal should be kept in mind for this initial work. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8308) Streamline all package installation steps for puppet
Title: Message Title Melissa Stone created an issue Puppet / PUP-8308 Streamline all package installation steps for puppet Issue Type: Task Assignee: Unassigned Created: 2018/01/03 2:04 PM Priority: Normal Reporter: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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
Jira (PUP-8307) Investigate ec2 testing for puppet
Title: Message Title Melissa Stone created an issue Puppet / PUP-8307 Investigate ec2 testing for puppet Issue Type: Task Assignee: Unassigned Created: 2018/01/03 1:53 PM Priority: Normal Reporter: Melissa Stone Puppet has code to enable ec2 testing, but the code here is very fragile. We need to figure out where this testing happens so we know the scope in which this code needs to be able to run. A lot of our newer testing utilities are necessarily only available internally. It appears we need to keep the ec2 logic executable externally as well. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Lucy Wyman
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a node INFO:- log when an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log every sub-action taken on a node like changing a task file permissions- log connection informationINFO:- (new) Log when bolt starts run execution with object type and first argument(command, script, task or file){{Starting bolt command run $COMMAND}}{{Starting bolt task run package}} (/) - Log when actions start on nodes (happens in the {{transport.rb}}?)- (previously at debug) Log results from each action on a node (as json representation)NOTICE:- (new) log when a run_* call is starting and what the first argument(command, script, task, or file) is{{Running task package}}- (new) log when a run_* call finishes and summarize how many nodes succeeded or failed{{Ran task package on 34 nodes with 3 failures}} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (PUP-8306) Mechanism for syncing local git changes to remote testing host
Title: Message Title Melissa Stone created an issue Puppet / PUP-8306 Mechanism for syncing local git changes to remote testing host Issue Type: Task Assignee: Unassigned Created: 2018/01/03 1:49 PM Priority: Normal Reporter: Melissa Stone We need some way to sync local git changes with the host we are using to test those changes. This only applies to git-based testing. This will be very useful for iterative development. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Lucy Wyman
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a node INFO:- log when an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log every sub-action taken on a node like changing a task file permissions- log connection informationINFO:- (new) Log when bolt starts run execution with object type and first argument(command, script, task or file){{Starting bolt command run $COMMAND}}{{Starting bolt task run package}}- Log when actions start on nodes (happens in the {{transport.rb}}? ) - (previously at debug) Log results from each action on a node (as json representation)NOTICE:- (new) log when a run_* call is starting and what the first argument(command, script, task, or file) is{{Running task package}}- (new) log when a run_* call finishes and summarize how many nodes succeeded or failed{{Ran task package on 34 nodes with 3 failures}} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (PUP-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Melissa Stone created an issue Puppet / PUP-8305 Git testing should consume the runtime archive rather than install system packages Issue Type: Task Assignee: Unassigned Created: 2018/01/03 1:47 PM Priority: Normal Reporter: Melissa Stone We currently have work scheduled to build out all required runtime components (ruby, openssl, etc), and make them available to grab during build time of puppet-agent. We should be able to leverage this to make our git-based testing faster and easier as well. This will be internal only for the moment (maybe, depending on Artifactory settings, once the package is consistently shipping to Artifactory), but that's fine. We should replace the logic in 00_EnvSetup.rb that installs these runtime components from system packages with the runtime archive. This will alleviate a lot of headache for developers trying to test subcomponents with git. Add Comment
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Lucy Wyman
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a node INFO:- log when an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log every sub-action taken on a node like changing a task file permissions- log connection informationINFO:- (new) Log when bolt starts run execution with object type and first argument(command, script, task or file){{Starting bolt command run $COMMAND}}{{Starting bolt task run package}}- Log when actions start on nodes (happens in the {{transport.rb}}? - (previously at debug) Log results from each action on a node (as json representation)NOTICE:- (new) log when a run_* call is starting and what the first argument(command, script, task, or file) is{{Running task package}}- (new) log when a run_* call finishes and summarize how many nodes succeeded or failed{{Ran task package on 34 nodes with 3 failures}} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Lucy Wyman
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a node INFO:- log when an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log every sub-action taken on a node like changing a task file permissions- log connection informationINFO:- (new) Log when bolt starts run execution with object type and first argument(command, script, task or file){{Starting bolt command run $COMMAND}}{{Starting bolt task run package}} (/) - Log when actions start on nodes- (previously at debug) Log results from each action on a node (as json representation) (/) NOTICE:- (new) log when a run_* call is starting and what the first argument(command, script, task, or file) is{{Running task package}}- (new) log when a run_* call finishes and summarize how many nodes succeeded or failed{{Ran task package on 34 nodes with 3 failures}} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (PUP-8304) SeverityProducer.assert_severity isn't ever called
Title: Message Title Eric Delaney created an issue Puppet / PUP-8304 SeverityProducer.assert_severity isn't ever called Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Unassigned Created: 2018/01/03 1:07 PM Priority: Normal Reporter: Eric Delaney In the class Puppet::Pops::Validation::SeverityProducer, the method assert_severity isn't ever called by anyone in the puppet code base. 13:02 $ grep -r assert_severity . ./lib/puppet/pops/validation.rb: def assert_severity level Add Comment
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Lucy Wyman assigned an issue to Unassigned Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3802) facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array
Title: Message Title Nick Walker created an issue PuppetDB / PDB-3802 facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array Issue Type: Bug Assignee: Unassigned Created: 2018/01/03 12:53 PM Priority: Normal Reporter: Nick Walker The Problem Provided a single element array for facts-blacklist PuppetDB will not blacklist that fact. Provided a 2-element array for facts-blacklist PuppetDB will not blacklist those 2 facts. Provided a 3-element array [a, b, c] PuppetDB will only blacklist fact b. Provided a 4-element array [w, x, y, z ] PuppetDB will only blacklist fact x and y. and so on. PuppetDB seems to ignore the 1st and last element of the array provided for facts-blacklist. Add Comment
Jira (PUP-8270) PAL task_signature adds 'default' to some type descriptions
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8270 PAL task_signature adds 'default' to some type descriptions Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4963) "puppet module build" fails on FIPS-enabled system
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-4963 "puppet module build" fails on FIPS-enabled system Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8285) filebucket --bucket behavior is either inconsistent or underexplained
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8285 filebucket --bucket behavior is either inconsistent or underexplained Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8183) Update puppet device documentation for --user
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8183 Update puppet device documentation for --user Change By: Geoff Nichols Team: Modules Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8170) Add support for parsing in the PAL API
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8170 Add support for parsing in the PAL API Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8171) PAL: add support for easy checking if function or plan is callable with a given set of arguments
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8171 PAL: add support for easy checking if function or plan is callable with a given set of arguments Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8247) Parser locator doesn't cache anything and doesn't appear to work.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8247 Parser locator doesn't cache anything and doesn't appear to work. Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8212) The Variant type without any types matches in strange ways
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8212 The Variant type without any types matches in strange ways Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8283) Puppet rejects tasks with valid non-Data types like 'Hash'
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8283 Puppet rejects tasks with valid non-Data types like 'Hash' Change By: Geoff Nichols Team: Direct Change Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8043) Add test to assert that task metadata type is validated according to spec.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8043 Add test to assert that task metadata type is validated according to spec. Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8182) Lookup unique merge doesn't deduplicate with a single layer - backport PUP 7608 to 4.10.z
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8182 Lookup unique merge doesn't deduplicate with a single layer - backport PUP 7608 to 4.10.z Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1542) Install Facter 3 as a gem
Title: Message Title Louis Mayorga commented on FACT-1542 Re: Install Facter 3 as a gem Please!!! Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1542) Install Facter 3 as a gem
Title: Message Title Chris Denneen commented on FACT-1542 Re: Install Facter 3 as a gem 1,000% Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3495) acceptance pre-suite package install method should accept short SHA
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3495 acceptance pre-suite package install method should accept short SHA Change By: Josh Cooper Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-3495) acceptance pre-suite package install method should accept short SHA
Title: Message Title Josh Cooper commented on PUP-3495 Re: acceptance pre-suite package install method should accept short SHA In the future (PUP-8268), we will no longer need to supply the SUITE_VERSION during install for AIO packages. But we still require the full SHA in order to find the build data file. We could try to figure that out based on the local checkout, but it gets complicated if you're setting SERVER or FORK to install from somewhere else. Going to close this as won't fix. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-1542) Install Facter 3 as a gem
Title: Message Title Trevor Vaughan commented on FACT-1542 Re: Install Facter 3 as a gem Happy New Year - We all still want this! Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-5987) Documentation for logdest is confusing
Title: Message Title Eric Delaney commented on PUP-5987 Re: Documentation for logdest is confusing Tested passed: SHA=1d90274de8f5a1ea7cb8463e465e607a47522274 SUITE_VERSION=1.10.8.140.g1d90274 [-l|--logdest syslog|eventlog||console] [--noop] SHA=4226c83bb08f3dd92dc92e9c39190ea38123792c SUITE_VERSION=5.3.3.154.g4226c83 [-l|--logdest syslog|eventlog||console] [--noop] master SHA=de540d2ba023183f6c7a65b3d16ca867e98516df SUITE_VERSION=5.3.3.379.gde540d2 [-l|--logdest syslog|eventlog||console] [--noop] Add Comment
Jira (PUP-7861) beaker instructions at ./acceptance/readme seem to be wrong
Title: Message Title Josh Cooper commented on PUP-7861 Re: beaker instructions at ./acceptance/readme seem to be wrong Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/f02ce862bbb9380fe3307d9eb33d04fb0598b262 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4065) errors/warnings in environment.conf should not be duplicated
Title: Message Title
Eric Delaney commented on PUP-4065
Re: errors/warnings in environment.conf should not be duplicated
Tested: SHA=1d90274de8f5a1ea7cb8463e465e607a47522274 SUITE_VERSION=1.10.8.140.g1d90274
[root@n80bqn063hdd1uu ~]# echo "parser = crazy" >> /etc/puppetlabs/code/environments/production/environment.conf
[root@n80bqn063hdd1uu ~]# puppet apply -e 'notify("yep")'
Warning: Invalid settings in environment.conf at '/etc/puppetlabs/code/environments/production/environment.conf'. The following unknown setting(s) are being ignored: parser
(file & line not available)
Error: Evaluation Error: Unknown function: 'notify'. at line 1:1 on node n80bqn063hdd1uu.delivery.puppetlabs.net
[root@n80bqn063hdd1uu ~]#
SHA=4226c83bb08f3dd92dc92e9c39190ea38123792c SUITE_VERSION=5.3.3.154.g4226c83
[root@xly40a0h6ra9fgm ~]# puppet --version
5.3.4
Jira (BOLT-290) Decompose --insecure flag
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Issue Type: Improvement Assignee: Unassigned Created: 2018/01/03 10:53 AM Priority: Normal Reporter: Alex Dreyer The --insecure flag has a different meaning for different transports and is not specific enough for future features. SSH: For ssh we should replace the --insecure flag with --no-host-key-check. In the config we should expose a host-key-check option that defaults to true. WINRM: for the winrm transport we should replace - insecure with --ssl/ -no-ssl on the commandline. In the config we should have a single ssl option that defaults to to true. Add Comment
Jira (BOLT-289) Standardize Target object
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-289 Standardize Target object Issue Type: Task Assignee: Unassigned Created: 2018/01/03 10:48 AM Priority: Normal Reporter: Alex Dreyer The Target datatype from puppet was moved into bolt. We should move the NodeURI logic into Target and update the Executor and Node classes to interact with targets objects. Changes: The Target class should be updated to expose the expected accessors. The Target class should have a from_url class method to create a Target from a url. unspecified options should be nil The Target class should have a parse_urls class method to create an array of Target objects from a --nodes argument. The Node initializer should take a single target object and save it instead of saving various options from config and the url separately. It should pass the target and config to an update_target method to apply transport defaults and configuration. Bolt::Node.from_uri should become Bolt::Node.from_target The executor should accept a list of target objects.
Jira (PUP-5494) Proper manual pages are nonexistent
Title: Message Title Garrett Guillotte commented on PUP-5494 Re: Proper manual pages are nonexistent With Kylo gone, this probably should be reassigned. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-277) SSL default makes winrm harder to use
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-277 SSL default makes winrm harder to use Change By: Alex Dreyer * Inline help still says "winrm://" default is 5985 ... its not anymore and is now 5986, so that should probably change accordingly * The --insecure help note is not super helpful for Windows people - its necessary . This should be updated to switch to specify the port 5985 when doing something like --node winrm://foo:bar@host changes based on whether ssl is used . com ... but you'd never know that * The error message without --insecure specified doesn't point users in the right direction - it just says basically "Connection Refused" on port 5986, which Windows users won't know what to do with IMHO . When we are using the default port and trying over SSL we should inform the user that we are trying tWhen we are using ssl and try on 5986 and the port is not open we should inform the user ssl may not be available on the target.When the user specifies a port and it's not SSL we should inform the user ssl is not available on the specified port. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8268) Install packages using beaker-puppet's puppet5 methods
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8268 Install packages using beaker-puppet's puppet5 methods Change By: Josh Cooper Assignee: Melissa Stone Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7861) beaker instructions at ./acceptance/readme seem to be wrong
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-7861 beaker instructions at ./acceptance/readme seem to be wrong Change By: Josh Cooper Assignee: Melissa Stone Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7482) Agent sends wrong content-type when using http file sources
Title: Message Title Josh Cooper assigned an issue to Kris Bosland Puppet / PUP-7482 Agent sends wrong content-type when using http file sources Change By: Josh Cooper Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-5987) Documentation for logdest is confusing
Title: Message Title Josh Cooper assigned an issue to Eric Delaney Puppet / PUP-5987 Documentation for logdest is confusing Change By: Josh Cooper Assignee: Garrett Guillotte Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4065) errors/warnings in environment.conf should not be duplicated
Title: Message Title Josh Cooper assigned an issue to Eric Delaney Puppet / PUP-4065 errors/warnings in environment.conf should not be duplicated Change By: Josh Cooper Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8182) Lookup unique merge doesn't deduplicate with a single layer - backport PUP 7608 to 4.10.z
Title: Message Title Josh Cooper commented on PUP-8182 Re: Lookup unique merge doesn't deduplicate with a single layer - backport PUP 7608 to 4.10.z Merged to 5.3.x in https://github.com/puppetlabs/puppet/commit/c11ddbea4c and master in https://github.com/puppetlabs/puppet/commit/eefdfd2276 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-285) Bolt should handle parser errors better
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-285 Bolt should handle parser errors better Change By: David Kramer Sub-team: bolt Bolt Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-285) Bolt should handle parser errors better
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-285 Bolt should handle parser errors better Change By: David Kramer Sprint: Bolt Kanban Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-7510) FIPS-Enabled Puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7510 FIPS-Enabled Puppet Change By: Josh Cooper Fix Version/s: PUP 4.10.10 Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8298) Add new issue type INVALID_TASK_NAME
Title: Message Title David Kramer updated an issue Puppet / PUP-8298 Add new issue type INVALID_TASK_NAME Change By: David Kramer Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8298) Add new issue type INVALID_TASK_NAME
Title: Message Title David Kramer updated an issue Puppet / PUP-8298 Add new issue type INVALID_TASK_NAME Change By: David Kramer Sub-team: Bolt Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8292) Bad Markdown in 'unique' function breaks Strings-generated reference
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8292 Bad Markdown in 'unique' function breaks Strings-generated reference Change By: Josh Cooper Fix Version/s: PUP 5.3.4 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8292) Bad Markdown in 'unique' function breaks Strings-generated reference
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8292 Bad Markdown in 'unique' function breaks Strings-generated reference Change By: Josh Cooper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8292) Bad Markdown in 'unique' function breaks Strings-generated reference
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8292 Bad Markdown in 'unique' function breaks Strings-generated reference Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8292) Bad Markdown in 'unique' function breaks Strings-generated reference
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8292 Bad Markdown in 'unique' function breaks Strings-generated reference Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8292) Bad Markdown in 'unique' function breaks Strings-generated reference
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8292 Bad Markdown in 'unique' function breaks Strings-generated reference Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-288) unable to install bolt
Title: Message Title robert rapelje updated an issue Puppet Task Runner / BOLT-288 unable to install bolt never mind, please close Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-288) unable to install bolt
Title: Message Title robert rapelje created an issue Puppet Task Runner / BOLT-288 unable to install bolt Issue Type: Bug Affects Versions: BOLT 0.6.0 Assignee: Unassigned Components: CLI Created: 2018/01/03 8:33 AM Environment: root@bolt-client-1 ~]# uname -a Linux bolt-client-1 3.10.0-693.11.1.el7.x86_64 #1 SMP Mon Dec 4 23:52:40 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [root@bolt-client-1 ~]# ruby --version ruby 2.0.0p648 (2015-12-16) [x86_64-linux] Google CentOS 7 virtual machine [root@bolt-client-1 etc]# cat centos-release CentOS Linux release 7.4.1708 (Core) Priority: Normal Reporter: robert rapelje This document instructs the reader to install bolt 0.6.0.gem https://tickets.puppetlabs.com/browse/BOLT-193 Error message is received and I am unable to install bolt gem install
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-266
Log run_* actions when called from a plan
Change By:
Lucy Wyman
Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a node INFO:- log when an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log every sub-action taken on a node like changing a task file permissions- log connection informationINFO:- (new) Log when bolt starts run execution with object type and first argument(command, script, task or file){{Starting bolt command run $COMMAND}}{{Starting bolt task run package}} (/) - Log when actions start on nodes- (previously at debug) Log results from each action on a node (as json representation) (/)NOTICE:- (new) log when a run_* call is starting and what the first argument(command, script, task, or file) is{{Running task package}}- (new) log when a run_* call finishes and summarize how many nodes succeeded or failed{{Ran task package on 34 nodes with 3 failures}} h2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug
Add Comment
Jira (PUP-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml
Title: Message Title Andrés Núñez Veiga updated an issue Puppet / PUP-8227 Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml Change By: Andrés Núñez Veiga Sprint: SCR 2017-12-13, SCR 2018-01-03 , SCR 2018-01-17 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml
Title: Message Title Steve Quin updated an issue Puppet / PUP-8227 Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml Change By: Steve Quin Sprint: SI Backlog - DAVIS, SCR 2017-12-13, SCR 2018-01-03 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8227) Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml
Title: Message Title Andrés Núñez Veiga updated an issue Puppet / PUP-8227 Enforcement via 'puppet resource/apply' overwrites transactionstore.yaml Change By: Andrés Núñez Veiga Sprint: SI Backlog - DAVIS, SCR 2017-12-13, SCR 2018-01-03 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8259) PAL list_tasks doesn't return useful results unless all task metadata is valid
Title: Message Title Thomas Hallgren assigned an issue to Michael Smith Puppet / PUP-8259 PAL list_tasks doesn't return useful results unless all task metadata is valid Change By: Thomas Hallgren Assignee: Thomas Hallgren Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-5494) Proper manual pages are nonexistent
Title: Message Title J.D. Welch updated an issue Puppet / PUP-5494 Proper manual pages are nonexistent Change By: J.D. Welch UX Contact: J.D. Welch Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.
