Jira (PUP-6802) Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment
Title: Message Title Josh Cooper commented on PUP-6802 Re: Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment The "ignore_plugin_errors" really means "if we perform a pluginsync and there are errors, then ignore them" This ticket was "if the environment we want to use doesn't exist, then skip pluginsync and give the server a chance to redirect us to the correct environment" The setting you really want is "strict_environment_mode". I'll add more details in the other ticket about why that's not working as expected. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.155674.1475855919000.13137.1644479940027%40Atlassian.JIRA.
Jira (PUP-11437) puppet lookup fails to interpolate topscope variables when an environment is specified
Title: Message Title
Josh Cooper commented on PUP-11437
Re: puppet lookup fails to interpolate topscope variables when an environment is specified
I think we want to do something like the following (ignoring whitespace changes):
diff --git a/lib/puppet/application/lookup.rb b/lib/puppet/application/lookup.rb
index cfbcfab81e..b9e6f22c87 100644
--- a/lib/puppet/application/lookup.rb
+++ b/lib/puppet/application/lookup.rb
@@ -374,12 +374,9 @@ Copyright (c) 2015 Puppet Inc., LLC Licensed under the Apache 2.0 License
unless node.is_a?(Puppet::Node) # to allow unit tests to pass a node instance
facts = retrieve_node_facts(node, given_facts)
- if Puppet.settings.set_by_cli?('environment')
-node = Puppet::Node.new(node, :classes => nil, :parameters => nil, :facts => facts, :environment => Puppet.settings.value('environment'))
- else
ni = Puppet::Node.indirection
Jira (PUP-11453) Remove cron trigger and use snyk org token
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11453 Remove cron trigger and use snyk org token Change By: Josh Cooper Sprint: Phoenix 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434827.1644471842000.13130.1644471960093%40Atlassian.JIRA.
Jira (FACT-3104) Remove cron trigger and use snyk org token
Title: Message Title Josh Cooper updated an issue Facter / FACT-3104 Remove cron trigger and use snyk org token Change By: Josh Cooper Sprint: Phoenix 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434826.1644471734000.13129.1644471960048%40Atlassian.JIRA.
Jira (PUP-11453) Remove cron trigger and use snyk org token
Title: Message Title Josh Cooper moved an issue Puppet / PUP-11453 Remove cron trigger and use snyk org token Change By: Josh Cooper Key: FACT PUP - 3105 11453 Project: Facter Puppet Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434827.1644471842000.13128.1644471900109%40Atlassian.JIRA.
Jira (FACT-3105) Remove cron trigger and use snyk org token
Title: Message Title Josh Cooper created an issue Facter / FACT-3105 Remove cron trigger and use snyk org token Issue Type: Task Assignee: Unassigned Created: 2022/02/09 9:44 PM Priority: Normal Reporter: Josh Cooper In puppet#6.x and main: Remove the cron trigger from https://github.com/puppetlabs/puppet/blob/6.x/.github/workflows/snyk_monitor.yaml#L5 Ask security to add the SNYK_FOSS_KEY organizational secret to the repo Update the snyk workflow to use the SNYK_FOSS_KEY Delete the SNYK_TOKEN secret from the repo Add Comment
Jira (FACT-3104) Remove cron trigger and use snyk org token
Title: Message Title Josh Cooper created an issue Facter / FACT-3104 Remove cron trigger and use snyk org token Issue Type: Task Assignee: Unassigned Created: 2022/02/09 9:42 PM Priority: Normal Reporter: Josh Cooper In facter#main only: Remove the cron trigger from https://github.com/puppetlabs/facter/blob/68952f2778597f75cd4c80fcd92146d53590c11c/.github/workflows/snyk_monitor.yaml#L5 Ask security to add the SNYK_FOSS_KEY organizational secret to the repo Update the snyk workflow to use the SNYK_FOSS_KEY Delete the SNYK_TOKEN secret from the repo Add Comment
Jira (PUP-11435) Puppet 6.26 and 7.13 may cause specs to fail
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11435 Puppet 6.26 and 7.13 may cause specs to fail Change By: Josh Cooper Acceptance Criteria: # Change is made to 6.x and main# The puppet_enterprise_module rspec tests should pass given the reproduction steps in the description Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.432469.164315863.13125.1644471480046%40Atlassian.JIRA.
Jira (PUP-11435) Puppet 6.26 and 7.13 may cause specs to fail
Title: Message Title
Josh Cooper commented on PUP-11435
Re: Puppet 6.26 and 7.13 may cause specs to fail
In the case where things work, only one instance of Packages is created (early on when inventory.rb is loaded) and is shared across tests, which means there is the potential for state to leak across tests. In the case where things don't work, the call to Facter.reset unregisters the fact. So the next call to Facter.value('_puppet_inventory_1') will force the fact to be reloaded via Kernel.load. My theory is that rspec redefines a method on the class, but then the call to Kernel.load overwrites the rspec method, so rspec's hook is never called. I think we should just remove the call to Facter.reset like nick.burgan-illig suggested earlier.
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
--
You received this message because you are subscribed to the Google Groups "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.432469.164315863.13124.1644471360036%40Atlassian.JIRA.
Jira (PDB-5450) Slow fact queries after PuppetDB 7.9.0 upgrade when using Postgres 12 with jit enabled
Title: Message Title Austin Blatt commented on PDB-5450 Re: Slow fact queries after PuppetDB 7.9.0 upgrade when using Postgres 12 with jit enabled A known issue (and link from the release note) has been added for this change. https://puppet.com/docs/puppetdb/6/known_issues.html Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434144.1643897486000.13118.1644458880026%40Atlassian.JIRA.
Jira (PDB-5259) Attempt to improve fact-contents endpoint performance
Title: Message Title Austin Blatt commented on PDB-5259 Re: Attempt to improve fact-contents endpoint performance A known issue (and link from the release note) has been added for this change. https://puppet.com/docs/puppetdb/6/known_issues.html Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.414907.1631116164000.13117.1644458820034%40Atlassian.JIRA.
Jira (PUP-11435) Puppet 6.26 and 7.13 may cause specs to fail
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11435
Puppet 6.26 and 7.13 may cause specs to fail
Change By:
Josh Cooper
Commit 78246ca8d08dee770886f0940a6472c45483d627 first released in 6.26.0 and 7.13.0 speeds up rspec tests but breaks puppet-enteprise-modules due to the way {{Facter.reset}} breaks stubbing for a custom fact.[https://github.com/puppetlabs/puppet/commit/78246ca8d08dee770886f0940a6472c45483d627]This ticket is to:1. Delete the call to {{Facter.reset}} line in [https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/lib/puppet/defaults.rb#L1998]2. Optional (attempt 1), try adding {{Facter.reset}} to puppet's [spec_helper.rb|https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/sec/spec_helper.rb]. That way the facter search path is reset across tests, but it's only triggered when running puppet's spec tests. But not when a module runs tests and calls puppet as a library.3. Optional (attempt 2), if attempt 1 doesn't work, try adding {{Facter.reset}} to puppet's [test helper|https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/lib/puppet/test/test_helper.rb#L145-L146] This likely has to be done after the call to {{{}Puppet.runtime[:facter]{}}}. Note this code will be invoked by modules that are using puppetlabs_spec_helper.4. If neither work, just omit the call to Facter.reset entirely.5. A more complete fix is to understand why this issue affects PE modules, but not a custom module generated via pdk (see comment below).To reproduce the issue:{code}$ git clone g...@github.com:puppetlabs/puppet_enterprise_modules$ cd puppet_enterprise_modules$ git revert f8ec0e5d9234be99b3566034e921d797fb85ea43$ PUPPET_VERSION="6.26.0" bundle install --without system_tests $ cd modules/puppet_enterprise$ PUPPET_VERSION="6.26.0" bundle exec rake spec SPEC=spec/unit/facter/inventory_spec.rb...Failures: 1) inventory facts the inventory and metadata facts when setting the inventory fact wil be populated when enabled Failure/Error: expect(Facter.value('_puppet_inventory_1')).not_to be nil expected not # => nil got # => nil Compared using equal?, which compares object identity. # ./spec/unit/facter/inventory_spec.rb:77:in `block (4 levels) in ' 2) inventory facts the inventory and metadata facts when setting the metadata fact sets enabled to true if enabled Failure/Error: expect(Facter.value('puppet_inventory_metadata')['packages']['collection_enabled']).to be true expected true got false # ./spec/unit/facter/inventory_spec.rb:89:in `block (4 levels) in 'Finished in 0.16165 seconds (files took 0.97491 seconds to load)9 examples, 2 failuresFailed examples:rspec ./spec/unit/facter/inventory_spec.rb:75 # inventory facts the inventory and metadata facts when setting the inventory fact wil be populated when enabledrspec ./spec/unit/facter/inventory_spec.rb:87 # inventory facts the inventory and metadata facts when setting the
Jira (PDB-5364) Enabling log-queries in 7.7.1 causes JSON serialization failures
Title: Message Title Charlie Sharpsteen commented on PDB-5364 Re: Enabling log-queries in 7.7.1 causes JSON serialization failures Looks like PDB-5259 fixed this in passing by adding an encoder for PgArray objects along with performance optimizations. Should be present in 6.20.0 and 7.9.0. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.423245.163664995.13082.169760031%40Atlassian.JIRA.
Jira (PUP-11435) Puppet 6.26 and 7.13 may cause specs to fail
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11435
Puppet 6.26 and 7.13 may cause specs to fail
Change By:
Josh Cooper
Commit 78246ca8d08dee770886f0940a6472c45483d627 first released in 6.26.0 and 7.13.0 speeds up rspec tests but breaks puppet-enteprise-modules due to the way {{Facter.reset}} breaks stubbing for a custom fact.[https://github.com/puppetlabs/puppet/commit/78246ca8d08dee770886f0940a6472c45483d627]This ticket is to:1. Delete the call to {{Facter.reset}} line in [https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/lib/puppet/defaults.rb#L1998]2. Optional (attempt 1), try adding {{Facter.reset}} to puppet's [spec_helper.rb|https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/sec/spec_helper.rb]. That way the facter search path is reset across tests, but it's only triggered when running puppet's spec tests. But not when a module runs tests and calls puppet as a library.3. Optional (attempt 2), if attempt 1 doesn't work, try adding {{Facter.reset}} to puppet's [test helper|https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/lib/puppet/test/test_helper.rb#L145-L146] This likely has to be done after the call to {{{}Puppet.runtime[:facter]{}}}. Note this code will be invoked by modules that are using puppetlabs_spec_helper.4. If neither work, just omit the call to Facter.reset entirely.5. A more complete fix is to understand why this issue affects PE modules, but not a custom module generated via pdk (see comment below).To reproduce the issue:{code}$ git clone g...@github.com:puppetlabs/puppet_enterprise_modules$ cd puppet_enterprise_modules$ git revert f8ec0e5d9234be99b3566034e921d797fb85ea43$ PUPPET_VERSION="6.26.0" bundle install --without system_tests $ cd modules/puppet_enterprise$ PUPPET_VERSION="6.26.0" bundle exec rake spec SPEC=spec/unit/facter/inventory_spec.rb...Failures: 1) inventory facts the inventory and metadata facts when setting the inventory fact wil be populated when enabled Failure/Error: expect(Facter.value('_puppet_inventory_1')).not_to be nil expected not # => nil got # => nil Compared using equal?, which compares object identity. # ./spec/unit/facter/inventory_spec.rb:77:in `block (4 levels) in ' 2) inventory facts the inventory and metadata facts when setting the metadata fact sets enabled to true if enabled Failure/Error: expect(Facter.value('puppet_inventory_metadata')['packages']['collection_enabled']).to be true expected true got false # ./spec/unit/facter/inventory_spec.rb:89:in `block (4 levels) in 'Finished in 0.16165 seconds (files took 0.97491 seconds to load)9 examples, 2 failuresFailed examples:rspec ./spec/unit/facter/inventory_spec.rb:75 # inventory facts the inventory and metadata facts when setting the inventory fact wil be populated when enabledrspec ./spec/unit/facter/inventory_spec.rb:87 # inventory facts the inventory and metadata facts when setting the
Jira (PUP-11435) Puppet 6.26 and 7.13 may cause specs to fail
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11435
Puppet 6.26 and 7.13 may cause specs to fail
Change By:
Josh Cooper
Commit 78246ca8d08dee770886f0940a6472c45483d627 first released in 6.26.0 and 7.13.0 speeds up rspec tests but breaks puppet-enteprise-modules due to the way {{Facter.reset}} breaks stubbing for a custom fact.[https://github.com/puppetlabs/puppet/commit/78246ca8d08dee770886f0940a6472c45483d627]This ticket is to:1. Delete the call to {{Facter.reset}} line in [https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/lib/puppet/defaults.rb#L1998]2. Optional (attempt 1), try adding {{Facter.reset}} to puppet's [spec_helper.rb|https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/sec/spec_helper.rb]. That way the facter search path is reset across tests, but it's only triggered when running puppet's spec tests. But not when a module runs tests and calls puppet as a library.3. Optional (attempt 2), if attempt 1 doesn't work, try adding {{Facter.reset}} to puppet's [test helper|https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/lib/puppet/test/test_helper.rb#L145-L146] This likely has to be done after the call to {{{}Puppet.runtime[:facter]{}}}. Note this code will be invoked by modules that are using puppetlabs_spec_helper.4. If neither work, just omit the call to Facter.reset entirely.5. A more complete fix is to understand why this issue affects PE modules, but not a custom module generated via pdk (see comment below).To reproduce the issue:{code :shell } $ git clone g...@github.com:puppetlabs/puppet_enterprise_modules$ cd puppet_enterprise_modules$ git revert f8ec0e5d9234be99b3566034e921d797fb85ea43$ PUPPET_VERSION="6.26.0" bundle install --without system_tests $ cd modules/puppet_enterprise$ PUPPET_VERSION="6.26.0" bundle exec rake spec SPEC=spec/unit/facter/inventory_spec.rb...Failures: 1) inventory facts the inventory and metadata facts when setting the inventory fact wil be populated when enabled Failure/Error: expect(Facter.value('_puppet_inventory_1')).not_to be nil expected not # => nil got # => nil Compared using equal?, which compares object identity. # ./spec/unit/facter/inventory_spec.rb:77:in `block (4 levels) in ' 2) inventory facts the inventory and metadata facts when setting the metadata fact sets enabled to true if enabled Failure/Error: expect(Facter.value('puppet_inventory_metadata')['packages']['collection_enabled']).to be true expected true got false # ./spec/unit/facter/inventory_spec.rb:89:in `block (4 levels) in 'Finished in 0.16165 seconds (files took 0.97491 seconds to load)9 examples, 2 failuresFailed examples:rspec ./spec/unit/facter/inventory_spec.rb:75 # inventory facts the inventory and metadata facts when setting the inventory fact wil be populated when enabledrspec ./spec/unit/facter/inventory_spec.rb:87 # inventory facts the inventory and metadata facts when setting
Jira (PUP-11435) Puppet 6.26 and 7.13 may cause specs to fail
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11435
Puppet 6.26 and 7.13 may cause specs to fail
Change By:
Josh Cooper
Commit 78246ca8d08dee770886f0940a6472c45483d627 first released in 6.26.0 and 7.13.0 speeds up rspec tests but breaks puppet-enteprise-modules due to the way {{Facter.reset}} breaks stubbing for a custom fact.[https://github.com/puppetlabs/puppet/commit/78246ca8d08dee770886f0940a6472c45483d627]This ticket is to:1. Delete the call to {{Facter.reset}} line in [https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/lib/puppet/defaults.rb#L1998]2. Optional (attempt 1), try adding {{Facter.reset}} to puppet's [spec_helper.rb|https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/sec/spec_helper.rb]. That way the facter search path is reset across tests, but it's only triggered when running puppet's spec tests. But not when a module runs tests and calls puppet as a library.3. Optional (attempt 2), if attempt 1 doesn't work, try adding {{Facter.reset}} to puppet's [test helper|https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/lib/puppet/test/test_helper.rb#L145-L146] This likely has to be done after the call to {{ {} Puppet.runtime[:facter] { }} } . Note this code will be invoked by modules that are using puppetlabs_spec_helper.4. If neither work, just omit the call to Facter.reset entirely.5. A more complete fix is to understand why this issue affects PE modules, but not a custom module generated via pdk (see comment below). To reproduce the issue:{code:shell}$ git clone g...@github.com:puppetlabs/puppet_enterprise_modules$ cd puppet_enterprise_modules$ git revert f8ec0e5d9234be99b3566034e921d797fb85ea43$ PUPPET_VERSION="6.26.0" bundle install --without system_tests $ cd modules/puppet_enterprise$ PUPPET_VERSION="6.26.0" bundle exec rake spec SPEC=spec/unit/facter/inventory_spec.rb...Failures: 1) inventory facts the inventory and metadata facts when setting the inventory fact wil be populated when enabled Failure/Error: expect(Facter.value('_puppet_inventory_1')).not_to be nil expected not # => nil got # => nil Compared using equal?, which compares object identity. # ./spec/unit/facter/inventory_spec.rb:77:in `block (4 levels) in ' 2) inventory facts the inventory and metadata facts when setting the metadata fact sets enabled to true if enabled Failure/Error: expect(Facter.value('puppet_inventory_metadata')['packages']['collection_enabled']).to be true expected true got false # ./spec/unit/facter/inventory_spec.rb:89:in `block (4 levels) in 'Finished in 0.16165 seconds (files took 0.97491 seconds to load)9 examples, 2 failuresFailed examples:rspec ./spec/unit/facter/inventory_spec.rb:75 # inventory facts the inventory and metadata facts when setting the inventory fact wil be populated when enabledrspec ./spec/unit/facter/inventory_spec.rb:87 # inventory facts the inventory and metadata facts when
Jira (PDB-5364) Enabling log-queries in 7.7.1 causes JSON serialization failures
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5364 Enabling log-queries in 7.7.1 causes JSON serialization failures Change By: Austin Blatt Fix Version/s: PDB 7.9.0 Fix Version/s: PDB 6.20.0 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.423245.163664995.13060.168620031%40Atlassian.JIRA.
Jira (PDB-5364) Enabling log-queries in 7.7.1 causes JSON serialization failures
Title: Message Title Austin Blatt commented on PDB-5364 Re: Enabling log-queries in 7.7.1 causes JSON serialization failures This issue was resolved while working on PDB-5259. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.423245.163664995.13059.168440066%40Atlassian.JIRA.
Jira (PDB-5364) Enabling log-queries in 7.7.1 causes JSON serialization failures
Title: Message Title Charlie Sharpsteen commented on PDB-5364 Re: Enabling log-queries in 7.7.1 causes JSON serialization failures This issue also affects PuppetDB 6.19.1 in PE 2019.8.9. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.423245.163664995.13055.168020057%40Atlassian.JIRA.
Jira (PDB-5364) Enabling log-queries in 7.7.1 causes JSON serialization failures
Title: Message Title Charlie Sharpsteen updated an issue PuppetDB / PDB-5364 Enabling log-queries in 7.7.1 causes JSON serialization failures Change By: Charlie Sharpsteen Affects Version/s: PDB 6.19.1 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.423245.163664995.13054.167960103%40Atlassian.JIRA.
Jira (PDB-5453) PE PDB Extensions status endpoint is broken
Title: Message Title Stel Abrego assigned an issue to Stel Abrego PuppetDB / PDB-5453 PE PDB Extensions status endpoint is broken Change By: Stel Abrego Assignee: Stel Abrego Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434809.163766000.12991.163940107%40Atlassian.JIRA.
Jira (PDB-5453) PE PDB Extensions status endpoint is broken
Title: Message Title Stel Abrego updated an issue PuppetDB / PDB-5453 PE PDB Extensions status endpoint is broken Change By: Stel Abrego Sprint: HA 2022- 03- 02 -16 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434809.163766000.12990.163940047%40Atlassian.JIRA.
Jira (PDB-5453) PE PDB Extensions status endpoint is broken
Title: Message Title Stel Abrego updated an issue PuppetDB / PDB-5453 PE PDB Extensions status endpoint is broken Change By: Stel Abrego Sprint: HA 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434809.163766000.12989.163820186%40Atlassian.JIRA.
Jira (PDB-5453) PE PDB Extensions status endpoint is broken
Title: Message Title Stel Abrego created an issue PuppetDB / PDB-5453 PE PDB Extensions status endpoint is broken Issue Type: Bug Assignee: Unassigned Created: 2022/02/09 1:56 PM Priority: Normal Reporter: Stel Abrego PDB-5333 changed the status endpoint function structure and that broke PE PDB because it relied on these functions like a library Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PDB-5359) Investigate if we can use the r10k module to deploy a rest API for r10k
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5359 Investigate if we can use the r10k module to deploy a rest API for r10k Change By: David McTavish Team: HA Ghost Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.423049.163653552.12902.160160114%40Atlassian.JIRA.
Jira (PDB-5384) Secure connection between components with HTTPS
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5384 Secure connection between components with HTTPS Change By: David McTavish Team: HA Ghost Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.426482.1638953834000.12901.160160047%40Atlassian.JIRA.
Jira (PDB-5449) Update pgjdbc
Title: Message Title David McTavish commented on PDB-5449 Re: Update pgjdbc merged? Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.433937.1643841148000.12854.1644437640024%40Atlassian.JIRA.
Jira (PDB-5452) Test query performance against JIT enabled Postgres
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5452 Test query performance against JIT enabled Postgres Change By: David McTavish Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434740.1644427481000.12846.1644436860148%40Atlassian.JIRA.
Jira (PDB-5452) Test query performance against JIT enabled Postgres
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5452 Test query performance against JIT enabled Postgres Change By: David McTavish Epic Link: PE-32590 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434740.1644427481000.12845.1644436860102%40Atlassian.JIRA.
Jira (PDB-5452) Test query performance against JIT enabled Postgres
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5452 Test query performance against JIT enabled Postgres Change By: David McTavish Sprint: HA 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434740.1644427481000.12842.1644436800134%40Atlassian.JIRA.
Jira (PDB-5452) Test query performance against JIT enabled Postgres
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5452 Test query performance against JIT enabled Postgres Change By: David McTavish Sprint: HA 2022-03-02 HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434740.1644427481000.12843.1644436800209%40Atlassian.JIRA.
Jira (PDB-4849) [SPIKE] Provide correlation of query information across the pdb and pg logs in debug mode
Title: Message Title David McTavish updated an issue PuppetDB / PDB-4849 [SPIKE] Provide correlation of query information across the pdb and pg logs in debug mode Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.368975.1597254942000.12807.1644436380388%40Atlassian.JIRA.
Jira (PDB-5342) Fix catalog validation "crutch"
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5342 Fix catalog validation "crutch" Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.420541.1634851939000.12816.1644436380562%40Atlassian.JIRA.
Jira (PDB-5192) Start decreasing the (spurious) test logging
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5192 Start decreasing the (spurious) test logging Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.406684.162621166.12809.1644436380476%40Atlassian.JIRA.
Jira (PDB-4805) Don't defer shutdown for cases intended to be immediate
Title: Message Title David McTavish updated an issue PuppetDB / PDB-4805 Don't defer shutdown for cases intended to be immediate Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.365265.1594230865000.12810.1644436380521%40Atlassian.JIRA.
Jira (PDB-5364) Enabling log-queries in 7.7.1 causes JSON serialization failures
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5364 Enabling log-queries in 7.7.1 causes JSON serialization failures Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.423245.163664995.12804.1644436380280%40Atlassian.JIRA.
Jira (PDB-5278) Grouping by a fact with a / in the name generates 500
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5278 Grouping by a fact with a / in the name generates 500 Change By: David McTavish Sprint: HAHA/Grooming, HA 2021-09-22, HA 2021-10-06, HA 2021-10-20, HA 2021-11-03, HA 2021-11-17, HA 2021-12-01, HA 2021-12-15 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.416232.1631899059000.12808.1644436380433%40Atlassian.JIRA.
Jira (PDB-5215) Diagnose and fix pdb SIGHUP handling
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5215 Diagnose and fix pdb SIGHUP handling Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.408847.1627498028000.12814.1644436380548%40Atlassian.JIRA.
Jira (PDB-5334) Fix facts-test/fact-environment-queries
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5334 Fix facts-test/fact-environment-queries Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.420025.1634593536000.12815.1644436380555%40Atlassian.JIRA.
Jira (PDB-5254) Initial blocking sync reporting unexpected error
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5254 Initial blocking sync reporting unexpected error Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.413562.16295.12818.1644436380620%40Atlassian.JIRA.
Jira (PDB-5193) Do first pass jmc profiling of the pdbext endpoints
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5193 Do first pass jmc profiling of the pdbext endpoints Change By: David McTavish Sprint: HAHA/Grooming, HA 2021-08-11 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.406685.1626211988000.12806.1644436380343%40Atlassian.JIRA.
Jira (PDB-5062) Remove password entry from database.ini when using certificate authentication
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5062 Remove password entry from database.ini when using certificate authentication Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.390954.161558092.12812.1644436380535%40Atlassian.JIRA.
Jira (PDB-4305) "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors
Title: Message Title David McTavish updated an issue PuppetDB / PDB-4305 "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.300026.1552508578000.12811.1644436380527%40Atlassian.JIRA.
Jira (PDB-5352) Re-allow branched migrations
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5352 Re-allow branched migrations Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.422927.1636493401000.12817.1644436380574%40Atlassian.JIRA.
Jira (PDB-5093) Describe anonymization_profile(s) and be clear about limitations
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5093 Describe anonymization_profile(s) and be clear about limitations Change By: David McTavish Sprint: HAHA/Grooming, HA 2021-06-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.393967.1617394115000.12813.1644436380543%40Atlassian.JIRA.
Jira (PDB-5260) Fix PQL parse performance problems
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5260 Fix PQL parse performance problems Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.414914.1631118889000.12805.1644436380325%40Atlassian.JIRA.
Jira (PDB-4781) PuppetDB deb should depend on Java 11 or Java 8
Title: Message Title David McTavish updated an issue PuppetDB / PDB-4781 PuppetDB deb should depend on Java 11 or Java 8 Change By: David McTavish Sprint: HAHA/Grooming Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.362058.159162861.12802.1644436320203%40Atlassian.JIRA.
Jira (PDB-5349) PuppetDB blocks primary on restart
Title: Message Title Nick Walker commented on PDB-5349 Re: PuppetDB blocks primary on restart The track we've gone down on this issue is basically to make the blocking portion of startup go as fast as possible. We don't sync reports during that blocking part now, we stopped doing GC on startup and possibly other small improvements. It's not clear that starting without syncing "enough" data is safe to allow agents to query against. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.421318.1635347225000.12797.1644436260034%40Atlassian.JIRA.
Jira (PDB-5428) Test puppetdb for ubuntu-20.04-amd64
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5428 Test puppetdb for ubuntu-20.04-amd64 Change By: David McTavish Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.432878.1643305759000.12697.1644433620207%40Atlassian.JIRA.
Jira (PDB-5421) Test puppetdb for sles-15-x86_64
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5421 Test puppetdb for sles-15-x86_64 Change By: David McTavish Story Points: 2.5 3 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.430482.164252957.12696.1644433620201%40Atlassian.JIRA.
Jira (PDB-5370) Test puppetdb for redhatfips-8-x86_64
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5370 Test puppetdb for redhatfips-8-x86_64 Change By: David McTavish Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.423374.1636749039000.12695.1644433620156%40Atlassian.JIRA.
Jira (PDB-5421) Test puppetdb for sles-15-x86_64
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5421 Test puppetdb for sles-15-x86_64 Change By: David McTavish Story Points: 2.5 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.430482.164252957.12690.1644433560031%40Atlassian.JIRA.
Jira (PDB-5421) Test puppetdb for sles-15-x86_64
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5421 Test puppetdb for sles-15-x86_64 Change By: David McTavish Sprint: HAHA/Grooming HA 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.430482.164252957.12682.1644433320278%40Atlassian.JIRA.
Jira (FACT-3095) Build Facter for JRuby on redhatfips-8-x86_64
Title: Message Title Molly Waggett updated an issue Facter / FACT-3095 Build Facter for JRuby on redhatfips-8-x86_64 Change By: Molly Waggett Sprint: Froyo - On Deck 3/2/2022 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.423338.1636748933000.12674.1644433260309%40Atlassian.JIRA.
Jira (PDB-5420) Build puppetdb for sles-15-x86_64
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5420 Build puppetdb for sles-15-x86_64 Change By: David McTavish Sprint: HAHA/Grooming HA 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.430481.1642529566000.12677.1644433260445%40Atlassian.JIRA.
Jira (PDB-5418) Enable sles-15-x86_64 builds for puppetdb
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5418 Enable sles-15-x86_64 builds for puppetdb Change By: David McTavish Sprint: HAHA/Grooming HA 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.430450.1642529446000.12675.1644433260356%40Atlassian.JIRA.
Jira (PDB-5419) Enable sles-15-x86_64 test pipeline for puppetdb
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5419 Enable sles-15-x86_64 test pipeline for puppetdb Change By: David McTavish Sprint: HAHA/Grooming HA 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.430451.164252945.12676.1644433260401%40Atlassian.JIRA.
Jira (PDB-5450) Slow fact queries after PuppetDB 7.9.0 upgrade when using Postgres 12 with jit enabled
Title: Message Title David McTavish updated an issue PuppetDB / PDB-5450 Slow fact queries after PuppetDB 7.9.0 upgrade when using Postgres 12 with jit enabled Change By: David McTavish Method Found: Needs Assessment Customer Feedback Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434144.1643897486000.12378.1644429120092%40Atlassian.JIRA.
Jira (PUP-11440) No option to fail fast when agent-specified environment does not exist
Title: Message Title Lisa Ross updated an issue Puppet / PUP-11440 No option to fail fast when agent-specified environment does not exist Change By: Lisa Ross Sprint: Phoenix 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.433415.1643667502000.12366.1644428880285%40Atlassian.JIRA.
Jira (PUP-11437) puppet lookup fails to interpolate topscope variables when an environment is specified
Title: Message Title Lisa Ross updated an issue Puppet / PUP-11437 puppet lookup fails to interpolate topscope variables when an environment is specified Change By: Lisa Ross Sprint: Phoenix 2022-03-02 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.432982.1643328691000.12359.1644428820203%40Atlassian.JIRA.
Jira (PDB-5452) Test query performance against JIT enabled Postgres
Title: Message Title Stel Abrego created an issue PuppetDB / PDB-5452 Test query performance against JIT enabled Postgres Issue Type: Task Assignee: Unassigned Created: 2022/02/09 9:24 AM Priority: Normal Reporter: Stel Abrego https://tickets.puppetlabs.com/browse/PDB-5450 describes a performance regression when using PDB with Postgres JIT enabled. This started being the default since Postgres 12. With the upcoming upgrade to Postgres 14 in PE, we need to test how JIT performance compares with it turned off. In particular, this query is probably a good candidate to start with: https://github.com/puppetlabs/puppetdb/pull/3592 Add Comment This message was sent by Atlassian Jira
Jira (PUP-11452) puppetserver_gem doesn't install gems when they are loaded by facter
Title: Message Title Jarret Lavallee commented on PUP-11452 Re: puppetserver_gem doesn't install gems when they are loaded by facter Thanks for reviewing this josh. I opened up https://github.com/puppetlabs/puppet/pull/8872 with the changes. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "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.434448.1644247869000.12179.1644420420085%40Atlassian.JIRA.
Jira (HI-628) convert_to: Sensitive only unless undef
Title: Message Title
Cocker updated an issue
Hiera / HI-628
convert_to: Sensitive only unless undef
Change By:
Cocker
h2. Context:Hiera provides the Convert-Function{noformat}lookup_options: blubb::my_variable1:convert_to: Sensitive blubb::my_variable2:convert_to: Sensitiveblubb::my_variable1: MY_PASSWORD# Variable intentionally left emptyblubb::my_variable2:{noformat} With {{blubb::my_variable2}} this leads to {{{}Sensitive[undef]{}}}, and this makes...{noformat}class blubb( Optional[Variant[String, Sensitive[String]]] $my_variable2,) {}{noformat}... not accepting the Variable:{noformat}Class[Blubb]: parameter 'my_variable2' expects a value of type Undef, String or Sensitive[String], got Sensitive[Undef]{noformat} h2. Improvement:The Convert-Function should leave {{undef}} unconverted, and return just {{undef}} instead of {{{}Sensitive[undef]{}}}. h2. References:[https://github.com/theforeman/puppet-katello/pull/436] [https://github.com/theforeman/puppet-foreman/pull/1018] .
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (HI-628) convert_to: Sensitive only unless undef
Title: Message Title
Cocker updated an issue
Hiera / HI-628
convert_to: Sensitive only unless undef
Change By:
Cocker
h2. Context:Hiera provides the Convert-Function {noformat} lookup_options: blubb::my_variable1:convert_to: Sensitive blubb::my_variable2:convert_to: Sensitiveblubb::my_variable1: MY_PASSWORD# Variable intentionally left emptyblubb::my_variable2:{noformat} With {{blubb::my_variable2}} this leads to {{ {} Sensitive[undef] { }} } , and this makes... {noformat} class blubb( Optional[Variant[String, Sensitive[String]]] $my_variable2,) {}{noformat} ... not accepting the Variable: {noformat} Class[Blubb]: parameter 'my_variable2' expects a value of type String or Sensitive[String], got Sensitive[Undef]{noformat} h2. Improvement:The Convert-Function should leave {{undef}} unconverted, and return just {{undef}} instead of {{{}Sensitive[undef]{}}}. h2. References:[https://github.com/theforeman/puppet-katello/pull/436 #discussion_r802535218 ] [https://github . com/theforeman/puppet-foreman/pull/1018] .
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (HI-628) convert_to: Sensitive only unless undef
Title: Message Title
Cocker updated an issue
Hiera / HI-628
convert_to: Sensitive only unless undef
Change By:
Cocker
h2. Context:Hiera provides the Convert-Function{ { noformat} lookup_options: }} {{ }}{{{} blubb:: {}}}{{{} my_variable1: {}}} {{}}{{ convert_to: Sensitive }} {{ }}{{{} blubb:: {}}}{{{} my_variable2: {}}} {{}}{{ convert_to: Sensitive }} {{}} {{{} blubb::my_variable1 {}}}{{{} : MY_PASSWORD {}}} {{ # Variable intentionally left empty }} {{{} blubb:: {}}}{{{} my_variable2: {}}}{{{}{}}} { { noformat } } With {{blubb::my_variable2}} this leads to {{ {} Sensitive[undef] { }} } , and this makes...{ { noformat} class blubb( }} {{ Optional[Variant[String, Sensitive[String]]] $my_variable2, }} {{ ) {} {noformat } } ... not accepting the Variable:{ { noformat} Class[Blubb]: parameter 'my_variable2' expects a value of type String or Sensitive[String], got Sensitive[Undef] {noformat } } h2. Improvement:The Convert-Function should leave {{undef}} unconverted, and return just {{undef}} instead of {{{}Sensitive[undef]{}}}. h2. References:[https://github.com/theforeman/puppet-katello/pull/436#discussion_r802535218].
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (HI-628) convert_to: Sensitive only unless undef
Title: Message Title
Cocker created an issue
Hiera / HI-628
convert_to: Sensitive only unless undef
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2022/02/09 4:10 AM
Priority:
Normal
Reporter:
Cocker
Context: Hiera provides the Convert-Function lookup_options: }}{{{}blubb::my_variable1: }}{{ convert_to: Sensitive }}{{{}blubb::my_variable2: }}{{ convert_to: Sensitive {{}} blubb::my_variable1: MY_PASSWORD # Variable intentionally left empty blubb::my_variable2:{} {{}} With blubb::my_variable2 this leads to Sensitive[undef], and this makes... class blubb( Optional[Variant[String, Sensitive[String]]] $my_variable2, ) {} ... not accepting the Variable: Class[Blubb]: parameter 'my_variable2' expects a value of type String or Sensitive[String], got Sensitive[Undef] Improvement: The Convert-Function should leave undef unconverted, and return just undef instead of Sensitive[undef]. References: https://github.com/theforeman/puppet-katello/pull/436#discussion_r802535218 .
Add Comment
