Jira (PUP-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-8939 Administrators are not able to run puppet agent when installed as SYSTEM in some cases Change By: Glenn Sarti Release Notes: Not Needed 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-820) bolt_shim module is not enough to effectively start with bolt
Title: Message Title Dylan Ratcliffe created an issue Puppet Task Runner / BOLT-820 bolt_shim module is not enough to effectively start with bolt Issue Type: Bug Affects Versions: BOLT 0.21.8 Assignee: Unassigned Components: DOCS, UX Created: 2018/08/29 6:01 PM Priority: Normal Reporter: Dylan Ratcliffe When users follow the documentation to integrate bolt with PE, it tells them to install the bolt_shim module. This is however not enough to get Bolt working correctly. Almost all of the examples in the documentation won't work because they rely on more than just the tasks that come from that module. New users shouldn't have to understand all of this to get it working. Here's some suggestions for fixing this: Create dependencies on the bolt_shim module for all the other modules Document what other modules are required Both^?
Jira (BOLT-796) Document how bundled content can be overridden
Title: Message Title Dylan Ratcliffe commented on BOLT-796 Re: Document how bundled content can be overridden It's also important that this is not only documented but also standardised and released carefully as people using PXP will need to replicate the Bolt Puppetfile on their master. If it's undocumented it will be a pain but also if it changes drastically every release this will be painful 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-1879) Duplicate facts without weight should emit a warning
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-1879 Duplicate facts without weight should emit a warning Change By: Jarret Lavallee 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 (FACT-1879) Duplicate facts without weight should emit a warning
Title: Message Title
Jarret Lavallee updated an issue
Facter / FACT-1879
Duplicate facts without weight should emit a warning
Change By:
Jarret Lavallee
Based on the documentation in https://puppet.com/docs/facter/3.9/custom_facts.html#fact-precedence, the first fact that returns a non {{nil}} value will be used. It does not mention the order in which the facts are loaded , which indicates that it may be inconsistent . This can lead to unexpected behavior if there are multiple declarations of the same fact with the same name. The issue comes in when it is not known that there are multiple versions of the same fact, which can lead to confusion and wasted effort trying to identify why the fact is not working as written. This can happen when installing forge modules, or when multiple developers/development teams are working in the same environment. As a puppet user, I would like to be notified when there are multiple versions of a fact with the same weight to alert me that a change is needed.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1879) Duplicate facts without weight should emit a warning
Title: Message Title Jarret Lavallee created an issue Facter / FACT-1879 Duplicate facts without weight should emit a warning Issue Type: Improvement Affects Versions: FACT 3.9.6 Assignee: Unassigned Created: 2018/08/29 5:33 PM Labels: maintenance triage Priority: Normal Reporter: Jarret Lavallee Based on the documentation in https://puppet.com/docs/facter/3.9/custom_facts.html#fact-precedence, the first fact that returns a non nil value will be used. It does not mention the order in which the facts are loaded, which indicates that it may be inconsistent. This can lead to unexpected behavior if there are multiple declarations of the same fact with the same name. The issue comes in when it is not known that there are multiple versions of the same fact, which can lead to confusion and wasted effort trying to identify why the fact is not working as written. This can happen when installing forge modules, or when multiple developers/development teams are working in the same environment. As a puppet user, I would like to be notified when there are multiple versions of a fact with the same weight to alert me that a change is needed.
Jira (PUP-9079) Rich data tags __ptype and __pvalue must not be allowed as attribute names
Title: Message Title
Henrik Lindberg commented on PUP-9079
Re: Rich data tags __ptype and __pvalue must not be allowed as attribute names
Tony Vu No, it means that the Object type needs to raise an error if someone tries to create an Object that has _ptype or _pvalue as attribute names - ie. in something like:
type Car = Object[attributes => {__ptype => String}]
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-7582) Make attempt to export or virtualize a class an error
Title: Message Title Henrik Lindberg commented on PUP-7582 Re: Make attempt to export or virtualize a class an error Eric Sorenson If you wanted this, but thought it would be complicated... it is a very simple change. (A "won't fix" is fine too, just wanted to let you know it is not hard to change since it is already configurable). 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-794) Unable to call a task with a Sensitive string
Title: Message Title Nick Maludy commented on BOLT-794 Re: Unable to call a task with a Sensitive string Talking with Nick and Alex, i think we want to limit the scope to simply: declare a parameter as sensitive in task metadata via the property "sensitive": true. This would ensure any input for that type is obfuscated in Bolt logs (except when --debug is passed). 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-751) Move file_upload function to upload_file
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-751 Move file_upload function to upload_file Change By: Nick Lewis 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-4044) (maint) Add packaging bootstrap/implode warnings
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4044 (maint) Add packaging bootstrap/implode warnings Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 4:14 PM Priority: Normal Reporter: gepetto-bot Since we have lots of different parts of our infrastructure which still use package:implode and package:bootstrap we cannot exactly remove them entirely yet. This commit adds empty warnings back in order to make sure that the tasks don't fail during any of our pipelines. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4045) (maint) Add packaging bootstrap/implode warnings
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4045 (maint) Add packaging bootstrap/implode warnings Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 4:14 PM Priority: Normal Reporter: gepetto-bot Since we have lots of different parts of our infrastructure which still use package:implode and package:bootstrap we cannot exactly remove them entirely yet. This commit adds empty warnings back in order to make sure that the tasks don't fail during any of our pipelines. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4046) Maint/5.2.x/stub packaging implode bootstrap
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4046 Maint/5.2.x/stub packaging implode bootstrap Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 4:14 PM Priority: Normal Reporter: gepetto-bot 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 (PDB-4043) (maint) Add packaging bootstrap/implode warnings
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4043 (maint) Add packaging bootstrap/implode warnings Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 4:08 PM Priority: Normal Reporter: gepetto-bot Since we have lots of different parts of our infrastructure which still use package:implode and package:bootstrap we cannot exactly remove them entirely yet. This commit adds empty warnings back in order to make sure that the tasks don't fail during any of our pipelines. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-264) Errors output on stdout, not stderr
Title: Message Title Nick Miller created an issue Puppet Strings / PDOC-264 Errors output on stdout, not stderr Issue Type: Bug Assignee: Unassigned Components: CLI Created: 2018/08/29 4:07 PM Environment: Run `puppet strings generate --format json` in puppetlabs/postgresql version 5.8.0 and look at the first two lines returned, they are not json, but errors. Priority: Normal Reporter: Nick Miller When puppet strings throws errors, it does so on stdout instead of stderr. If you use `--format json`, then this breaks the json object. Add Comment
Jira (BOLT-750) Remove puppetlabs-apply from bolt
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-750 Remove puppetlabs-apply from bolt Change By: Nick Lewis 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 (PUP-5921) Deprecate source_permissions
Title: Message Title Jim Richardson commented on PUP-5921 Re: Deprecate source_permissions Yes I agree with you now I matter of fact I learned that in puppet class yesterday. On Wed, Aug 29, 2018, 12:05 PM Josh Cooper (JIRA) < 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-4042) Test merge master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4042 Test merge master Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 3:17 PM Priority: Normal Reporter: gepetto-bot 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.
Jira (PUP-6165) it should not be possible to disable manifest ordering
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6165 it should not be possible to disable manifest ordering Change By: Josh Cooper Sprint: Platform Core Hopper 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-6165) it should not be possible to disable manifest ordering
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6165 it should not be possible to disable manifest ordering Change By: Josh Cooper Team: Platform Core Coremunity 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-9065) Applying cached catalogs should read in deferred functions
Title: Message Title Tony Vu assigned an issue to Tony Vu Puppet / PUP-9065 Applying cached catalogs should read in deferred functions Change By: Tony Vu Assignee: Tony Vu 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-789) Ship with Ruby 2.5, OpenSSL 1.1.0
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-789 Ship with Ruby 2.5, OpenSSL 1.1.0 Change By: Michael Smith Puppet 6 has decided they're going to ship with Ruby 2.5, and done all the prep work for us. We should bump Bolt to use Ruby 2.5 for any performance boosts this might give. Also bump OpenSSL to 1.1.0 to keep pace. 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-809) Make max_threads configurable for bolt-server
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-809 Make max_threads configurable for bolt-server 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-789) Ship with Ruby 2.5, OpenSSL 1.1.0
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-789 Ship with Ruby 2.5, OpenSSL 1.1.0 Change By: Michael Smith Summary: Ship with Ruby 2.5 , OpenSSL 1.1.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 (BOLT-809) Make max_threads configurable for bolt-server
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-809 Make max_threads configurable for bolt-server 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 (PDB-4041) Test merge 5.2.x
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4041 Test merge 5.2.x Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 1:10 PM Priority: Normal Reporter: gepetto-bot 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.
Jira (PUP-7582) Make attempt to export or virtualize a class an error
Title: Message Title Eric Sorenson commented on PUP-7582 Re: Make attempt to export or virtualize a class an error I think we're out of time on this one and it seems very low risk to leave it. I'm just gonna close/wontfix. 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-6165) it should not be possible to disable manifest ordering
Title: Message Title Eric Sorenson commented on PUP-6165 Re: it should not be possible to disable manifest ordering +1 to making this the only option; we made the ordering algorithm pluggable in https://projects.puppetlabs.com/issues/18508 , theoretically to allow different algorithms like a "fuzzer" random order. But nobody ever used this AFAIK and I agree with RI that it'd be good to have a guarantee that it's always on in Puppet 6 and above. 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-8833) Create the CI pipeline
Title: Message Title Josh Cooper commented on PUP-8833 Re: Create the CI pipeline I added the jenkins view for adhoc, release and master, and created the release branch (at the same sha as master is currently) 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-9091) Change deprecation warning for illegal top level constructs to an error
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9091 Change deprecation warning for illegal top level constructs to an error Change By: Josh Cooper Sprint: Platform Core Hopper 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-9091) Change deprecation warning for illegal top level constructs to an error
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9091 Change deprecation warning for illegal top level constructs to an error Change By: Josh Cooper Team: Coremunity 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-1434) Disallow manifests from declaring things outside the namespace implied by their filenames
Title: Message Title Kris Bosland updated an issue Puppet / PUP-1434 Disallow manifests from declaring things outside the namespace implied by their filenames Change By: Kris Bosland 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-1434) Disallow manifests from declaring things outside the namespace implied by their filenames
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Work for this ticket is being done in PUP-8894, PUP-9020 (Puppet 5.5.x deprecation warnings); PUP-4242 and PUP-9091 (Puppet 6.0.0 errors). Puppet / PUP-1434 Disallow manifests from declaring things outside the namespace implied by their filenames Change By: Kris Bosland Resolution: Duplicate Assignee: Kris Bosland Status: Accepted Closed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9091) Change deprecation warning for illegal top level constructs to an error
Title: Message Title Kris Bosland created an issue Puppet / PUP-9091 Change deprecation warning for illegal top level constructs to an error Issue Type: Improvement Assignee: Kris Bosland Created: 2018/08/29 12:01 PM Fix Versions: PUP 6.0.0 Priority: Normal Reporter: Kris Bosland Illegal top level constructs have been given a deprecation warning in Puppet 5.5.x with PUP-9020, now in Puppet 6.0.0 they should be reported as an error. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-794) Unable to call a task with a Sensitive string
Title: Message Title Michael Smith commented on BOLT-794 Re: Unable to call a task with a Sensitive string I don't think we ended up with the behavior we wanted. What I think we want is to work is declare a parameter as sensitive in task metadata via the property "sensitive": true. This would ensure any input for that type is obfuscated in Bolt logs. It would accept either input matching the declared type, or input of the declared type wrapped in a call to Sensitive(...). for a parameter not marked sensitive in task metadata, accept input of the declared type wrapped in a call to Sensitive(...) and ensure it's obfuscated in Bolt logs. Being wrapped in Sensitive(...) is assumed to obfuscate it in any other plan output as a property of the Puppet language. declaring a parameter to have the type Sensitive in metadata would not be allowed, as this wouldn't work with PE. These properties allow a task author or a plan author to ensure input is obfuscated, without having to modify parts not under their control. What we ended up with is if a parameter is marked "sensitive": true, then input is obfuscated. the type passed must match the type declared in task metadata, so if input is wrapped in a call to Sensitive(...) then the parameter type must also be declared as Sensitive. Those properties mean that the task and plan authors have to be aligned about whether or not the type is wrapped with Sensitive(...). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9079) Rich data tags __ptype and __pvalue must not be allowed as attribute names
Title: Message Title Tony Vu commented on PUP-9079 Re: Rich data tags __ptype and __pvalue must not be allowed as attribute names Thomas Hallgren does this mean that the PCORE_TYPE_KEY in serialization needs to change? 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-4867) Puppets modulepath setting should be made into separate settings for distmoduledir / sitemoduledir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4867 Puppets modulepath setting should be made into separate settings for distmoduledir / sitemoduledir Change By: Josh Cooper Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 7.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-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title
Josh Cooper commented on PUP-8896
Re: Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
$ tree ~/.puppetlabs/etc/code/environments/production/modules/pup8896
/Users/josh/.puppetlabs/etc/code/environments/production/modules/pup8896
└── manifests
├── foo
│ └── bar
│ └── types
│ └── baz.pp
└── init.pp
$ find ~/.puppetlabs/etc/code/environments/production/modules/pup8896 -type f -exec cat {} \; -print
class pup8896::foo::bar::types::baz() {
notify { 'in baz': }
}
/Users/josh/.puppetlabs/etc/code/environments/production/modules/pup8896/manifests/foo/bar/types/baz.pp
Jira (PUP-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title Josh Cooper commented on PUP-8896 Re: Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load Closing this as a dup 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-8896) Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load
Title: Message Title Josh Cooper commented on PUP-8896 Re: Modules with manifest directories containing 'manifests', 'functions', 'types' or 'plans' fail to load This was fixed in https://github.com/puppetlabs/puppet/commit/44c4ea06f5c5fd172dcc50b189548209b8ab890f#diff-fcdcebff8dbdf5277e916cc78e22320bR608 as part of PUP-4242. We calculate the relative path from one of the module path entries, instead of ascending the path. $ git rev-parse HEAD ce6d50daa45484ab6033d0121b0af6f7ddd3c04b $ bx puppet apply -e "include pup8896" Warning: Unacceptable location. The name 'pup8896::foo::bar::types::baz' is unacceptable in file '/Users/josh/.puppetlabs/etc/code/environments/production/modules/pup8896/manifests/foo/bar/types/baz.pp' (file: /Users/josh/.puppetlabs/etc/code/environments/production/modules/pup8896/manifests/foo/bar/types/baz.pp, line: 1, column: 1) Notice: Compiled catalog for localhost in environment production in 0.03 seconds Notice: in baz Notice: /Stage[main]/Pup8896::Foo::Bar::Types::Baz/Notify[in baz]/message: defined 'message' as 'in baz' Notice: Applied catalog in 0.01 seconds But it's resolved in the commit after: $ git rev-parse HEAD
Jira (PUP-9013) password_max_age is incorrectly set when using a value of -1
Title: Message Title Jarret Lavallee commented on PUP-9013 Re: password_max_age is incorrectly set when using a value of -1 I was doing some digging into this and it looks like the data returned from the system tools is different from what is in the shadow file. Below is an example on CentOS 6.10 using shadow-utils-4.1.5.1-5.el6.x86_64 and libuser-0.56.13-8.el6_7.x86_64. The /etc/shadow has "-1" as the max password, but any util on the system that reads it reports the value as "4294967295". [root@t8nnztlmi0quqg3 ~]# chage -l blah Last password change : Aug 29, 2018 Password expires : never Password inactive : never Account expires : never Minimum number of days between password change : 0 Maximum number of days between password change : 4294967295 Number of days of warning before password expires : 7 [root@t8nnztlmi0quqg3 ~]# grep blah /etc/shadow blah:!!:17772:0:-1:7::: [root@t8nnztlmi0quqg3 ~]# getent shadow blah blah:!!:17772:0:4294967295:7:::
Jira (PDB-4032) Bump puppet-agent packaging dep to 5.99.0
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4032 Bump puppet-agent packaging dep to 5.99.0 Change By: Zachary Kent Assignee: Zachary Kent 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-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Josh Cooper assigned an issue to Kris Bosland Puppet / PUP-4242 Add errors for manifests declaring things in wrong namespace Change By: Josh Cooper Assignee: Kris Bosland 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-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Josh Cooper commented on PUP-4242 Re: Add errors for manifests declaring things in wrong namespace Kris Bosland Can you add release notes? 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-4032) Bump puppet-agent packaging dep to 5.99.0
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4032 Bump puppet-agent packaging dep to 5.99.0 Change By: Josh Cooper Team: PuppetDB 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-8529) Remove data_binding_terminus setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8529 Remove data_binding_terminus setting Change By: Josh Cooper Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 7.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 (BOLT-794) Unable to call a task with a Sensitive string
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-794 Unable to call a task with a Sensitive string Change By: David Kramer 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 (PUP-7433) Restructure Gemfile to use different group names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7433 Restructure Gemfile to use different group names Change By: Josh Cooper Release Notes Summary: Restructure puppet's Gemfile so that bundler installs puppet's runtime, feature-related, and test dependencies by default. The development and documentation groups can be installed using: bundle install --with development documentation. Release Notes: Bug Fix 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-7433) Restructure Gemfile to use different group names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7433 Restructure Gemfile to use different group names Change By: Josh Cooper 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-7433) Restructure Gemfile to use different group names
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-7433 Restructure Gemfile to use different group names Change By: Josh Cooper Assignee: Josh Cooper 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-7433) Restructure Gemfile to use different group names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7433 Restructure Gemfile to use different group names 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 (PDB-4040) Merge 5.2.x -> master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4040 Merge 5.2.x -> master Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 10:07 AM Priority: Normal Reporter: gepetto-bot 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 (PUP-5921) Deprecate source_permissions
Title: Message Title
Josh Cooper commented on PUP-5921
Re: Deprecate source_permissions
There is no way to have non executable files in a recursive file definition since directories must have execute permissions.
That's not quite true. If you set the mode to 0640 for the initial directory, then puppet will make sure all directories are also executable. For example given:
class recurse {
file { '/tmp/recurse':
ensure => directory,
mode=> '640',
recurse => true,
source => 'puppet:///modules/recurse',
}
}
Where the module contains:
# tree -p /etc/puppetlabs/code/environments/production/modules/recurse/files
/etc/puppetlabs/code/environments/production/modules/recurse/files
Jira (PUP-9069) Add support for RHEL 8 in systemd provider
Title: Message Title Branan Riley assigned an issue to Unassigned Puppet / PUP-9069 Add support for RHEL 8 in systemd provider Change By: Branan Riley Assignee: Emilien Macchi 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-9069) Add support for RHEL 8 in systemd provider
Title: Message Title Branan Riley updated an issue Puppet / PUP-9069 Add support for RHEL 8 in systemd provider Change By: Branan Riley Sprint: Platform OS 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-9069) Add support for RHEL 8 in systemd provider
Title: Message Title Branan Riley updated an issue Puppet / PUP-9069 Add support for RHEL 8 in systemd provider Change By: Branan Riley Team: Platform OS 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-9090) Puppet apply causes a Stack Level too deep on Windows (include function)
Title: Message Title Josh Cooper commented on PUP-9090 Re: Puppet apply causes a Stack Level too deep on Windows (include function) My guess is that powershell is causing the current drive and/or working directory to be resolved differently casewise and perhaps the pops recursion guard doesn't detect when infinite recursion occurs due to case mismatch? For example I see both C:\Source and C:\source above. Also things like PUP-6985 or how the win32-dir gem rewrites the Dir.pwd method to retrieve the current working directly differently than how ruby does it. https://github.com/chef/win32-dir/blob/ffi/lib/win32/dir.rb#L150-L182 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-819) Documentation of valid '--nodes' values is unclear
Title: Message Title Michael Smith commented on BOLT-819 Re: Documentation of valid '--nodes' values is unclear https://puppet.com/docs/bolt/0.x/bolt_options.html#specify-nodes-in-the-command-line gets into how to do brace expansion to cover several similar names. We should probably augment that page to mention what can be used there: protocol://user:password@host:port, or inventory group name. Some of the details around IP addresses are captured in https://puppet.com/docs/bolt/0.x/bolt_command_reference.html#command-options. 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-819) Documentation of valid '--nodes' values is unclear
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-819 Documentation of valid '--nodes' values is unclear Change By: Lucy Wyman Summary: Documentation of valid '--nodes' values is unclear Sprint: Bolt Kanban Method Found: Needs Assessment Customer Feedback 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-754) Add a cert whitelist to bolt-server
Title: Message Title Lucy Wyman assigned an issue to Unassigned Puppet Task Runner / BOLT-754 Add a cert whitelist to bolt-server Change By: Lucy Wyman Assignee: 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-819) Documentation of valid '--nodes' values is unclear
Title: Message Title Lucy Wyman commented on BOLT-819 Re: Documentation of valid '--nodes' values is unclear Thanks for bringing this to our attention Lee Lowder! I moved it into our current sprint - seems like it'll be quick to fix. 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 Eric Sorenson commented on PUP-8094 Re: Lookup ignores environment from the classifier when using rule with trusted facts The user need for lookup is to simulate, as closely as possible, the values that a node will get when a catalog is compiled for it. Therefore, lookup should behave as similar to the catalog compilation data flow as possible – including the fact that the ENC would be authoritative for the environment. Am I missing something? 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 Henrik Lindberg commented on PUP-8094 Re: Lookup ignores environment from the classifier when using rule with trusted facts Eric Sorenson See my comment above There is a choice between using a) "current/given env" (what it does now) or b) "the env it would switch to" (what was asked in this ticket), or c) or some other combination because just switching to b) isn't quite right either since it depends on why you are looking up; is it for debugging "the values you got", or "the values you will get". At the same time, it is not right to just get values from ENC but ignore what it says about env, since the other things ENC gives may then be completely wrong. So, something needs to be done about this - but what? So - no clear path yet. 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-819) Documentation unclear
Title: Message Title Lee Lowder created an issue Puppet Task Runner / BOLT-819 Documentation unclear Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 5:34 AM Priority: Normal Reporter: Lee Lowder The documentation around the --nodes param is unclear. All the examples only show host names being used, but the help output and https://puppet.com/docs/bolt/0.x/bolt_command_reference.html#command-options have a note about IPv6 addresses, with and without ports. No where that I could find does it explicitly state that `–nodes` can take IP addresses as arguments, though in my testing, using IPv4 addresses did actually work. The docs and examples should be clarified around this, and also state explicitly if it is expected what you can use for the nodes list - names, iipv4, ipv6,and / or a mixture of the three, as well as what sort of globbing or regex type functions are available. For example, if all the IP addresses I need to specify share 3 of 4 elements in their dotted quad, is there a way from the command line to easily specify this and just list out the last portion for those nodes? Add Comment
Jira (PUP-9090) Puppet apply causes a Stack Level too deep on Windows (include function)
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-9090 Puppet apply causes a Stack Level too deep on Windows (include function) Change By: Glenn Sarti Environment: Windows 10 - 1803Ruby 2.4.3-2 x64Puppet Gem 5.5.6 x64 (No agent or master) 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-9090) Puppet apply causes a Stack Level too deep on Windows (include function)
Title: Message Title Glenn Sarti commented on PUP-9090 Re: Puppet apply causes a Stack Level too deep on Windows (include function) And just to prove it's not URU, I used the path instead of URU CMD -> PowerShell -> CD to correct Dir -> SET PATH - STACK TOO DEEP (BAD!) CMD -> CD to correct Dir -> Powershell -> SET PATH - EVALUATION ERROR (Good) Microsoft Windows [Version 10.0.17134.228] (c) 2018 Microsoft Corporation. All rights reserved. C:\Users\glenn.sarti>powershell Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. Loading personal and system profiles took 1872ms. C:\Users\glenn.sarti> cd \source\tmp\wtf C:\source\tmp\wtf> $ENV:PATH = 'C:\tools\ruby2.4.3-2x64\bin;' + $ENV:PATH C:\source\tmp\wtf> be puppet apply .\langserver-sidecar20180828-13160-1pngrjb Error: Could not run: stack level too deep
Jira (PUP-9090) Puppet apply causes a Stack Level too deep on Windows (include function)
Title: Message Title Glenn Sarti commented on PUP-9090 Re: Puppet apply causes a Stack Level too deep on Windows (include function) What the ?Unable to render embedded object: File (@?#@?@#) not found.? CMD -> PowerShell -> CD to correct Dir -> URU - STACK TOO DEEP (BAD!) CMD -> CD to correct Dir -> Powershell -> URU - EVALUATION ERROR (Good) icrosoft Windows [Version 10.0.17134.228] (c) 2018 Microsoft Corporation. All rights reserved. C:\Users\glenn.sarti>powershell Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. Loading personal and system profiles took 1811ms. C:\Users\glenn.sarti> cd \source\tmp\wtf C:\source\tmp\wtf> uru 2.4 ---> these rubies match your `2.4` tag: [1] 2.4.3-2-x64 : ruby 2.4.3p205 (2017-12-14 revision 61247)
Jira (PUP-9090) Puppet apply causes a Stack Level too deep on Windows (include function)
Title: Message Title Glenn Sarti commented on PUP-9090 Re: Puppet apply causes a Stack Level too deep on Windows (include function) Also tried combinations of Elevated vs Non-Elevated. No change in test scenarios. Hrmm interesting. (URU is the ruby manager on Windows) So running; CMD -> URU -> PowerShell - EVALUATION ERROR (Good) CMD -> PowerShell -> URU - STACK TOO DEEP (BAD!) CMD -> Change PATH -> PowerShell - STACK TOO DEEP (BAD!) CMD -> Change PATH -> (Run puppet apply) -> PowerShell - EVALUATION ERROR (Good) (!?@#!@$!) 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-9090) Puppet apply causes a Stack Level too deep on Windows (include function)
Title: Message Title Glenn Sarti created an issue Puppet / PUP-9090 Puppet apply causes a Stack Level too deep on Windows (include function) Issue Type: Bug Assignee: Unassigned Created: 2018/08/29 1:41 AM Environment: Windows 10 - 1803 Ruby 2.4.3-2 x64 Puppet Gem 5.5.6 x64 Priority: Normal Reporter: Glenn Sarti This is a real edge case but it's SUPER SUPER WEIRD Using a manifest of include ppp I expect the output from puppet apply manifest.pp to raise a compile error such as Error: Evaluation Error: Error while evaluating a Function Call, Could not find class ::ppp for glenns.gallifrey.local (file: C:/Source/tmp/wtf/manifest.pp, line: 1, column: 1) on node glenns.gallifrey.local However in certain circumstance I get a "Could not run: stack level too deep", which appears to be puppet recursively trying to load
Jira (PUP-9084) Build CI image for Ubuntu 18.10 x86
Title: Message Title Mihai Buzgau assigned an issue to Sebastian Miclea Puppet / PUP-9084 Build CI image for Ubuntu 18.10 x86 Change By: Mihai Buzgau Assignee: Sebastian Miclea 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-9085) Setup local Jenkins server
Title: Message Title Mihai Buzgau assigned an issue to Mihai Buzgau Puppet / PUP-9085 Setup local Jenkins server Change By: Mihai Buzgau Assignee: Mihai Buzgau 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-9088) Build Puppet Agent for Ubuntu 18.10
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9088 Build Puppet Agent for Ubuntu 18.10 Change By: Mihai Buzgau Story Points: 3 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-9089) Determine the process for updating a PA component
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9089 Determine the process for updating a PA component Change By: Mihai Buzgau Story Points: 5 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-9086) Add dummy job to local Jenkins deployment
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9086 Add dummy job to local Jenkins deployment Change By: Mihai Buzgau Story Points: 3 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-9087) Investigate process for building the PA
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9087 Investigate process for building the PA Change By: Mihai Buzgau Story Points: 5 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-9084) Build CI image for Ubuntu 18.10 x86
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9084 Build CI image for Ubuntu 18.10 x86 Change By: Mihai Buzgau Story Points: 5 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-9085) Setup local Jenkins server
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9085 Setup local Jenkins server Change By: Mihai Buzgau Story Points: 3 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-9089) Determine the process for updating a PA component
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9089 Determine the process for updating a PA component Change By: Mihai Buzgau Sprint: C PR - 2018- 09 08 - 12 29 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-9083) This epic is a placeholder for items related to learning the Puppet Build/Test/Release process
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9083 This epic is a placeholder for items related to learning the Puppet Build/Test/Release process Change By: Mihai Buzgau Epic Name: PA - Learning 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-9083) This epic is a placeholder for items related to learning the Puppet Build/Test/Release process
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9083 This epic is a placeholder for items related to learning the Puppet Build/Test/Release process Change By: Mihai Buzgau Epic Name: PA PR - Learning 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-9089) Determine the process for updating a PA component
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9089 Determine the process for updating a PA component Issue Type: Story Assignee: Unassigned Created: 2018/08/29 1:06 AM Priority: Normal Reporter: Mihai Buzgau Fork the PA repo Point the local jenkins deployment to the fork Update one of the PA components Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9088) Build Puppet Agent for Ubuntu 18.10
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9088 Build Puppet Agent for Ubuntu 18.10 Issue Type: Story Assignee: Unassigned Created: 2018/08/29 1:01 AM Priority: Normal Reporter: Mihai Buzgau 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 (PUP-9087) Investigate process for building the PA
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9087 Investigate process for building the PA Issue Type: Story Assignee: Unassigned Created: 2018/08/29 12:58 AM Priority: Normal Reporter: Mihai Buzgau Build the puppet agent using the locally deployed Jenkins server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9086) Add dummy job to local Jenkins deployment
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9086 Add dummy job to local Jenkins deployment Issue Type: Story Assignee: Unassigned Created: 2018/08/29 12:56 AM Priority: Normal Reporter: Mihai Buzgau Add a dummy job to local Jenkins deployment. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9085) Setup local Jenkins server
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9085 Setup local Jenkins server Issue Type: Story Assignee: Unassigned Created: 2018/08/29 12:54 AM Priority: Normal Reporter: Mihai Buzgau Using the steps described here: https://github.com/puppetlabs/ci-job-configs/blob/master/doc/qe/jjb-vagrant.md setup a local Jenkins server that contains all the PA Jenkins jobs: https://jenkins-platform.delivery.puppetlabs.net/view/puppet-agent%20suite%20pipelines/ Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9084) Build CI image for Ubuntu 18.10 x86
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9084 Build CI image for Ubuntu 18.10 x86 Issue Type: Story Assignee: Unassigned Created: 2018/08/29 12:51 AM Priority: Normal Reporter: Mihai Buzgau Learn the process of building a VMWare image using puppet-labs packer and platform-ci-utils on a ubuntu 18.10 image Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9083) This epic is a placeholder for items related to learning the Puppet Build/Test/Release process
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9083 This epic is a placeholder for items related to learning the Puppet Build/Test/Release process Issue Type: Epic Assignee: Unassigned Created: 2018/08/29 12:40 AM Priority: Normal Reporter: Mihai Buzgau 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
Jira (PUP-6507) Puppet help: Hide bad subcommands, and sort remainder by usefulness
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-6507
Puppet help: Hide bad subcommands, and sort remainder by usefulness
Change By:
Josh Cooper
The CLI leads meeting recently discussed the current slate of built-in Puppet subcommands (all thirty of them), and came to the conclusion that some of them are useless and/or harmful.Deprecating and removing subcommands is a larger task, and improving the interfaces of useful-but-problematic ones is an even bigger one. But we identified two things we can do today to vastly improve the user experience. Namely: * {{puppet help}}'s list of subcommands should omit the useless or confusing ones completely. This won't break the workflow of anyone who's actually using them, but will keep new users from hitting their heads on exposed nails or stepping into the insulation. * The list of remaining subcommands should be sorted into categories according to their usefulness, so users who haven't memorized everything can more easily stay on the rails.h2. The useless commandsThe CLI leads team has broadly agreed that the following subcommands aren't good news. This list mostly focuses on the "indirector faces," but also includes some other stuff. * puppet file * puppet report * puppet resource_type * puppet status * puppet inspect * puppet plugin * puppet doc * puppet catalog * puppet ca * puppet certificate_request * puppet certificate_revocation_list * puppet keyh2. Categories of remaining commandsh3. Useful on a daily basis for most users * puppet agent * puppet apply * puppet cert * puppet resource * puppet moduleh3. Occasionally useful, or frequently useful for a smaller subset of users * puppet config * puppet describe * puppet device * puppet epp * puppet facts * puppet filebucket * puppet help * puppet lookup * puppet man * puppet node * puppet parserh3. Rarely useful * puppet certificate * puppet masterh3. Plugin-provided(We should have a section for PE-only or third-party subcommands.)Updated**Here is a list of subcommands in puppet#master:||Useful Subcommands||Status|||apply|keep||agent|keep||config|keep||help|keep||lookup|keep||module|keep||resource|keep|||Less Used||Status||What For?|||catalog|keep|download catalog||device|keep|run puppet on devices||epp|keep|interact with puppet's templating parser/render||facts|keep|generate puppet facts||filebucket|keep|interact with filebucket||generate|keep|environment isolation||parser|keep|validate catalogs||script|keep|runs puppet code without a catalog|||Could Be Useful With Work||Status||What For?|||node|???|retrieve node classification||plugin|???|force pluginsync||report|???|upload report||status|???|check server status|||Needs Work/Replacing||Status||What For?|||ca|delete|replace with {{`puppetserver ca`}}||cert| ??? delete |split into puppetserver ca and agent cli||certificate|delete| ||certificate_request|delete| ||certificate_request_list|delete| ||key|delete| |||Documentation Related||Status||What For?|||describe| ??? keep |list and describe types & providers||doc| ??? keep
Jira (PUP-8446) Remove "puppet man" face application
Title: Message Title Josh Cooper commented on PUP-8446 Re: Remove "puppet man" face application We need to improve our docs tooling before we can remove this. Moving this out of the removals epic. For 6.0, we can hide the man application from the help output and that's filed as PUP-6507. 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.
