Jira (PUP-8138) Ruby true and false should be inferred to corresponding parameterized Boolean data type
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8138 Ruby true and false should be inferred to corresponding parameterized Boolean data type Change By: Henrik Lindberg Release Notes Summary: issue never released 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-8138) Ruby true and false should be inferred to corresponding parameterized Boolean data type
Title: Message Title Henrik Lindberg commented on PUP-8138 Re: Ruby true and false should be inferred to corresponding parameterized Boolean data type This does not need any docs or release note since the issue was never in a release. The feature (a Boolean with parameter) has a separate ticket and will be documented. 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-8128) Add URI data type
Title: Message Title Henrik Lindberg commented on PUP-8128 Re: Add URI data type There is no more work needed except possibly pre-docs (subtask). Since the specification shows examples etc. I am not sure how much we actually do need the predocs for this - Thomas Hallgren ? 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-8184) Remote filebuckets lose the leading slash
Title: Message Title Josh Cooper created an issue Puppet / PUP-8184 Remote filebuckets lose the leading slash Issue Type: Bug Assignee: Unassigned Created: 2017/11/16 5:17 PM Priority: Normal Reporter: Josh Cooper If you backup a file to a local filebucket, and list its contents you'll see (once PUP-5606 is fixed): $ bx puppet filebucket list -l 549c165e620be535764e782eb1e4e83f 2017-11-16 15:27:39 /private/tmp/foo But if the same file is backed up a remote filebucket hosted by puppetserver, and you list its contents, the leading slash is lost:
Jira (BOLT-45) Display JSON results
Title: Message Title Michelle Fredette commented on BOLT-45 Re: Display JSON results added release note. 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-202) When running bolt task on a WIndows node without Puppet installed, the error message is very obscure.
Title: Message Title Michelle Fredette commented on BOLT-202 Re: When running bolt task on a WIndows node without Puppet installed, the error message is very obscure. Added release note as enhancement, not bug. 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-200) Prevent WinRM stream reading deadlock
Title: Message Title Michelle Fredette commented on BOLT-200 Re: Prevent WinRM stream reading deadlock added release note. 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-208) WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks
Title: Message Title Michelle Fredette commented on BOLT-208 Re: WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks Added release note. 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-151) Display results as they occur, instead of when all nodes finish
Title: Message Title Michelle Fredette commented on BOLT-151 Re: Display results as they occur, instead of when all nodes finish added release note. 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-98) Add sudo and sudo password prompt support
Title: Message Title Michelle Fredette commented on BOLT-98 Re: Add sudo and sudo password prompt support added release note. 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-206) Winrm connector doesn't always propagate exit status properly in failure scenarios
Title: Message Title Michelle Fredette commented on BOLT-206 Re: Winrm connector doesn't always propagate exit status properly in failure scenarios Added release note. 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 Owen Rodabaugh updated an issue PuppetDB / PDB-3311 Improve error message on "index row size" exceptions Change By: Owen Rodabaugh CS Priority: Normal CS Impact: This error is not at all helpful in understanding the underlying cause(puppet code that isn't quite right). Troubleshooting it can be extremely difficult. It can result in performance issues if enough nodes are sending in catalogs with this resource issue. It can also cause exporting of resources to fail for any nodes which have this issue as the catalog never gets into PDB. CS Severity: 3 - Serious CS Business Value: 3 - CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8131) Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8131
Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Change By:
Eric Delaney
Sprint:
Platform Core Grooming Hopper
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-8131) Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Title: Message Title
Eric Delaney commented on PUP-8131
Re: Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
I looked at the code and most of the cases are easy enough to just add the missing string to the message in the benchmark() call.
In one case we'll need to escape % format so that we can process the string once in the method and then again inside of benchmark "ie string % {format_now}
more string in %% {seconds} seconds" so that the "%{seconds}
will be passed in the string to benchmark to complete the formatting of it
The puppet-test string uses benchmark, but none of the strings in it appear to be marked for translation.
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-221) Bolt currently treats PowerShell syntax errors as success when executing commands over WinRM
Title: Message Title
Ethan Brown updated an issue
Puppet Task Runner / BOLT-221
Bolt currently treats PowerShell syntax errors as success when executing commands over WinRM
Change By:
Ethan Brown
Similar to BOLT-206, command should be updated to a slightly more robust execution model when running user code, so that terminating PowerShell errors are treated as failures properly. While {{script}} and {{task}} execution does this properly now, {{command}} does not behave as robustly. Some scenarios may already fail expectedly, while others (such as failure to parse code) may not behave properly.
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-8131) Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8131
Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Change By:
Eric Delaney
Acceptance Criteria:
- Refactor calls to Puppet::Util.benchmark to pass in a complete message string- include "in %{seconds} seconds" in the string- have benchmark() format the string and and set the number of seconds take msg % " { seconds: seconds }
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-8131) Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8131
Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Change By:
Eric Delaney
Acceptance Criteria:
- Refactor calls to Puppet::Util.benchmark to pass in a complete message string- include "in %{seconds} seconds" in the string- have benchmark() format the string and and set the number of seconds take msg % " { seconds: seconds } - ensure tests and CI continue to pass
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-221) Bolt currently treats PowerShell syntax errors as success when executing commands over WinRM
Title: Message Title Ethan Brown created an issue Puppet Task Runner / BOLT-221 Bolt currently treats PowerShell syntax errors as success when executing commands over WinRM Issue Type: Improvement Assignee: Unassigned Components: WinRM Created: 2017/11/16 4:15 PM Labels: windows Priority: Normal Reporter: Ethan Brown Similar to BOLT-206, command should be updated to a slightly more robust execution model when running user code, so that terminating PowerShell errors are treated as failures properly. Some scenarios may already fail expectedly, while others (such as failure to parse code) may not behave properly. Add Comment
Jira (PUP-7934) I18N dates in localized output should also be localized
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7934 I18N dates in localized output should also be localized Change By: Eric Delaney Sprint: Platform Core 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-8003) Update and test rubocop performance complaints Performance/Caller and Performance/CompareWithBlock
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8003 Update and test rubocop performance complaints Performance/Caller and Performance/CompareWithBlock Change By: Eric Delaney Sprint: Platform Core 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-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8122 I18n strings that include repeated lists of sentence fragments can be hard to translate Change By: Eric Delaney Sprint: Platform Core 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-8183) Update puppet device documentation for --user
Title: Message Title Rick Sherman assigned an issue to Rick Sherman Puppet / PUP-8183 Update puppet device documentation for --user Change By: Rick Sherman Assignee: Rick Sherman 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 Rick Sherman created an issue Puppet / PUP-8183 Update puppet device documentation for --user Issue Type: Task Assignee: Unassigned Created: 2017/11/16 4:05 PM Priority: Normal Reporter: Rick Sherman Previously `puppet device` required --user=root to create certificates. This has been fixed, but the man page was not updated. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-7937) extra "." or missing "." in csr message
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-7937
extra "." or missing "." in csr message
Change By:
Eric Delaney
Acceptance Criteria:
Add the "." to the message at ../lib/puppet/ssl/certificate_authority.rb:402{ { code} "%{alt_names}. To continue"... {code } } rake parallel:spec[2]rake rubocoprun through CIaddress CI issues
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-7937) extra "." or missing "." in csr message
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-7937
extra "." or missing "." in csr message
Change By:
Eric Delaney
Acceptance Criteria:
Add the "." to the message at ../lib/puppet/ssl/certificate_authority.rb:402 ' {quote} "%{alt_names}. To continue"... ' {quote} rake parallel:spec[2]rake rubocoprun through CIaddress CI issues
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-7937) extra "." or missing "." in csr message
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-7937
extra "." or missing "." in csr message
Change By:
Eric Delaney
Acceptance Criteria:
Add the "." to the message at ../lib/puppet/ssl/certificate_authority.rb:402{ quote} { "%{alt_names}. To continue"... {quote } } rake parallel:spec[2]rake rubocoprun through CIaddress CI issues
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-7937) extra "." or missing "." in csr message
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-7937
extra "." or missing "." in csr message
Change By:
Eric Delaney
Acceptance Criteria:
Add the "." to the message at ../lib/puppet/ssl/certificate_authority.rb:402 ' "%{alt_names}. To continue"... ' rake parallel:spec[2]rake rubocoprun through CIaddress CI issues
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-7937) extra "." or missing "." in csr message
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-7937
extra "." or missing "." in csr message
Change By:
Eric Delaney
Acceptance Criteria:
Add the "." to the message at ../lib/puppet/ssl/certificate_authority.rb:402"%{alt_names}. To continue"...rake parallel:spec[2]rake rubocoprun through CIaddress CI issues
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-8108) puppet device cannot create certs when run as root (4.10.x backport)
Title: Message Title Rick Sherman commented on PUP-8108 Re: puppet device cannot create certs when run as root (4.10.x backport) Hmm, the only docs are in the `puppet device` man page. I'll open a ticket to update the documentation there, which will result in more PRs 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-8108) puppet device cannot create certs when run as root (4.10.x backport)
Title: Message Title Melissa Stone commented on PUP-8108 Re: puppet device cannot create certs when run as root (4.10.x backport) This has passed CI. Are there any docs updates needed for this ticket? 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-8128) Add URI data type
Title: Message Title Melissa Stone commented on PUP-8128 Re: Add URI data type This has passed CI, but there's still an open sub task. Thomas Hallgren, is there any more work needed before we can resolve this ticket? 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-8138) Ruby true and false should be inferred to corresponding parameterized Boolean data type
Title: Message Title Melissa Stone commented on PUP-8138 Re: Ruby true and false should be inferred to corresponding parameterized Boolean data type Thomas Hallgren does this need any docs? 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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime
Title: Message Title Melissa Stone commented on PUP-7677 Re: Create a feature flag setting for puppet 6 features during puppet 5 lifetime This passed CI with https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent%20suite%20pipelines/job/platform_puppet-agent_puppet-agent-modules-and-pez_daily-pa-5.3.x/12/ 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-98) Add sudo and sudo password prompt support
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-98 Add sudo and sudo password prompt support Change By: Alex Dreyer Release Notes Summary: This allows bolt to run commands scripts and tasks as a different user than the ssh connection. There are three new commandline flags associated with it:run_as - User to run as using privilege escalationsudo - Program to execute for privilege escalation. Currently only sudo is supported.sudo_password - Password for privilege escalation Release Notes: New Feature 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-200) Prevent WinRM stream reading deadlock
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-200 Prevent WinRM stream reading deadlock Change By: Ethan Brown Release Notes Summary: Bolt may have previously deadlocked when executing a script or task on a Windows host, and that host wrote more than 4k to stderr. 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-200) Prevent WinRM stream reading deadlock
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-200 Prevent WinRM stream reading deadlock Change By: Ethan Brown Release Notes: Bug 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 (BOLT-202) When running bolt task on a WIndows node without Puppet installed, the error message is very obscure.
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-202 When running bolt task on a WIndows node without Puppet installed, the error message is very obscure. Change By: Ethan Brown Release Notes Summary: When running a script or task over WinRM, Bolt previously would have failed with an obscure message when the interpreter necessary to execute the file was unavailable. For instance, if unable to find Puppet when running .pp files. Error messaging has been improved. 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-202) When running bolt task on a WIndows node without Puppet installed, the error message is very obscure.
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-202 When running bolt task on a WIndows node without Puppet installed, the error message is very obscure. Change By: Ethan Brown Release Notes: Bug 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 (BOLT-208) WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-208 WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks Change By: Ethan Brown Release Notes Summary: Bolt previously only treated WinRM script execution as PowerShell code. To behave more like task execution, scripts now use the same file extension based whitelist to determine which executable should run a given file type. Currently, this allows for .rb scripts to be run with Ruby, .pp files to be run with Puppet, and .ps1 files to be run with PowerShell. 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-208) WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-208 WinRM node should run arbitrary whitelisted scripts by extension, as it does for tasks Change By: Ethan Brown Release Notes: New Feature 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-206) Winrm connector doesn't always propagate exit status properly in failure scenarios
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-206 Winrm connector doesn't always propagate exit status properly in failure scenarios Change By: Ethan Brown Release Notes Summary: When executing against WinRM nodes and a script or task operation fails due to exiting the script with a non-0 exit code, a terminating PowerShell error, or a PowerShell parser failure, Bolt previously may have incorrectly reported the result of the operation as a success. 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-206) Winrm connector doesn't always propagate exit status properly in failure scenarios
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-206 Winrm connector doesn't always propagate exit status properly in failure scenarios Change By: Ethan Brown Release Notes: Bug 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 (BOLT-185) Add the execution functions from puppet to a bolt module
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-185 Add the execution functions from puppet to a bolt module Change By: Alex Dreyer Fix Version/s: BOLT 0.8.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 (BOLT-220) Acceptance test for sudo support
Title: Message Title Zach Reichert created an issue Puppet Task Runner / BOLT-220 Acceptance test for sudo support Issue Type: Task Assignee: Unassigned Created: 2017/11/16 2:59 PM Priority: Normal Reporter: Zach Reichert 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-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5206
Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Change By:
Josh Cooper
Acceptance Criteria:
* The {{--local}} flag to the filebucket command should always use the {{$ clientbucket clientbucketdir }} setting for its operations* Docs are updated to reflect this (if they don't say so already)* Tests verify that this behavior is consistent
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-7954) I18N update rubocop-i18n to support complaining about translation strings with #{}
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-7954
I18N update rubocop-i18n to support complaining about translation strings with #{}
Change By:
Eric Delaney
Affects Version/s:
PUP 5.3.3
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-7954) I18N update rubocop-i18n to support complaining about translation strings with #{}
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-7954
I18N update rubocop-i18n to support complaining about translation strings with #{}
Change By:
Eric Delaney
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-8092) Concatenated strings causing breakages with Japanese group 2
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8092 Concatenated strings causing breakages with Japanese group 2 Change By: Eric Delaney 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-8092) Concatenated strings causing breakages with Japanese group 2
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8092 Concatenated strings causing breakages with Japanese group 2 Change By: Eric Delaney Affects Version/s: PUP 5.3.3 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-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Paul Anderson commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment Melissa Stone I agree that if I put my end user had on, and I set the environment in [main], and Puppet explodes, and double checking the documentation doesn't give me any reason to prefer the [agent] environment, that the current documentation is misleading. 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-179) Bolt cannot decrypt private key without relying on ssh-agent
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-179 Bolt cannot decrypt private key without relying on ssh-agent Change By: David Kramer Sprint: Bolt 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 (BOLT-161) Display error messages from tasks
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-161 Display error messages from tasks Change By: David Kramer Sprint: Bolt 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 (BOLT-160) The bolt task run should handle _output specially
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-160 The bolt task run should handle _output specially Change By: David Kramer Sprint: Bolt 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 (BOLT-81) Error message regarding ssh-agent on successful run
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-81 Error message regarding ssh-agent on successful run Change By: David Kramer Sprint: Bolt 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 (BOLT-219) Stabilize transport API
Title: Message Title David Kramer created an issue Puppet Task Runner / BOLT-219 Stabilize transport API Issue Type: Task Assignee: Unassigned Created: 2017/11/16 1:51 PM Priority: Normal Reporter: David Kramer 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-8143) Some Solaris Init services are not functional with Puppet 5
Title: Message Title Maggie Dreyer commented on PUP-8143 Re: Some Solaris Init services are not functional with Puppet 5 Thanks for looking into that, Eric! In that case it sounds like the PR is ready to merge. 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-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Melissa Stone commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment Paul Anderson The issue with the documentation is that we are overloading environment. It is used for different things in different contexts. You can find a good summary at https://tickets.puppetlabs.com/browse/PUP-6048?focusedCommentId=275369=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-275369. In the situation where users want to set the environment in puppet.conf, but want to refer to an environment that only exists on the master, that should always be set in the [agent] section. If set either at the top level or in [main], commands like puppet apply and puppet config assume environment is referring to an environment that is defined locally (i.e., exists on the local filesystem). My argument is that the current documentation is misleading, as it's apparent that setting the environment in [main] isn't doing what users expect it to do. Do you agree? 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-8143) Some Solaris Init services are not functional with Puppet 5
Title: Message Title Eric Delaney commented on PUP-8143 Re: Some Solaris Init services are not functional with Puppet 5 When using 'child' the splunk service is started: Nov 16 13:26:08 solaris-10-64.delivery.puppetlabs.net puppet-agent[1156]: [ID 702911 daemon.notice] Run of Puppet configuration client already in progress; skipping (/opt/puppetlabs/puppet/cache/state/agent_catalog_run.lock exists) Nov 16 13:26:09 solaris-10-64.delivery.puppetlabs.net puppet-agent[1151]: [ID 702911 daemon.notice] found_type_tst Nov 16 13:26:14 solaris-10-64.delivery.puppetlabs.net puppet-agent[1151]: [ID 702911 daemon.notice] (/Stage[main]/Main/Service[splunk]/ensure) ensure changed 'stopped' to 'running' Nov 16 13:26:14 solaris-10-64.delivery.puppetlabs.net puppet-agent[1151]: [ID 702911 daemon.notice] Applied catalog in 5.07 seconds and completes starting up correctly: -bash-3.2# /etc/init.d/splunk status Splunk status: splunkd is running (PID: 1255).
Jira (BOLT-190) Tasks in subfolders of a module are not found in plans but should not be
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-190 Tasks in subfolders of a module are not found in plans but should not be Change By: Alex Dreyer Sprint: Bolt One Point Oh PuppetHack 2017 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-146) Configure what interpreter/shell to use
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-146 Configure what interpreter/shell to use Change By: David Kramer Sprint: Bolt Ready for Grooming One Point Oh 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-169) Execution results for tasks that did not output JSON are not hashes
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-169 Execution results for tasks that did not output JSON are not hashes Change By: Alex Dreyer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-27) Display progress bar in summary view while tasks are executing
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-27 Display progress bar in summary view while tasks are executing Change By: David Kramer Sprint: Bolt 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 (BOLT-57) Download a file
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-57 Download a file Change By: David Kramer Sprint: Bolt Ready for Grooming One Point Oh 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-190) Tasks in subfolders of a module are not found in plans but should not be
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-190 Tasks in subfolders of a module are not found in plans but should not be Change By: David Kramer Sprint: Bolt Ready for Grooming One Point Oh 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-32) Add ability to enumerate available plans
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-32 Add ability to enumerate available plans Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-119) Implement `--noop` commandline flag and API support for noop tasks/plans
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-119 Implement `--noop` commandline flag and API support for noop tasks/plans Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-125) Support WinRM over SSL
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-125 Support WinRM over SSL Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-66) Integrate bolt and puppet-bolt for task loading and validation
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-66 Integrate bolt and puppet-bolt for task loading and validation Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-155) Show list of available tasks with bolt task show
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-155 Show list of available tasks with bolt task show Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-157) Show documentation for tasks
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-157 Show documentation for tasks Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-121) Create a default module path
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-121 Create a default module path Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-165) Fix task plan result output
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-165 Fix task plan result output Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-156) implement powershell input method
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-156 implement powershell input method Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-116) Consider the contents and format of a possible bolt.conf
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-116 Consider the contents and format of a possible bolt.conf Change By: David Kramer Sprint: Bolt Ready for Grooming PuppetHack 2017 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-185) Add the execution functions from puppet to a bolt module
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-185 Add the execution functions from puppet to a bolt module Change By: David Kramer Sprint: Tasks 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 (BOLT-66) Integrate bolt and puppet-bolt for task loading and validation
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-66 Integrate bolt and puppet-bolt for task loading and validation Change By: David Kramer Fix Version/s: BOLT 0.8.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-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Paul Anderson commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment Melissa Stone I see how I was unclear in my communication (I'm not talking about the notice/warning; it's the crash!). The issue does not occur when someone sets their environment in the agent section of the configuration. However, if one sets the environment in the [main] section on a Puppet-managed system running only the agent, they will encounter this error. This is quickly reproducible via puppet config set agent other_than_production and then puppet help. Also, to your documentation point, [the current documentation]( https://puppet.com/docs/puppet/5.3/config_file_main.html#config-sections) would seem to indicate that setting the environment in [main] should be fine, since one would assume no [server] functions would occur on an agent-only node: main is the global section used by all commands and services. It can be overridden by the other sections. 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-8107) Ability to specify source IP for the agent
Title: Message Title Jere Julian commented on PUP-8107 Re: Ability to specify source IP for the agent PR at https://github.com/puppetlabs/puppet/pull/6371 The customer requested that this be applied to the 4.x train as well. If not opposed, please let me know the preferred process, whether this commit can be merged there or if you prefer a separate PR. Thanks 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-8107) Ability to specify source IP for the agent
Title: Message Title Jere Julian assigned an issue to Jere Julian Puppet / PUP-8107 Ability to specify source IP for the agent Change By: Jere Julian Assignee: Jere Julian 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-7196) Intermittent test failure on Windows for Puppet::ModuleTool::Applications::Builder
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7196 Intermittent test failure on Windows for Puppet::ModuleTool::Applications::Builder 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-7196) Intermittent test failure on Windows for Puppet::ModuleTool::Applications::Builder
Title: Message Title Josh Cooper commented on PUP-7196 Re: Intermittent test failure on Windows for Puppet::ModuleTool::Applications::Builder We no longer run puppet specs against in-house Windows Jenkins nodes, so closing this out. 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-8143) Some Solaris Init services are not functional with Puppet 5
Title: Message Title
Eric Delaney commented on PUP-8143
Re: Some Solaris Init services are not functional with Puppet 5
The underlying issue appears to be that the '/etc/init.d/splunk' calls
3734: execve("/opt/splunk/bin/splunk", 0x080777C0, 0x080779E8) argc = 4
And that is outputting strings, to stdout. However since ctrun in the none case isn't waiting its already closed its side of the pipes and the splunk process gets a SIGPIPE which it never set up a signal handler for and dies.
3734: write(1, "\n S p l u n k > T a k".., 87) Err#32 EPIPE 3734: Received signal #13, SIGPIPE [default]
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-7931) Support HTTPS Compression on report upload
Title: Message Title Josh Cooper commented on PUP-7931 Re: Support HTTPS Compression on report upload . The trick is that the agent speaks first, so if server doesn't support whatever compression was used (gzip, inflate, etc), then the agent will have to send the report twice. We'd like to use HTTP expect/continue so that the master can reply with HTTP 100 Continue or 415 Unsupported Media Type between the time the agent sends the HTTP headers and the report body. 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-7948) selmodversion_loaded lines variable broken
Title: Message Title
Jennifer Solman updated an issue
Puppet / PUP-7948
selmodversion_loaded lines variable broken
Change By:
Jennifer Solman
I was playing with rubocop when it complained about:{code}== lib/puppet/provider/selmodule/semodule.rb ==W:121: 13: Lint/EmptyExpression: Avoid empty expressions.{code}Looking at the code its complaining about the "lines = ()" assignment:{code} def selmodversion_loadedlines = ()begin execpipe("#{command(:semodule)} --list") do |output|output.each_line do |line| line.chomp! bits = line.split if bits[0] == @resource[:name]self.debug "load version #{bits[1]}"return bits[1] endend endrescue Puppet::ExecutionFailure raise Puppet::ExecutionFailure, "Could not list policy modules: #{lines.join(' ').chomp!}", $!.backtraceendnil end{code}Looking at the code, lines will be assigned "nil" which doesn't have a .join method. So the exception will fail. We also fail to do anything with the lines variable in the method so if it was intended to be an array, it never gets changed from an empty array which is kind of pointless.We should enable "Lint/EmptyExpression" in the .robocop.yml if when this is fixed and we're on 0.49 or greater. Branch off of 5.3.x
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
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 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-3439) PMT can't accept deflate (zlib) compressed content from the forge
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3439 PMT can't accept deflate (zlib) compressed content from the forge Change By: Josh Cooper 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-3036) Replace keywords `and` and `or` where they don't change semantics, using rubocop:Style/AndOr
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3036 Replace keywords `and` and `or` where they don't change semantics, using rubocop:Style/AndOr 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-7904) return() errors inside iteration functions
Title: Message Title Josh Cooper commented on PUP-7904 Re: return() errors inside iteration functions ping Garrett Guillotte 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-7904) return() errors inside iteration functions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7904 return() errors inside iteration functions 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-7904) return() errors inside iteration functions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7904 return() errors inside iteration functions Change By: Josh Cooper Component/s: DOCS 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-8181) break() fails with illegal context error within hash iteration outside any function
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8181 break() fails with illegal context error within hash iteration outside any function 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 (FACT-1797) Amazon EC2 Instance not detected as is_virtual
Title: Message Title Mark Bentley commented on FACT-1797 Re: Amazon EC2 Instance not detected as is_virtual I'm seeing the same issue on a c5.4xlarge running Windows Server 2012R2 Facter 3.5.1 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-44) Display human-readable results from running a task
Title: Message Title David Kramer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-44 Display human-readable results from running a task Change By: David Kramer Assignee: Alex Dreyer 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-206) Winrm connector doesn't always propagate exit status properly in failure scenarios
Title: Message Title Michael Smith commented on BOLT-206 Re: Winrm connector doesn't always propagate exit status properly in failure scenarios Ethan Brown can you add release notes? 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-202) When running bolt task on a WIndows node without Puppet installed, the error message is very obscure.
Title: Message Title Michael Smith commented on BOLT-202 Re: When running bolt task on a WIndows node without Puppet installed, the error message is very obscure. Ethan Brown please add release notes. 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-44) Display human-readable results from running a task
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-44 Display human-readable results from running a task Change By: Alex Dreyer Sprint: Bolt Ready for Grooming 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-8181) break() fails with illegal context error within hash iteration outside any function
Title: Message Title Reid Wahl updated an issue Puppet / PUP-8181 break() fails with illegal context error within hash iteration outside any function Change By: Reid Wahl Summary: break() fails with illegal context error within a loop over a hash iteration outside any function 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-8181) break() fails with illegal context error within a loop over a hash outside any function
Title: Message Title
Reid Wahl updated an issue
Puppet / PUP-8181
break() fails with illegal context error within a loop over a hash outside any function
Change By:
Reid Wahl
break() fails with an illegal context error within an each loop hash iteration outside any functionIt may be that I simply need to use a function and call it a day... I am, however, surprised that this doesn't work, and I wonder if this is by design or by accident.{code}$ cat test2.pp# test.pp$test_hash = { 'Linus' => 'Torvalds', 'Richard' => 'Stallman', 'Dennis' => 'Ritchie',}$test_hash.each |String $first, String $last| { if $last == 'Stallman' {notice("YES")break() } else {notice("NO") }}{code}{code}$ puppet apply test2.ppNotice: Scope(Class[main]): NONotice: Scope(Class[main]): YESError: break() from context where this is illegal at /tmp/test2.pp:12 on node {code}I've tried the same thing with {{return()}}:{code}$ puppet apply test2.ppNotice: Scope(Class[main]): NONotice: Scope(Class[main]): YESError: return() from context where this is illegal at /tmp/test2.pp:13 on node {code}If I run {{break()}} within a class, I get the same error.If I run {{return()}} within a class, it breaks out of the entire class rather than just the lambda in the {{.each}} loop:{code}$ cat test3.pp# test.ppclass test_class { $test_hash = {'Linus' => 'Torvalds','Richard' => 'Stallman','Dennis' => 'Ritchie', } $test_hash.each |String $first, String $last| {if $last == 'Stallman' { notice("YES") return()}else { notice("NO")} } notice("OUT OF THE LOOP")}include ::test_class{code}{code}$ puppet apply test3.ppNotice: Scope(Class[Test_class]): NONotice: Scope(Class[Test_class]): YESNotice: Compiled catalog for in environment production in 0.26 secondsNotice: Applied catalog in 0.45 seconds{code}Edit: Issue may be confined to hashes. I'm trying `map` like in the language doc's examples (https://puppet.com/docs/puppet/5.3/function.html#break). The array example works fine. The hash example breaks.{code}$ cat test4.pp# test.ppclass test_class { $data = [1,2,3] notice $data.map |$x| {if $x == 3 { break()}$x*10 } $data_hash = { 'a' => 1, 'b' => 2, 'c' => 3 } notice $data_hash.map |$key, $value| {if $value == 3 { break()}$value*10 } notice("OUT OF THE LOOP")}include ::test_class{code}{code}$ puppet apply test4.ppNotice: Scope(Class[Test_class]): [10, 20]Error: break() from context where this is illegal at /tmp/test4.pp:15 on node {code}Example of a workaround using a function and {{return()}}:{code}$ cat test5.pp# test.ppfunction has_two($data) { $data.each |$key, $value| {if $value == 2 { return(true)} } return(false)}$data = { 'a' => 1, 'b' => 2, 'c' => 3 }if has_two($data) { notice "YES"}else { notice "NO"}{code}{code}$ puppet apply test5.ppNotice: Scope(Class[main]): YESNotice: Compiled catalog for in environment production in 0.16 secondsNotice: Applied catalog in 0.49 seconds{code}
Jira (PUP-7507) puppet lookup --facts can't modify $facts hash
Title: Message Title Gerhardus Geldenhuis commented on PUP-7507 Re: puppet lookup --facts can't modify $facts hash Perhaps to be absolutely clear, my expectation is that I should be able to fully simulate an actual hiera lookup with a combination of facts provided via --facts which should be compatible with what I would get if I did a facter -y or -j and also be compatible with the output of any fact hashes like trusted and lastly combine anything remaining from PuppetDB if available. 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-7507) puppet lookup --facts can't modify $facts hash
Title: Message Title Henrik Lindberg commented on PUP-7507 Re: puppet lookup --facts can't modify $facts hash Thomas Hallgren I think we ended up with the idea of allowing the key trusted in the given facts, to be treated as the information that ends up in $trusted - that would be the same way this gets done when a node's data is obtained from PDB. Not sure that is tested though. 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.
