Jira (PUP-10656) Provide a JSON terminus for facts
Title: Message Title Josh Cooper commented on PUP-10656 Re: Provide a JSON terminus for facts Passed CI in d61cf32faa Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.371009.1599069868000.70093.1604366340032%40Atlassian.JIRA.
Jira (PUP-8660) "puppet apply" should not ignore updated custom facts within the module under test
Title: Message Title Josh Cooper commented on PUP-8660 Re: "puppet apply" should not ignore updated custom facts within the module under test This is a hard thing to fix because some people distribute report processors from the primary compiler to secondary compilers, and in that case, you do want the pluginsync'ed report processor to take precedence. This isn't going to make puppet7 as more research is required to find a path forward on this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.245552.1523589265000.70084.1604364540046%40Atlassian.JIRA.
Jira (PUP-8660) "puppet apply" should not ignore updated custom facts within the module under test
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8660 "puppet apply" should not ignore updated custom facts within the module under test Change By: Josh Cooper Fix Version/s: PUP 7.0.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.245552.1523589265000.70085.1604364540103%40Atlassian.JIRA.
Jira (PUP-10253) Undeprecate source_permissions
Title: Message Title Karl Pietri commented on PUP-10253 Re: Undeprecate source_permissions Ever since the deprecation warning showed up I've been searching for a solution for the use case of a mixed directories of files/scripts put out by teams that don't have access to puppet code. Its a common pattern and there just isn't a good solution without keeping this functionality. Moving to something that only does the mode would be perfectly acceptable and probably better. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.343626.1579985788000.69969.1604357640023%40Atlassian.JIRA.
Jira (PUP-10720) Update `cadir` default to return the new location post-migration
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10720 Update `cadir` default to return the new location post-migration Change By: Justin Stoller Sprint: Froyo 11/02/2020 , Froyo 11/09/2020 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.375129.1602802813000.69916.1604356980107%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10772 fresh puppet agent installation fails when msgpack is enabled on puppetserver Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.376434.1603966281000.69687.1604348940315%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10772 fresh puppet agent installation fails when msgpack is enabled on puppetserver Change By: Josh Cooper Fix Version/s: PUP 6.20.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.376434.1603966281000.69686.1604348940269%40Atlassian.JIRA.
Jira (PUP-10772) fresh puppet agent installation fails when msgpack is enabled on puppetserver
Title: Message Title Josh Cooper moved an issue Puppet / PUP-10772 fresh puppet agent installation fails when msgpack is enabled on puppetserver Change By: Josh Cooper Key: PA PUP - 3441 10772 Project: Puppet Agent Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.376434.1603966281000.69619.1604346660096%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Martin Alfke commented on FACT-2847 Re: Facter 4 breaks rspec on fact test Hi Sebastian Miclea , moving fact stubbing in the before block totally makes sense. I can confirm working tests when using the following entries in .sync.yml file: --- spec/spec_helper.rb: mock_with: ':rspec' Gemfile: optional: ':development': - gem: facter version: '> 4.0.43' Don't forget to run pdk update! Test shows the following result: pdk test unit --tests spec/unit/facter/puppet_agent_fact_spec.rb pdk (INFO): Using Ruby 2.5.8 pdk (INFO): Using Puppet 6.19.0 [✔] Preparing to run the
Jira (PUP-2173) puppet config set certname accepts upper-case names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2173 puppet config set certname accepts upper-case names Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Previously, the "puppet config set" command could set a value that was invalid, which would cause puppet to fail the next time it ran or the service was restarted. Now the command validates the settings' value prior to committing the change to puppet.conf. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.31150.1396893989000.69307.1604338200072%40Atlassian.JIRA.
Jira (FACT-2847) Facter 4 breaks rspec on fact test
Title: Message Title Sebastian Miclea commented on FACT-2847 Re: Facter 4 breaks rspec on fact test Hi Martin Alfke, We had an other more in depth look at this case and understood what happens. My first suggestion for the fix (moving the Facter.fact(:os) the before block) is still correct and will be required in order to have this test working. We found out that the second failure you had, with uname being called, was caused by a bug in how values were reset. The good news is that that was already fixed in 4.0.43. Running the tests using the latest Facter should have this test passing. Let us know if you encounter any other issues. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.376201.1603820546000.69123.1604329140029%40Atlassian.JIRA.
Jira (FACT-2833) Investigate performance for hypervisor fact
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2833 Investigate performance for hypervisor fact Change By: Andrei Filipovici Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "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.374205.1602078248000.69040.1604305560100%40Atlassian.JIRA.
