Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland commented on PUP-2868 Re: `puppet config print` confusing for users Release notes added. 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-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kris Bosland Release Notes Summary: puppet config print, set, and delete now print the environment and section on stderr to reduce user confusion. puppet config print also warns the user if they do not specify a section. 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-8188) --render-as broken in puppet config print
Title: Message Title Kris Bosland assigned an issue to Unassigned Puppet / PUP-8188 --render-as broken in puppet config print Change By: Kris Bosland 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-4937) puppet agent runs report time spent applying catalogue but omit total time spent
Title: Message Title Josh Cooper commented on PUP-4937 Re: puppet agent runs report time spent applying catalogue but omit total time spent Melissa Stone also 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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Josh Cooper commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log Also related Melissa Stone 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-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Josh Cooper commented on PUP-6343 Re: Add catalog apply time to Puppet::Util::Metric "time" category This should be handled in PUP-970. Melissa Stone can you confirm and close this as a dup if so? 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-366) Target cannot be used to construct a copy
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-366 Target cannot be used to construct a copy Change By: Michael Smith Sprint: Bolt 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-8517) module install against local repository fails
Title: Message Title Barry Haycock commented on PUP-8517 Re: module install against local repository fails Thanks for the guidance on the issue, I have been able to find out that the section that maintains the forge that I was connecting to only supported puppet < 4.8. I have been able to find a newer version that supports my needs This ticket can be closed 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-478) Implement Typed Facts
Title: Message Title Josh Cooper commented on PUP-478 Re: Implement Typed Facts We've seen real world examples where ec2 metadata is a binary gzip and other cases where ec2 metadata is sensitive. Having typed data would be useful. 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-8543) Puppet partly relies on legacy facts
Title: Message Title
Philippe Muller updated an issue
Puppet / PUP-8543
Puppet partly relies on legacy facts
Change By:
Philippe Muller
*Puppet Version: 5.4.0* *OS Name/Version: All*Reading the documentation, I believe the recommended way to access facts is through {{$facts}}, using [modern facts|https://puppet.com/docs/facter/3.9/core_facts.html#modern-facts].However, some parts of the code base still relies on legacy facts. For example, see [provider/service/init.rb|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/init.rb#L7].When writing a module which strictly relies on [modern facts|https://puppet.com/docs/facter/3.9/core_facts.html#modern-facts], this is bothering: the only way to make them work is to provide both [legacy|https://puppet.com/docs/facter/3.9/core_facts.html#legacy-facts] and modern facts. *Desired Behavior:*Only relies modern facts.*Actual Behavior:*Still relies on legacy facts. Gives weird _weird_ errors, like this one:{noformat} Puppet::PreformattedError: Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/service: Could not autoload puppet/provider/service/gentoo: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass {noformat} (i) Not using Gentoo: this misleading error is just a side effect of [this all to downcase|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/init.rb#L24] on an undefined legacy fact in my rspec-puppet mocked facts.
Add Comment
Jira (PUP-8543) Puppet partly relies on legacy facts
Title: Message Title Philippe Muller commented on PUP-8543 Re: Puppet partly relies on legacy facts I updated the issue description, trying to improve it. My point is: Since Facter 3 (I believe), there are both "legacy" and "modern" facts (as described in Core Facts) The issue is that while the documentation seems to recommend using modern facts, Puppet is still relying a lot on legacy facts I stumbled upon this issue while writing tests for a Puppet module. I wanted to rely strictly on modern facts. So I only mocked modern facts. But when using the service type, I got the weird error specified in the description. So no, I am not using Gentoo, nor a Puppet Server. Just Puppet 4 and 5, running with rspec-puppet. As it appears that legacy facts use is generalized in the Puppet code base, I did not make this issue specific to the service type. 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,
Jira (PUP-8543) Puppet partly relies on legacy facts
Title: Message Title
Philippe Muller updated an issue
Puppet / PUP-8543
Puppet partly relies on legacy facts
Change By:
Philippe Muller
*Puppet Version: 5.4.0* *OS Name/Version: All*Reading the documentation, I believe the recommended way to access facts is through {{$facts}} , using [modern facts|https://puppet . com/docs/facter/3.9/core_facts.html#modern-facts]. However, some parts of the code base still relies on legacy facts. For example, see [provider/service/init.rb|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/init.rb#L7].When writing a module which strictly relies on new [modern facts|https://puppet.com/docs/facter/3.9/core_facts.html#modern - style facts ] , this is bothering: the only way to make them work is to provide both [ legacy and new |https://puppet.com/docs/facter/3.9/core_facts.html#legacy - style facts ] and modern facts . *Desired Behavior:*Only relies new-style modern facts.*Actual Behavior:*Still relies on legacy facts. Gives weird errors, like this one:{noformat} Puppet::PreformattedError: Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/service: Could not autoload puppet/provider/service/gentoo: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-230) Puppet strings should look for default parameter values in module-scoped hiera
Title: Message Title Jacob Henner created an issue Puppet Strings / PDOC-230 Puppet strings should look for default parameter values in module-scoped hiera Issue Type: Improvement Assignee: Unassigned Created: 2018/03/12 8:19 PM Priority: Normal Reporter: Jacob Henner When generating documentation for parameterized classes, puppet strings only includes the default values which are specified within the class itself. Instead, puppet strings should also consider values in hiera, and indicate when there are multiple possible defaults, or an unclear selection (hiera files based upon facts) with a comment such as "multiple defaults: see hiera". Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Michael Smith
During the first action that uses the PCP transport while running a plan attempt to use {{/commands/plan_start}} (providing the plan name) to get a plan_job_id. If the command is not supported by Orchestrator, continue without a plan_job_id. Other errors should halt the plan.Subsequent actions over the PCP transport should use the same plan_job_id. On completion, error, or Ctrl-C, Bolt should call {{/commands/plan_end}} if {{plan_start}} was previously used. This indicates that transports need a concept of setup and teardown.The name of nested plans are essentially ignored by the PCP transport.
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
Jira (PUP-8544) Remove webrick application and server
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8544
Remove webrick application and server
Change By:
Josh Cooper
Remove the {{puppet master}} application, related webrick code in {{puppet/network/http/webrick*}}, and related unit tests. Verify all of the acceptance tests rely on {{puppetserver}} . Also remove the {{rack}} feature.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-343) Document Bolt with Orchestrator
Title: Message Title Kate Lopresti commented on BOLT-343 Re: Document Bolt with Orchestrator Added draft copy below the pre docs. Michael Smith can you please review. https://docs.google.com/document/d/1oOcCMzw9M9PylEgI5ARWzzSBoPv6W3q_8oHuGA05VzY/edit?usp=sharing. 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-2868) `puppet config print` confusing for users
Title: Message Title Eric Delaney commented on PUP-2868 Re: `puppet config print` confusing for users Kris Bosland Can you add release notes if 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 (PUP-8477) selinux types are being set on every run
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-8477 selinux types are being set on every run Change By: Kris Bosland 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-8469) fqdn_rand should use md5 on non-fips enabled hosts
Title: Message Title
Kris Bosland commented on PUP-8469
Re: fqdn_rand should use md5 on non-fips enabled hosts
All current branches now give the same result (17 in my case): 4.10.x:
% bx puppet apply -e '$value = fqdn_rand(30); notice("$puppetversion: $value")' /Users/kris.bosland/work/puppet/.bundle/ruby/2.4.0/gems/CFPropertyList-2.2.8/lib/cfpropertylist/rbCFTypes.rb:24: warning: constant ::Fixnum is deprecated
Notice: Scope(Class[main]): 4.10.11: 17
Notice: Compiled catalog for x in environment production in 0.10 seconds
Notice: Applied catalog in 0.01 seconds
5.3.x:
% bx puppet apply -e '$value = fqdn_rand(30); notice("$puppetversion: $value")'
Notice: Scope(Class[main]): 5.3.6: 17
Notice: Compiled catalog for kris.bosland-c02kf9eafft1 in environment production in 0.04 seconds
Notice: Applied catalog in 0.01 seconds
5.5.x:
% bx puppet apply -e '$value = fqdn_rand(30);
Jira (PUP-8448) "puppet cert clean" only works if at least one cert has already been signed
Title: Message Title Eric Delaney commented on PUP-8448 Re: "puppet cert clean" only works if at least one cert has already been signed Tested on 5.5.x SHA=68d2b2e715fa815623200044a67ce31ce3b4d3ef [root@c8zt7s780qtaq1h ssl]# puppet cert list "viygf9yfieg5dpt.delivery.puppetlabs.net" (SHA256) 1A:B0:5C:6F:75:A2:C1:AD:CA:CF:55:6C:8A:E7:FE:5B:A2:A7:14:0A:1C:67:CD:03:9A:E1:D7:CF:FD:1E:1C:7F [root@c8zt7s780qtaq1h ssl]# puppet cert clean viygf9yfieg5dpt.delivery.puppetlabs.net Notice: Removing file Puppet::SSL::CertificateRequest viygf9yfieg5dpt.delivery.puppetlabs.net at '/etc/puppetlabs/puppet/ssl/ca/requests/viygf9yfieg5dpt.delivery.puppetlabs.net.pem' [root@c8zt7s780qtaq1h ssl]# Add Comment This message was sent by Atlassian
Jira (PUP-8501) Switch to using multi_json
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8501 Switch to using multi_json Change By: Maggie Dreyer Fix Version/s: PUP 5.5.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-8469) fqdn_rand should use md5 on non-fips enabled hosts
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-8469 fqdn_rand should use md5 on non-fips enabled hosts Change By: Kris Bosland 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-8448) "puppet cert clean" only works if at least one cert has already been signed
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8448 "puppet cert clean" only works if at least one cert has already been signed Change By: Eric Delaney Assignee: Eric Delaney 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-2884) yumrepo type includepkgs and exclude properties don't handle list as documented
Title: Message Title Eric Delaney commented on PUP-2884 Re: yumrepo type includepkgs and exclude properties don't handle list as documented Tested on 5.5.x at SHA=68d2b2e715fa815623200044a67ce31ce3b4d3ef [root@viygf9yfieg5dpt ~]# puppet describe yumrepo yumrepo === The client-side description of a yum repository. Repository configurations are found by parsing `/etc/yum.conf` and the files indicated by the `reposdir` option in that file (see `yum.conf(5)` for details). Most parameters are identical to the ones documented in the `yum.conf(5)` man page. ... - **exclude** The string of package names or shell globs separated by spaces to
Jira (PUP-2884) yumrepo type includepkgs and exclude properties don't handle list as documented
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-2884 yumrepo type includepkgs and exclude properties don't handle list as documented Change By: Eric Delaney Assignee: Eric Delaney 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-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Eric Delaney commented on PUP-6639 Re: Yumrepo can't work with files using spaces in their INI format Tested on 5.5.x at SHA=68d2b2e715fa815623200044a67ce31ce3b4d3ef We have this repo file with spaces around the "=" sign and a trailing space after the password string [root@viygf9yfieg5dpt ~]# cat /etc/yum.repos.d/crazy-updates.repo [crazy-updates-that-we-keep] name=localmirror-updates baseurl=http://osmirror.delivery.puppetlabs.net/centos-7-x86_64/RPMS.updates gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 username=crazy_user password = password_with_a_space_after_the_string When we apply add another repo to the file, we process the file properly, while we remove the spaces we properly handled reading them. [root@viygf9yfieg5dpt ~]# puppet apply t.pp Notice: Compiled catalog for viygf9yfieg5dpt.delivery.puppetlabs.net in environment production in 0.04 seconds
Jira (BOLT-102) Loading params from file on powershell triggers splat operator error
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-102 Loading params from file on powershell triggers splat operator error Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-102) Loading params from file on powershell triggers splat operator error
Title: Message Title Michael Smith commented on BOLT-102 Re: Loading params from file on powershell triggers splat operator error Kate Lopresti this could be resolved with a minor addition to https://puppet.com/docs/bolt/0.x/bolt_options.html where we specify loading from file via the @ symbol. 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-221) Bolt currently treats PowerShell syntax errors as success when executing commands over WinRM
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-221 Bolt currently treats PowerShell syntax errors as success when executing commands over WinRM 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 (PUP-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-6639 Yumrepo can't work with files using spaces in their INI format Change By: Eric Delaney Assignee: Eric Delaney 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-356) Option to ignore local tasks when using pcp transport
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-356 Option to ignore local tasks when using pcp transport 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 (PUP-2868) `puppet config print` confusing for users
Title: Message Title Josh Cooper commented on PUP-2868 Re: `puppet config print` confusing for users Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/ad5541b1742279efb38af12d6e063d1110720660 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-374) Update bolt-vanagon to ship latest platforms
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-374 Update bolt-vanagon to ship latest platforms Change By: Michael Smith Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-374) Update bolt-vanagon to ship latest platforms
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-374 Update bolt-vanagon to ship latest platforms Change By: Michael Smith These are similar projects Add Debian 9 and remove i386 platforms for Bolt . We should keep These updates bring the platform support in-sync between bolt and more inline with pdk , which is a similar project . That comes Additionally check the rest of pdk's platform config to : add Debian 9, remove i386 see if there are any updates for specific platforms that should be done to Bolt's config . 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
Jira (BOLT-374) Update bolt-vanagon to ship latest platforms
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-374 Update bolt-vanagon to ship latest platforms Change By: Michael Smith Summary: Update bolt-vanagon to be consistent with pdk-vanagon ship latest platforms 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-8188) --render-as broken in puppet config print
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-8188 --render-as broken in puppet config print Change By: Kris Bosland 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 (BOLT-379) Accept ssh key as a string
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-379
Accept ssh key as a string
Change By:
Michael Smith
Sometimes ssh keys are not stored on disk or in the ssh agent. Bolt should accept an ssh key as a config option for the ssh transport.Requirements:- Should not be passable from the CLI.- Like sudo-password, should only be allowed in inventory data.- When users want to pass key data they should set {{private-key}} as an object in the config or inventory with {{key-data}} whose value is a single unencrypted private key. For example{code}ssh: private-key:key-data: | -BEGIN RSA PRIVATE KEY- ABCDE... -END RSA PRIVATE KEY-{code}
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
Jira (BOLT-379) Accept ssh key as a string
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-379 Accept ssh key as a string Change By: Michael Smith Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-379) Accept ssh key as a string
Title: Message Title Michael Smith commented on BOLT-379 Re: Accept ssh key as a string As context, private-key is being updated to accept a string or object so we can maintain compatibility with simple file references, but later add other things such as a password. 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-379) Accept ssh key as a string
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-379
Accept ssh key as a string
Change By:
Michael Smith
Sometimes ssh keys are not stored on disk or in the ssh agent. Bolt should accept an ssh key as a config option for the ssh transport.Requirements:- Should not be passable from the CLI.- When users want to pass key data they should set {{private-key}} as an object in the config or inventory with {{key-data}} whose value is a single unencrypted private key. For example{code}ssh: private-key:key-data: | -BEGIN RSA PRIVATE KEY- ABCDE... -END RSA PRIVATE KEY-{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this
Jira (BOLT-379) Accept ssh key as a string
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-379
Accept ssh key as a string
Change By:
Michael Smith
Sometimes ssh keys are not stored on disk or in the ssh agent. Bolt should accept an ssh key as a config option for the ssh transport.Requirements: - Should not be passable from the CLI. - When users want to pass key data they should set {{private-key}} as an object in the config or inventory with {{key-data}} whose value is a single unencrypted private key. For example{code}ssh: private-key:key-data: | -BEGIN RSA PRIVATE KEY-
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-8412) In the puppet report, provide details of which provider was used for each resource
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8412 In the puppet report, provide details of which provider was used for each resource Change By: Melissa Stone Assignee: Melissa Stone 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-7400) yumrepo provider should support username and password
Title: Message Title
Eric Delaney commented on PUP-7400
Re: yumrepo provider should support username and password
Tested on 5.5.x at SHA=68d2b2e715fa815623200044a67ce31ce3b4d3ef
[root@viygf9yfieg5dpt ~]# cat t.pp
yumrepo { 'crazy-updates':
ensure => 'present',
baseurl => 'http://osmirror.delivery.puppetlabs.net/centos-7-x86_64/RPMS.updates',
descr=> 'localmirror-updates',
gpgcheck => '1',
gpgkey => 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7',
password => 'password',
username => 'crazy_user',
}
[root@viygf9yfieg5dpt ~]# puppet apply t.pp
Notice: Compiled catalog for viygf9yfieg5dpt.delivery.puppetlabs.net in environment production in 0.04 seconds
Jira (PUP-7400) yumrepo provider should support username and password
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7400 yumrepo provider should support username and password Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action 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-377) Add the ability to pass inventory via environment variables
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-377 Add the ability to pass inventory via environment variables Change By: Michael Smith Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-377) Add the ability to pass inventory via environment variables
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-377 Add the ability to pass inventory via environment variables Change By: Michael Smith One of the design criteria for the Discovery Edge service, which operates on the network edges of the customers infrastructure, executing Discovery providers and tasks, is to not persist secrets to disk. The edge fetches secrets over a secure communication layer (HTTP/2+TLS) and keeps them in memory.In order to execute a task using Bolt, one currently has to persist the secret (key file) to disk in order to pass it to Bolt using the --private-key parameter. The request is to enable passing sensitive configuration, such as keyfile content and passwords, via environment variables.Environment variables have content size limits. On Windows that's 32KiB for the entire environment block, on Linux it's 128KiB for a single value. Our solution should be prioritized for passing a single RSA key (commonly 4KB) to Bolt on a medium sized group of nodes(16KB of node names) . - We should accept inventory as a yaml string from BOLT_INVENTORY. Documentation should mention that JSON is accepted.- We should error if BOLT_INVENTORY is set and --inventoryfile is passed as a CLI arg- We should ignore configured inventoryfile when BOLT_INVENTORY is set- Error if BOLT_INVENTORY is not a valid inventory format- Extending the supported configuration options in inventory will be addressed in a separate ticket. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7400) yumrepo provider should support username and password
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-7400 yumrepo provider should support username and password Change By: Eric Delaney Assignee: Eric Delaney 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-379) Accept ssh key as a string
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-379 Accept ssh key as a string Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8470 Unable to modify local user group membership with forcelocal Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action 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-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Eric Delaney commented on PUP-8470 Re: Unable to modify local user group membership with forcelocal tested on 5.5.x SHA=68d2b2e715fa815623200044a67ce31ce3b4d3ef [root@h3oycahh6hc35wl ~]# puppet apply t.pp Notice: Compiled catalog for h3oycahh6hc35wl.delivery.puppetlabs.net in environment production in 0.03 seconds Notice: /Stage[main]/Main/Group[group1]/ensure: created Notice: /Stage[main]/Main/Group[group2]/ensure: created Notice: /Stage[main]/Main/User[user1]/ensure: created Notice: Applied catalog in 0.18 seconds [root@h3oycahh6hc35wl ~]# grep group /etc/group group1:x:901:user1 group2:x:902:user1 [root@h3oycahh6hc35wl ~]# grep user1 /etc/passwd user1:x:900:1000:user1:/home/user1:/bin/bash [root@h3oycahh6hc35wl ~]#
Jira (BOLT-349) Update release automation to tag bolt-vanagon and publish packages
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-349 Update release automation to tag bolt-vanagon and publish packages 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 (PUP-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8470 Unable to modify local user group membership with forcelocal Change By: Eric Delaney Assignee: Eric Delaney 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-8463) Remove existing warnings and run PRs through 'ruby -wc'
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8463 Remove existing warnings and run PRs through 'ruby -wc' Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action 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-8463) Remove existing warnings and run PRs through 'ruby -wc'
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8463 Remove existing warnings and run PRs through 'ruby -wc' Change By: Eric Delaney Assignee: Eric Delaney 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-920) Add catalog application information to report
Title: Message Title Eric Delaney assigned an issue to Melissa Stone Puppet / PUP-920 Add catalog application information to report Change By: Eric Delaney Assignee: Eric Delaney Melissa Stone 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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-8409 Puppet config print lists invalid value for environment_timeout when set to unlimited Change By: Jorie Tappa Assignee: Jorie Tappa 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-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8470 Unable to modify local user group membership with forcelocal Change By: Eric Delaney Assignee: Eric Sorenson 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-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8443 Topscope 'environment' can become nil when setting node parameters in a custom terminus Change By: Eric Delaney Assignee: Thomas Hallgren 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-8477) selinux types are being set on every run
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8477 selinux types are being set on every run Change By: Eric Delaney 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-8469) fqdn_rand should use md5 on non-fips enabled hosts
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8469 fqdn_rand should use md5 on non-fips enabled hosts Change By: Eric Delaney Assignee: Jayant Sane 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-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Eric Delaney assigned an issue to Eric Sorenson Puppet / PUP-8470 Unable to modify local user group membership with forcelocal Change By: Eric Delaney Assignee: Melissa Stone Eric Sorenson 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-8448) "puppet cert clean" only works if at least one cert has already been signed
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8448 "puppet cert clean" only works if at least one cert has already been signed Change By: Eric Delaney Assignee: Jacob Helwig 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-8463) Remove existing warnings and run PRs through 'ruby -wc'
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8463 Remove existing warnings and run PRs through 'ruby -wc' Change By: Eric Delaney Assignee: Jacob Helwig 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-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Eric Delaney assigned an issue to Thomas Hallgren Puppet / PUP-8443 Topscope 'environment' can become nil when setting node parameters in a custom terminus Change By: Eric Delaney Assignee: Jacob Helwig Thomas Hallgren 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-8267) Rewrite acceptance rake tasks to leverage beaker subcommand support
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8267 Rewrite acceptance rake tasks to leverage beaker subcommand support Change By: Eric Delaney 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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8409 Puppet config print lists invalid value for environment_timeout when set to unlimited Change By: Eric Delaney 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-8188) --render-as broken in puppet config print
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8188 --render-as broken in puppet config print Change By: Eric Delaney Assignee: Jennifer Solman 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-8232) Re-add the puppet facts upload face and REST facts terminus
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8232 Re-add the puppet facts upload face and REST facts terminus Change By: Eric Delaney 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-8412) In the puppet report, provide details of which provider was used for each resource
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-8412 In the puppet report, provide details of which provider was used for each resource Change By: Eric Delaney Assignee: Eric Delaney 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-2884) yumrepo type includepkgs and exclude properties don't handle list as documented
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-2884 yumrepo type includepkgs and exclude properties don't handle list as documented Change By: Eric Delaney Assignee: Eric Delaney 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-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Eric Delaney assigned an issue to Unassigned Puppet / PUP-6639 Yumrepo can't work with files using spaces in their INI format Change By: Eric Delaney Assignee: Eric Delaney 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-2868) `puppet config print` confusing for users
Title: Message Title Craig Gomes assigned an issue to Kris Bosland Puppet / PUP-2868 `puppet config print` confusing for users Change By: Craig Gomes 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-8544) Remove webrick application and server
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8544
Remove webrick application and server
Change By:
Josh Cooper
Remove the {{puppet master}} application and , related webrick code in {{puppet/network/http/webrick*}} , and related unit tests. Verify all of the acceptance tests rely on {{puppetserver}}
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-8544) Remove webrick application and server
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8544 Remove webrick application and server Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8544) Remove webrick application and server
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8544 Remove webrick application and server Change By: Josh Cooper Sub-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-8544) Remove webrick application and server
Title: Message Title Josh Cooper created an issue Puppet / PUP-8544 Remove webrick application and server Issue Type: Task Assignee: Unassigned Created: 2018/03/12 1:55 PM Fix Versions: PUP 6.0.0 Priority: Normal Reporter: Josh Cooper Remove the puppet master application and related webrick code in puppet/network/http/webrick* Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8459) ENC acceptance tests didn't catch regression
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8459 ENC acceptance tests didn't catch regression Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action 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-373) Update Puppet for new core functions
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-373 Update Puppet for new core functions Change By: Michael Smith Release Notes Summary: Adds new core functions: empty, keys, values, join, flatten, length. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-373) Update Puppet for new core functions
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-373 Update Puppet for new core functions 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-373) Update Puppet for new core functions
Title: Message Title
Michael Smith commented on BOLT-373
Re: Update Puppet for new core functions
A basic example of some new functions
plan example::funcs(Optional[TargetSpec] $nodes = undef) {
notice("Nodes was empty: ${$nodes.empty()}")
if $nodes {
$targets = get_targets($nodes)
notice("Given ${$targets.length()} targets: ${$targets.map |$t| { $t.name }.join(',')}")
}
}
Add Comment
Jira (BOLT-356) Option to ignore local tasks when using pcp transport
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-356 Option to ignore local tasks when using pcp transport 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-373) Update Puppet for new core functions
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-373 Update Puppet for new core functions 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-377) Add the ability to pass inventory via environment variables
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-377 Add the ability to pass inventory via environment variables Change By: Michael Smith One of the design criteria for the Discovery Edge service, which operates on the network edges of the customers infrastructure, executing Discovery providers and tasks, is to not persist secrets to disk. The edge fetches secrets over a secure communication layer (HTTP/2+TLS) and keeps them in memory.In order to execute a task using Bolt, one currently has to persist the secret (key file) to disk in order to pass it to Bolt using the --private-key parameter. The request is to enable passing sensitive configuration, such as keyfile content and passwords, via environment variables.Environment variables have content size limits. On Windows that's 32KiB for the entire environment block, on Linux it's 128KiB for a single value. Our solution should be prioritized for passing a single RSA key (commonly 4KB) to Bolt on a medium sized group of nodes(16KB of node names)- We should accept inventory as a yaml string from BOLT_INVENTORY. Documentation should mention that JSON is accepted.- We should error if BOLT_INVENTORY is set and --inventoryfile is passed as a CLI arg- We should ignore configured inventoryfile when BOLT_INVENTORY is set- Error if BOLT_INVENTORY is not a valid inventory format- Extending the supported configuration options in inventory will be addressed in a separate ticket. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-377) Add the ability to pass inventory via environment variables
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-377 Add the ability to pass inventory via environment variables Change By: Michael Smith One of the design criteria for the Discovery Edge service, which operates on the network edges of the customers infrastructure, executing Discovery providers and tasks, is to not persist secrets to disk. The edge fetches secrets over a secure communication layer (HTTP/2+TLS) and keeps them in memory.In order to execute a task using Bolt, one currently has to persist the secret (key file) to disk in order to pass it to Bolt using the --private-key parameter. The request is to enable passing sensitive configuration, such as keyfile content and passwords, via environment variables.Environment variables have content size limits. On Windows that's 32KiB for the entire environment block, on Linux it's 128KiB for a single value. Our solution should be prioritized for passing a single RSA key (commonly 4KB) to Bolt on a medium sized group of nodes(16KB of node names) - We should accept inventory a yaml string from BOLT_INVENTORY. Documentation should mention that JSON is accepted. - We should error if BOLT_INVENTORY is set and --inventoryfile is passed as a CLI arg - We should ignore configured inventoryfile when BOLT_INVENTORY is set - Extending the supported configuration options in inventory will be addressed in a separate ticket. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-349) Update release automation to tag bolt-vanagon and publish packages
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-349 Update release automation to tag bolt-vanagon and publish packages Change By: Michael Smith Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Kris Bosland commented on PUP-6639 Re: Yumrepo can't work with files using spaces in their INI format Merged to master in https://github.com/puppetlabs/puppet/commit/2b7929982b1833192fe6dd9a2a136c59ae39be19 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-3874) (maint) update clj-parent and rbac dependencies
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3874 (maint) update clj-parent and rbac dependencies Issue Type: Bug Assignee: Unassigned Created: 2018/03/12 11:40 AM Priority: Normal Reporter: gepetto-bot This updates clj-parent to the latest version, as well as the version of rbac, and the rbac-client. Activity service has been rolled into rbac, so that dependency is no longer needed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-360) Store facts for targets in inventory
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-360 Store facts for targets in inventory Change By: Alex Dreyer Users should be able to store facts values for targets in inventory. Functionally facts are the same as vars but different conceptually. A fact is an observed state on the node. In the context of bolt that may come from running facter on the node, executing and arbitrary fact gathering command or task, looking up facts from puppetdb, aws, any inventory source, etc. However facts may be used when looking up the value of vars. * Fact values should be loaded from the inventory using the same merging strategy as config.* A new function add_facts(target, fact_hash) that uses the config deep merge to merge new fact values and update old values. * A new function facts(target) should return the facts hash for a target. 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
Jira (PUP-8542) remove documentation for yumrepo property target as it does not work
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8542 remove documentation for yumrepo property target as it does not work Change By: Eric Delaney Release Notes Summary: The yumrepo provider contains the property 'target' which does not work. We have removed the description for the property so it will no longer appear in the 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-8543) Puppet partly relies on legacy facts
Title: Message Title Justin Stoller commented on PUP-8543 Re: Puppet partly relies on legacy facts As Josh mentions Phillippe, the $facts accessor is the preferred way to reference facts from the Puppet Language in manifests, when writing custom types and providers in Ruby a different way to access the facts is needed, which is the Facter[:] method that you're seeing. The error you're seeing is definitely a problem and it looks like Facter cannot resolve either the operatingsystem or osfamily fact for your Gentoo server. Does this occur when you run the server or that agent? What does facter -dtp operatingsystem and facter -dtp osfamily return on that server? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-360) Store facts for targets in inventory
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-360 Store facts for targets in inventory Change By: Nick Lewis Users should be able to store facts values for targets in inventory.* Fact values should be loaded from the inventory file using the same merging strategy as config.* A new function add_facts(target, fact_hash) that uses the config deep merge to merge new fact values and update old values. * A new function facts(target) should return the facts hash for a target. 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-378) Add bolt packages to Winston ticket automation
Title: Message Title Katie Lawhorn updated an issue Puppet Task Runner / BOLT-378 Add bolt packages to Winston ticket automation Change By: Katie Lawhorn Sub-team: Bolt 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-8517) module install against local repository fails
Title: Message Title
Jesse Scott commented on PUP-8517
Re: module install against local repository fails
Barry Haycock in that other ticket, the issued ended up being that their custom Forge implementation was returning an unexpected value for one of the pagination keys. What does your implementation of the Forge API return in that section? Example from the official API:
"pagination": {
"limit": 20,
"offset": 0,
"first": "/v3/releases?module=puppetlabs-motd=20=0",
"previous": null,
"current": "/v3/releases?module=puppetlabs-motd=20=0",
"next": null,
"total": 12
}
Is it possible that your implementation is returning "false" for the "previous"/"next" keys instead of "null" when you've reached the ends of the result set?
Jira (PUP-8543) Puppet partly relies on legacy facts
Title: Message Title Josh Cooper commented on PUP-8543 Re: Puppet partly relies on legacy facts Hi Philippe Muller, the $facts hash is available when writing a manifest, but not in a provider, so it's ok to call Facter(:fact). Can you provide more information about your puppetserver and puppet-agent versions? I am guessing that the service type is loaded in puppetserver, and the osfamily fact is not getting resolved for some reason. /cc Justin Stoller, Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8517) module install against local repository fails
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8517 module install against local repository fails Change By: Josh Cooper Component/s: PMT 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-8517) module install against local repository fails
Title: Message Title Josh Cooper commented on PUP-8517 Re: module install against local repository fails The were some changes around internationalization and pagination of the forge. /cc Jesse Scott 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-8517) module install against local repository fails
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8517 module install against local repository fails Change By: Josh Cooper Team: Puppet Developer Experience 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-8418) TypeError no implicit conversion of nil into String in puppet 5.3.4
Title: Message Title Josh Cooper commented on PUP-8418 Re: TypeError no implicit conversion of nil into String in puppet 5.3.4 3 of the 4 items above are complete, and the 4th item will be done in the next few days. I don't think there's anything remaining to do for puppet or puppet-agent. Closing this as a dup of PUP-8407. 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-8543) Puppet partly relies on legacy facts
Title: Message Title Philippe Muller commented on PUP-8543 Re: Puppet partly relies on legacy facts For reference: ~/dev/oss/puppet master= $ git grep -E 'Facter\.value\(:?"?(osfamily|operatingsystem|hostname|domain|operatingsystemmajrelease|lsbdistrelease|kernelrelease|kernelmajversion)"?\)' | wc -l 75 As I am a newbie in this code base, I guess I missed a lot of others. 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
Jira (PUP-8543) Puppet partly relies on legacy facts
Title: Message Title Philippe Muller created an issue Puppet / PUP-8543 Puppet partly relies on legacy facts Issue Type: Bug Affects Versions: PUP 5.4.0 Assignee: Unassigned Components: Types and Providers Created: 2018/03/12 10:37 AM Priority: Normal Reporter: Philippe Muller Puppet Version: 5.4.0 OS Name/Version: All Reading the documentation, I believe the recommended way to access facts is through $facts. However, some parts of the code base still relies on legacy facts. For example, see provider/service/init.rb. When writing a module which strictly relies on new-style facts, this is bothering: the only way to make them work is to provide both legacy and new-style facts. Desired Behavior: Only relies new-style facts. Actual Behavior: Still relies on legacy facts. Gives weird errors, like this one: Puppet::PreformattedError: Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/service: Could not autoload puppet/provider/service/gentoo: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass
