Jira (PUP-4024) Puppet should allow setting null property value
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4024 Puppet should allow setting null property value Change By: Josh Cooper Epic Link: PUP-7560 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.68190.1424201506000.11534.1644385620036%40Atlassian.JIRA.
Jira (PUP-4514) Improve external syntax checking of heredoc
Title: Message Title Josh Cooper commented on PUP-4514 Re: Improve external syntax checking of heredoc We don’t have plans on implementing this anytime soon so I’m going to close. 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.78334.143057478.11533.1644385380029%40Atlassian.JIRA.
Jira (PUP-11438) An iterable returned by tree_each iterator does not work with reduce
Title: Message Title Heston Hoffman assigned an issue to Heston Hoffman Puppet / PUP-11438 An iterable returned by tree_each iterator does not work with reduce Change By: Heston Hoffman Assignee: Heston Hoffman 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.433034.1643390827000.11416.1644359700395%40Atlassian.JIRA.
Jira (PUP-11452) puppetserver_gem doesn't install gems when they are loaded by facter
Title: Message Title Josh Cooper commented on PUP-11452 Re: puppetserver_gem doesn't install gems when they are loaded by facter Thanks for digging into this issue jarret.lavallee I agree that it's better to shell out than try to list gems "in process" as the puppetserver_gem provider is currently doing. Could you submit your changes (https://github.com/jarretlavallee/puppetlabs-puppetserver_gem/commit/327c7c90f40874d3c7d5f31d8708cf12366cca63) as a PR to puppet#6.x? We can help with the tests if needed. 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.11408.1644359400127%40Atlassian.JIRA.
Jira (PUP-11446) Facts returning nil are converted to empty string
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11446 Facts returning nil are converted to empty string Change By: Josh Cooper Team: Phoenix 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.433923.1643832932000.11389.1644358200032%40Atlassian.JIRA.
Jira (PUP-11438) An iterable returned by tree_each iterator does not work with reduce
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11438 An iterable returned by tree_each iterator does not work with reduce Change By: Josh Cooper Team: Phoenix 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.433034.1643390827000.11388.1644358140059%40Atlassian.JIRA.
Jira (PUP-11428) Puppet Agent does not automatically refresh CRLs on crl_refresh_interval
Title: Message Title Josh Cooper commented on PUP-11428 Re: Puppet Agent does not automatically refresh CRLs on crl_refresh_interval ahamilto This is indeed a bug, but it's yet another reason (out of many) to run puppet from cron or scheduled task. Most folks use that combined with the fqdn_rand function to space agent runs out across the 30 minute interval. As such, we're not likely to fix this any time soon. 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.429291.1641916206000.11387.1644358080046%40Atlassian.JIRA.
Jira (PUP-11428) Puppet Agent does not automatically refresh CRLs on crl_refresh_interval
Title: Message Title Nirupama Mantha updated an issue Puppet / PUP-11428 Puppet Agent does not automatically refresh CRLs on crl_refresh_interval Change By: Nirupama Mantha Affects Version/s: PUP 6.25.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.429291.1641916206000.11383.1644357600147%40Atlassian.JIRA.
Jira (PUP-11438) An iterable returned by tree_each iterator does not work with reduce
Title: Message Title Nirupama Mantha commented on PUP-11438 Re: An iterable returned by tree_each iterator does not work with reduce We currently don't plan to address this, you can submit a PR if you would like us to review it. We will update our documentation to remove it from our list. cc/heston.hoffman 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.433034.1643390827000.11372.1644356820028%40Atlassian.JIRA.
Jira (PUP-11451) Make collecting exported resources optional
Title: Message Title Nirupama Mantha commented on PUP-11451 Re: Make collecting exported resources optional What do you think about this request? ben.ford charliesharpsteen nick.walker 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.434328.1643983687000.11346.1644355260070%40Atlassian.JIRA.
Jira (FACT-3095) Build Facter for JRuby on redhatfips-8-x86_64
Title: Message Title David McTavish updated an issue Facter / FACT-3095 Build Facter for JRuby on redhatfips-8-x86_64 Change By: David McTavish Sprint: Froyo/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.423338.1636748933000.11300.1644350400137%40Atlassian.JIRA.
Jira (FACT-3103) Build Facter for JRuby on sles-15-x86_64
Title: Message Title David McTavish updated an issue Facter / FACT-3103 Build Facter for JRuby on sles-15-x86_64 Change By: David McTavish Sprint: Froyo/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.430447.1642529435000.11269.1644348240298%40Atlassian.JIRA.
Jira (PUP-10928) Puppet falls back to non-rich data if there is binary data in the catalog
Title: Message Title Josh Cooper commented on PUP-10928 Re: Puppet falls back to non-rich data if there is binary data in the catalog It would be fairly easy to add a puppet setting to disable falling back to *PSON*. The code where the fallback happens is:https://github.com/puppetlabs/puppet/blob/4772afa194402a3876069785a178611797a8eb7d/lib/puppet/indirector/catalog/json.rb#L21-L23. So to implement this, I think we'd want: A new setting in defaults.rb, located near "preferred_serialization_format" something like "allow_pson_serialization=true|false". The new setting should allow the fallback by default. If the fallback is triggered, but the fallback is not allowed, then log an error and exception at "err" level instead of "debug". If the fallback is triggered and the fallback is allowed, then log a warning (instead of info) saying that PSON is deprecated and will be removed in a future release. Another option would be to add a "rich_data_pson" serialization format, but I dislike that because 1) it doesn't solve the "accidentally putting binary data in the catalog" problem and 2) we want to get away from PSON as much as possible, see PUP-3852. 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
Jira (PUP-10928) Puppet falls back to non-rich data if there is binary data in the catalog
Title: Message Title Nick Hall commented on PUP-10928 Re: Puppet falls back to non-rich data if there is binary data in the catalog This has been open a year - we've recently hit this. Is that at least a workaround so that if somebody adds binary data to a catalogue mistakenly that we can stop puppet overwriting files with the Deferred() (e.g) strings rather than the results of the call? e.g. can we stop it falling back to JSON? If not, this has the potential to have a lot of impact. 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.388074.1613713885000.10790.1644331260469%40Atlassian.JIRA.
Jira (PUP-11446) Facts returning nil are converted to empty string
Title: Message Title
Sean Millichamp commented on PUP-11446
Re: Facts returning nil are converted to empty string
josh To be clear, what I observed and reported doesn't seem to be a facter issue. In fact, interestingly, facter by itself seem to have the inverse behavior as to what I saw versus when the facts are presented in Puppet. Given two Ruby facts, one simple fact which returns "nil" and one which returns a hash containing a single key with a nil value you get these results with the facter CLI:
facter --version 3.14.17 (commit ce1f2bb4a91a1ac4ae5852091c96ae6ee3712e23)
facter -p --json mysimplefact mystructuredfact { "mysimplefact": "", "mystructuredfact": { "mykey": null } }
Facter does the correct thing with the structured fact, but turns the simple fact nil value into a string. Now, those same Facts as presented by Puppet: Notice: mystructuredfact: {"mykey":""} Notice: mysimplefact: null Notice: mysimplefact is key in facts hash: false The value of the structured fact key is now the empty string, the simple fact value is now null, and on top of that the fact doesn't even get added to the $facts hash. The behavior I think we should have is that the data types returned by Facter should be preserved when used in Puppet. I think that a fact which returns nil as its only value should continue to not be present in the facts hash. At the very least, the behavior should be consistent between Puppet and Facter. You can see the quick module I put together for the above testing here: https://github.com/seanmil/facttest As an aside to this issue, Puppet type system support in facts would be awesome!
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
