Jira (PDB-5133) Use grouping sets for event-counts endpoints
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-5133
Use grouping sets for event-counts endpoints
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2021/05/18 5:01 PM
Priority:
Normal
Reporter:
Austin Blatt
Currently, when the PE console queries the aggregate event counts endpoint and requests summarize_by="containing_class,certname,resource"}}l, the event-counts query performs the three queries in separate queries joined by {{UNION ALL. This results in the events query being run three times. Instead, we can likely get the same results using GROUPING SETS, which will only execute the underlying query once. https://github.com/puppetlabs/pe-console-ui/blob/83f6fb5197b88f5da1f24254faa4ad3400923253/src/puppetlabs/pe_console_middleware/cm/state_inspector/core.clj#L211-L214 https://www.postgresqltutorial.com/postgresql-grouping-sets/ https://www.postgresql.org/docs/10/queries-table-expressions.html#QUERIES-GROUPING-SETS
Add Comment
Jira (PDB-5132) Officially support the event counts endpoints
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5132 Officially support the event counts endpoints Issue Type: Improvement Assignee: Unassigned Created: 2021/05/18 4:04 PM Priority: Normal Reporter: Austin Blatt aggregate-event-counts and event-counts have been around for a long time, and are used in the PE console, but they produce log warnings 2021-03-24T10:35:00.222Z WARN [p.p.q.engine] The aggregate-event-counts entity is experimental and may be altered or removed in the future. 2021-03-24T10:35:00.485Z WARN [p.p.q.engine] The event-counts entity is experimental and may be altered or removed in the future.
Jira (PDB-5131) Enable drop joins by default
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5131 Enable drop joins by default Issue Type: Improvement Assignee: Unassigned Created: 2021/05/18 3:41 PM Priority: Normal Reporter: Austin Blatt Drop joins has shown that it can significantly speed up nodes queries, so we should enable it by default for that entity. We should test that drop joins can be disabled, so that users can back out of this change if they encounter errors. Initially this will target main so that 6.x will be more stable. If it proves stable, we may backport it later. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11070) pacman package provider failing for facter version 4.1.1
Title: Message Title
Jim Richardson updated an issue
Puppet / PUP-11070
pacman package provider failing for facter version 4.1.1
Change By:
Jim Richardson
*Puppet Version: 7.6.1* *Puppet Server Version:* *OS Name/Version: Arch, Manjaro*Between facter version 3.14.16 and 4.1.1 the operatingsystem fact change value for Archlinux and Manjorolinux Manjarolinux systems. I will paste below the old, and new versions, and a pactch patch I applied that resolved my issue.{{$ facter --version3.14.16$ facter operatingsystemArchlinux$ facter --version4.1.1manjaro$ facter operatingsystemArchmanjaro$ facter --version4.1.1$ facter operatingsystemManjaro$ diff -uN gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb.original gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb--- gems/2.6.0/gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb.original 2021-05-18 13:42:53.605213957 -0400+++ gems/2.6.0/gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb 2021-05-18 13:44:11.515267826 -0400@@ -17,8 +17,8 @@ # Yaourt is a common AUR helper which, if installed, we can use to query the AUR commands :yaourt => "/usr/bin/yaourt" if yaourt? - confine :operatingsystem => [:archlinux, :manjarolinux]- defaultfor :operatingsystem => [:archlinux, :manjarolinux]+ confine :operatingsystem => [:archlinux, :manjarolinux, :arch, :manjaro]+ defaultfor :operatingsystem => [:archlinux, :manjarolinux, :arch, :manjaro] has_feature :install_options has_feature :uninstall_options has_feature :upgradeable}}*Desired Behavior:**Support new fact operatingsystem values for Archlinux family**Actual Behavior:**Fails to provide pacman support with new values.*
Add Comment
Jira (PUP-11070) pacman package provider failing for facter version 4.1.1
Title: Message Title
Jim Richardson updated an issue
Puppet / PUP-11070
pacman package provider failing for facter version 4.1.1
Change By:
Jim Richardson
*Puppet Version: 7.6.1* *Puppet Server Version:* *OS Name/Version: Arch, Manjaro*Between facter version 3.14.16 and 4.1.1 the operatingsystem fact change value for Archlinux and Manjorolinux systems. I will paste below the old, and new versions, and a pactch I applied that resolved my issue. {{ $ facter --version $ facter --version3 3 .14.16 $ facter operatingsystemArchlinux operatingsystem Archlinux $ facter -- version4 version4 .1.1 manjaro $ facter operatingsystemArch operatingsystem Arch manjaro $ facter -- version4 version4 .1.1 $ facter operatingsystemManjaro operatingsystem Manjaro $ diff -uN gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb.original gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb --- gems/2.6.0/gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb.original 2021-05-18 13:42:53.605213957 -0400 +++ gems/2.6.0/gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb 2021-05-18 13:44:11.515267826 -0400 @@ -17,8 +17,8 @@ # Yaourt is a common AUR helper which, if installed, we can use to query the AUR commands :yaourt => "/usr/bin/yaourt" if yaourt? - confine :operatingsystem => [:archlinux, :manjarolinux] - defaultfor :operatingsystem => [:archlinux, :manjarolinux] + confine :operatingsystem => [:archlinux, :manjarolinux, :arch, :manjaro] + defaultfor :operatingsystem => [:archlinux, :manjarolinux, :arch, :manjaro] has_feature :install_options has_feature :uninstall_options has_feature :upgradeable }} *Desired Behavior:**Support new fact operatingsystem values for Archlinux family**Actual Behavior:**Fails to provide pacman support with new values.*
Add Comment
Jira (PUP-11070) pacman package provider failing for facter version 4.1.1
Title: Message Title Jim Richardson created an issue Puppet / PUP-11070 pacman package provider failing for facter version 4.1.1 Issue Type: Bug Affects Versions: PUP 7.6.0 Assignee: Unassigned Components: Types and Providers Created: 2021/05/18 10:59 AM Priority: Normal Reporter: Jim Richardson Puppet Version: 7.6.1 Puppet Server Version: OS Name/Version: Arch, Manjaro Between facter version 3.14.16 and 4.1.1 the operatingsystem fact change value for Archlinux and Manjorolinux systems. I will paste below the old, and new versions, and a pactch I applied that resolved my issue. $ facter --version$ facter --version3.14.16 $ facter operatingsystemArchlinux $ facter --version4.1.1 manjaro$ facter operatingsystemArch manjaro$ facter --version4.1.1 $ facter operatingsystemManjaro $ diff uN gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb.original gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb-- gems/2.6.0/gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb.original 2021-05-18 13:42:53.605213957 0400+++ gems/2.6.0/gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb 2021-05-18 13:44:11.515267826 -0400@@ -17,8 17,8 @@ # Yaourt is a common AUR helper which, if installed, we can use to query the AUR commands :yaourt => "/usr/bin/yaourt" if yaourt? confine :operatingsystem => [:archlinux, :manjarolinux]- defaultfor :operatingsystem => [:archlinux, :manjarolinux] confine :operatingsystem => [:archlinux, :manjarolinux, :arch, :manjaro]+ defaultfor :operatingsystem => [:archlinux, :manjarolinux, :arch, :manjaro] has_feature :install_options has_feature :uninstall_options has_feature :upgradeable Desired Behavior: Support new fact operatingsystem values for Archlinux family Actual Behavior: Fails to provide pacman support with new
Jira (PUP-11066) optional_param does not set Integer to optional for custom ruby functions
Title: Message Title Lucy Wyman commented on PUP-11066 Re: optional_param does not set Integer to optional for custom ruby functions Definitely not a blocker since we can just use `optional_param 'Optional[Integer]'`, works just as expected. No rush on our end, just didn't want to forget to make a ticket for it. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399614.1621017826000.35223.1621355760031%40Atlassian.JIRA.
Jira (PUP-11062) better handling of enable=delayed case for a systemd service
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11062 better handling of enable=delayed case for a systemd service Change By: Mihai Buzgau Sprint: NW-2021-06-02 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399504.162100079.35097.162135365%40Atlassian.JIRA.
Jira (PUP-11066) optional_param does not set Integer to optional for custom ruby functions
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11066 optional_param does not set Integer to optional for custom ruby functions Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399614.1621017826000.35087.1621349700028%40Atlassian.JIRA.
Jira (PUP-11066) optional_param does not set Integer to optional for custom ruby functions
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11066 optional_param does not set Integer to optional for custom ruby functions Change By: Mihai Buzgau Sprint: Triaged tickets Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399614.1621017826000.35086.1621349640033%40Atlassian.JIRA.
Jira (PUP-11066) optional_param does not set Integer to optional for custom ruby functions
Title: Message Title
Mihai Buzgau updated an issue
Puppet / PUP-11066
optional_param does not set Integer to optional for custom ruby functions
Change By:
Mihai Buzgau
With a custom ruby function with the following definition, passing `nil` to Timeout errors:{ { code} } Puppet::Functions.create_function(:wait, Puppet::Functions::InternalFunction) do dispatch :wait doparam 'Variant[Future, Array[Future]]', :futuresoptional_param 'Integer[1]', :timeoutoptional_param 'Hash[String[1], Any]', :optionsreturn_type 'Array[Boltlib::PlanResult]' end def wait(futures, timeout = nil, options = {}){ { code} } Inspecting the types that Puppet expects for the function indicates that the timeout is `PIntegerType`, not optional.With the following definition, the function has the correct signature:{ { code} } Puppet::Functions.create_function(:wait, Puppet::Functions::InternalFunction) do dispatch :wait doparam 'Variant[Future, Array[Future]]', :futuresoptional_param 'Optional[Integer[1]]', :timeoutoptional_param 'Hash[String[1], Any]', :optionsreturn_type 'Array[Boltlib::PlanResult]' end def wait(futures, timeout = nil, options = {}){ { code} }
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11067) Specifying purge_ssh_keys parameter for non-existing user errors out
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11067 Specifying purge_ssh_keys parameter for non-existing user errors out Change By: Mihai Buzgau Sprint: NW-2021-06-02 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399645.162108100.35079.1621349160043%40Atlassian.JIRA.
Jira (PUP-11067) Specifying purge_ssh_keys parameter for non-existing user errors out
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11067 Specifying purge_ssh_keys parameter for non-existing user errors out Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399645.162108100.35080.1621349160101%40Atlassian.JIRA.
Jira (PUP-11067) Specifying purge_ssh_keys parameter for non-existing user errors out
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11067 Specifying purge_ssh_keys parameter for non-existing user errors out Change By: Mihai Buzgau Labels: community Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399645.162108100.35077.1621348860084%40Atlassian.JIRA.
Jira (PUP-11068) Add '--names-only' option to `puppet facts diff`
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11068 Add '--names-only' option to `puppet facts diff` Change By: Mihai Buzgau Sprint: Triaged tickets Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399649.1621234478000.35076.1621348860041%40Atlassian.JIRA.
Jira (PUP-11069) [Ruby 3] Handle sorted_set removal in semantic_puppet gem
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-11069 [Ruby 3] Handle sorted_set removal in semantic_puppet gem Change By: Mihai Buzgau Sprint: Triaged tickets Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399744.1621342573000.35069.1621348620095%40Atlassian.JIRA.
Jira (FACT-3042) Facter should retrieve EC2 metadata using IMDSv2 without requring user configuration
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3042 Facter should retrieve EC2 metadata using IMDSv2 without requring user configuration Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399711.1621283832000.35067.1621348500150%40Atlassian.JIRA.
Jira (FACT-3042) Facter should retrieve EC2 metadata using IMDSv2 without requring user configuration
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-3042 Facter should retrieve EC2 metadata using IMDSv2 without requring user configuration Change By: Mihai Buzgau Sprint: NW-2021-06-02 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399711.1621283832000.35063.1621348320029%40Atlassian.JIRA.
Jira (PUP-7559) puppet doesn't specify file type to get default selinux context
Title: Message Title Claire Cadman updated an issue Puppet / PUP-7559 puppet doesn't specify file type to get default selinux context Change By: Claire Cadman Labels: doc-reviewed file linux platform-os selinux type_and_provider Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.191580.1495040547000.35024.1621346820029%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10844 Agent failures with server_list when one puppetserver fails Change By: Claire Cadman Labels: doc-reviewed jira_escalated platform_7.2 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.381638.1608653215000.35023.1621346760030%40Atlassian.JIRA.
Jira (PUP-10922) The fqdn_rand() function should not assume case-consistency in the fqdn fact
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10922 The fqdn_rand() function should not assume case-consistency in the fqdn fact Change By: Claire Cadman Labels: doc-reviewed jira_escalated Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.387597.1613401978000.35022.1621346700217%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: Claire Cadman Labels: doc-reviewed jira_escalated Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.389668.1614728039000.35009.1621346520038%40Atlassian.JIRA.
Jira (PUP-11046) Ruby 3 removed URI.escape/unescape
Title: Message Title Claire Cadman updated an issue Puppet / PUP-11046 Ruby 3 removed URI.escape/unescape Change By: Claire Cadman Labels: doc-reviewed Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.397686.1619735375000.34997.1621346160026%40Atlassian.JIRA.
Jira (PUP-11048) Ruby 3 freezes CHILD_STATUS, so it can't be stubbed
Title: Message Title Claire Cadman updated an issue Puppet / PUP-11048 Ruby 3 freezes CHILD_STATUS, so it can't be stubbed Change By: Claire Cadman Labels: doc-reviewed Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.397709.1619737032000.34996.1621346100043%40Atlassian.JIRA.
Jira (PUP-11055) Use require_relative in puppet
Title: Message Title Claire Cadman updated an issue Puppet / PUP-11055 Use require_relative in puppet Change By: Claire Cadman Labels: doc-reviewed Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.398144.1620153504000.34990.1621345860097%40Atlassian.JIRA.
Jira (PUP-11061) Two Sensitive instances with the same value are not equal
Title: Message Title Gabriel Nagy commented on PUP-11061 Re: Two Sensitive instances with the same value are not equal From a Slack convo with Henrik: https://puppetcommunity.slack.com/archives/C0W1X7ZAL/p1621341048001500 gabi Today at 3:30 PM @helindbe or whoever may have more context: I was curious if https://tickets.puppetlabs.com/browse/PUP-11061 was an implementation oversight or intended behavior helindbe 15 minutes ago The only thing that shpuld be allowed is to know the base type of the value (e.g String), but not specifics of that steing, such as the lenght or characters in it. From that it follows that comparison should not be allowed. One reason is that equality check can fail and the error message may reveal the sensitive value. However, since unwrap is available, it isn’t really a hard security concern, but unwrap shifts the responsibility not to spill the secret. Hope this explains why it works the way it does. helindbe 11 minutes ago So, I consider this intended behavior, but I don’t see a real problem if an equality check was to return true if sensitive values are equal and false for all other cases (including possible errors). Problem is, where do you stop, also support in selector and case and other comparisons… Probably best to keep it the way it is. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3027) Loosen the Ruby dependency to allow install on Ruby 3
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3027 Loosen the Ruby dependency to allow install on Ruby 3 Change By: Gheorghe Popescu Release Notes: Enhancement Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.396686.1619079094000.34971.1621342740104%40Atlassian.JIRA.
Jira (FACT-3027) Loosen the Ruby dependency to allow install on Ruby 3
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3027 Loosen the Ruby dependency to allow install on Ruby 3 Change By: Gheorghe Popescu Release Notes Summary: Allow facter gem to be installed on ruby 3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.396686.1619079094000.34970.1621342740043%40Atlassian.JIRA.
Jira (PUP-11069) [Ruby 3] Handle sorted_set removal in semantic_puppet gem
Title: Message Title Gabriel Nagy created an issue Puppet / PUP-11069 [Ruby 3] Handle sorted_set removal in semantic_puppet gem Issue Type: Improvement Assignee: Unassigned Created: 2021/05/18 5:56 AM Priority: Normal Reporter: Gabriel Nagy PUP-11047 handles the sorted_set removal from puppet, but this is also used in the semantic_puppet gem. There are a number of ways in which we can accomplish this: explicitly depend on the sorted_set gem and include it in puppet-runtime implement the functionality using the RbTreeMap class from puppet use the rbtree gem to implement the functionality (as suggested in https://github.com/puppetlabs/puppet/pull/8589#discussion_r631590428) Add Comment
Jira (PUP-3631) NIM provider uses a regex that is too restrictive when parsing RPM release tags
Title: Message Title Austin Boyd updated an issue Puppet / PUP-3631 NIM provider uses a regex that is too restrictive when parsing RPM release tags Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 44383 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.57947.141531438.34889.1621334340033%40Atlassian.JIRA.
Jira (PUP-11015) The "posix" provider of the "exec" resource does not fullfil the documentation
Title: Message Title Felix commented on PUP-11015 Re: The "posix" provider of the "exec" resource does not fullfil the documentation Hi, would you care to share any thoughts on this? I'd actually prefer this issue to be handled rather than letting it fall into oblivion, as this might on the one hand be very unexpected to puppet users and on the other hand might actually constitute a security issue for puppet users relying on the documentation when embedding not-completely-trusted values into commands during execution. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.394250.1617733822000.34821.1621326420078%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title R.I.Pienaar commented on PUP-10627 Re: write public information to puppet_dir/public The product is secure, the information in this file is not a security risk for the vast number of users. Those who function in repressive security environments can carry the cost associated with learning every minute detail and tweaking it all to their exact needs - as they already do for everything they use. Leaving sane defaults for the majority of users. Thats why this directory was made to specifically make it easy and obvious where and what puppet is providing as public - the problem is a) a file in there is not public b) it's not public because 1 user decided its a risk while 10s felt its good use to make that data public. When picking defaults its common for those to be picked in a way to serve the majority and then allow the minorities who do need things at a much more restrictive level to adjust things. Catering to new users with sane defaults the promote a safe use of the product is not their "ignorance", it's just how new users are and how people who do not make a product their entire life exist. It's a careful balance in product design. Another tenet of product design is that of consistency and obviousness and now we have a non public file in a public directory which is not consistent or obvious. And yes, every response by you so far has been that of a Jerk Scott Cyprus I'd appreciate if you can town it down a bit to a more civil level. It would also help if you didnt edit out entire comments so that when people respond to you others can see what the responses are about. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-2938) Ship facter 4 nightly gems
Title: Message Title Gheorghe Popescu commented on FACT-2938 Re: Ship facter 4 nightly gems nightly gems available at: http://nightlies.puppet.com/downloads/gems/facter-nightly/ Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.386160.1612447345000.34801.1621321860155%40Atlassian.JIRA.
Jira (PUP-3631) NIM provider uses a regex that is too restrictive when parsing RPM release tags
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-3631 NIM provider uses a regex that is too restrictive when parsing RPM release tags Change By: Mihai Buzgau Labels: aix jira_escalated package platform-os type_and_provider Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.57947.141531438.34796.1621321560032%40Atlassian.JIRA.
Jira (FACT-3040) undefined method `each_line' for nil:NilClass
Title: Message Title Gheorghe Popescu commented on FACT-3040 Re: undefined method `each_line' for nil:NilClass merged at https://github.com/puppetlabs/facter/commit/83ecb26ef2de5b3f7005ee88968fafa684020791 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "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.399650.1621235043000.34792.1621320840031%40Atlassian.JIRA.
