Jira (PUP-10526) pip3 package provider fails manage multiple environments
Title: Message Title Josh Cooper commented on PUP-10526 Re: pip3 package provider fails manage multiple environments The same issue was reported in PUP-11681, so I'm going to close this as well. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359538.1590075231000.1935.1674017340022%40Atlassian.JIRA.
Jira (PUP-11717) Can't "dig" into facts when legacy facts are excluded
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11717 Can't "dig" into facts when legacy facts are excluded Change By: Josh Cooper Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479164.1673933795000.1931.1674004800027%40Atlassian.JIRA.
Jira (FACT-3179) Facter.resolve returns a subclass of Hash, not Hash
Title: Message Title Josh Cooper updated an issue Facter / FACT-3179 Facter.resolve returns a subclass of Hash, not Hash Change By: Josh Cooper Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479163.1673933582000.1930.1674004740023%40Atlassian.JIRA.
Jira (FACT-3177) Update facter acceptance tests to handle puppet7 vs puppet8
Title: Message Title Josh Cooper updated an issue Facter / FACT-3177 Update facter acceptance tests to handle puppet7 vs puppet8 Change By: Josh Cooper Sprint: Phoenix 2023-01-18 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479046.1673585982000.1677.1673978940021%40Atlassian.JIRA.
Jira (PUP-11716) Require JRuby 9.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11716 Require JRuby 9.4 Change By: Josh Cooper In PUP-11649, we're dropping support for MRI Ruby < 2.7, however, we have to keep support for JRuby 9.2 (which implements 2.5.x language features) until we have puppetserver builds with JRuby 9.4. Update the RUBY_VERSION check in lib/puppet.rb and deprecation warningUpdate rspec matrix in github actionsUpdate branch protection rules Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479162.1673918589000.1676.1673977260021%40Atlassian.JIRA.
Jira (PUP-11718) Drop support for ruby < 3.2
<<< text/html; charset="UTF-8": Unrecognized >>>
Jira (PUP-11649) Drop support for ruby < 2.7
Title: Message Title Josh Cooper commented on PUP-11649 Re: Drop support for ruby < 2.7 Hi Tim Meusel yes, good question. I'd be ok requiring at least 3.1 or 3.2 in puppet8. Unfortunately, the process is a little complicated due to JRuby and not breaking other projects that use puppet as a library like bolt, module CI, etc. I'll file a separate ticket to bump the minimum after we have puppet/ruby 3.2 and puppetserver/jruby 9.4 builds in CI, but before we release Puppet 8. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.470537.1665159191000.1674.1673976780025%40Atlassian.JIRA.
Jira (FACT-3179) Facter.resolve returns a subclass of Hash, not Hash
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-3179
Facter.resolve returns a subclass of Hash, not Hash
Change By:
Josh Cooper
In Facter3, the {{Facter.resolve}} API returned a {{Hash}} :{noformat}# /opt/puppetlabs/puppet/bin/ruby -e "require 'facter'; puts Facter::FACTERVERSION; puts Facter . resolve('').class" 3.14.24 Hash{noformat} In Facter4, it returns a {{Facter::FactCollection}} that extends {{Hash}} :{noformat}$ bx ruby -e "require 'facter'; puts Facter::VERSION; puts Facter . resolve('').class" 4.3.0Facter::FactCollection{noformat} The {{FactCollection}} class is not part of the Facter API and leaks implementation details. The {{resolve}} method should return a {{Hash}}.The {{Facter.to_hash}} method was fixed in https://github.com/puppetlabs/facter/commit/7e681d009e but {{Facter.resolve}} was missed.
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To
Jira (FACT-3179) Facter.resolve returns a subclass of Hash, not Hash
Title: Message Title Josh Cooper updated an issue Facter / FACT-3179 Facter.resolve returns a subclass of Hash, not Hash Change By: Josh Cooper Fix Version/s: FACT 4.3.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479163.1673933582000.1671.1673976300094%40Atlassian.JIRA.
Jira (FACT-3179) Facter.resolve returns a subclass of Hash, not Hash
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-3179
Facter.resolve returns a subclass of Hash, not Hash
Change By:
Josh Cooper
In Facter3, the {{Facter.resolve}} API returned a {{Hash}}.In Facter4, it returns a {{Facter::FactCollection}} that extends {{Hash}}. The {{FactCollection}} class is not part of the Facter API and can cause leaks implementation details to leak . The {{resolve}} method should return a {{Hash}}.The {{Facter.to_hash}} method was fixed in https://github.com/puppetlabs/facter/commit/7e681d009e but {{Facter.resolve}} was missed.
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Jira (FACT-3165) facter --debug reports wrong location of a resolved fact.
Title: Message Title Josh Cooper updated an issue Facter / FACT-3165 facter --debug reports wrong location of a resolved fact. Change By: Josh Cooper Labels: regresion regression Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.473610.1666921663000.1437.1673973240176%40Atlassian.JIRA.
Jira (PUP-1079) Exported resources is exporting to the database with --noop flag
Title: Message Title Sean Millichamp commented on PUP-1079 Re: Exported resources is exporting to the database with --noop flag I just noticed this issue and wanted to chime in and say I can see value in either behavior. In general, I would prefer -noop runs to not affect the active catalog in PuppetDB for a given node as that is a surprising effect for most users. However, I also frequently use the current behavior of updating the catalog so I can use puppet query to dig through the catalog in PuppetDB to validate that the catalog looks how I would expect (especially in terms of exported resource generation). I suppose I could, as an alternate approach, look at the client's on-disk copy of the catalog on a -noop run instead but the client's copy is typically harder for me to access than the PuppetDB one. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21413.1387220582000.1424.1673971620023%40Atlassian.JIRA.
Jira (PUP-1079) Exported resources is exporting to the database with --noop flag
Title: Message Title Xiuqing Jiang updated an issue Puppet / PUP-1079 Exported resources is exporting to the database with --noop flag Change By: Xiuqing Jiang Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21413.1387220582000.1316.1673950680128%40Atlassian.JIRA.
Jira (PUP-1079) Exported resources is exporting to the database with --noop flag
Title: Message Title Xiuqing Jiang updated an issue Puppet / PUP-1079 Exported resources is exporting to the database with --noop flag Change By: Xiuqing Jiang Labels: customer jira_escalated needs_decision puppet_agent redmine Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21413.1387220582000.1312.1673950620030%40Atlassian.JIRA.
Jira (PUP-1079) Exported resources is exporting to the database with --noop flag
Title: Message Title Xiuqing Jiang updated an issue Puppet / PUP-1079 Exported resources is exporting to the database with --noop flag Change By: Xiuqing Jiang Affects Version/s: PUP 6.28.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21413.1387220582000.1313.1673950620086%40Atlassian.JIRA.
