Jira (PUP-10491) Allow adding descriptive or administrative information to resources
Title: Message Title Gene Liverman commented on PUP-10491 Re: Allow adding descriptive or administrative information to resources Ciprian Badescu - we kinda do but this would be even better. We utilize https://forge.puppet.com/modules/ploperations/profile_metadata, which we own, do accomplish a higher level version of this. We combine that with https://forge.puppet.com/modules/ploperations/meta_motd to show metadata in the message of the day (motd) and also have https://github.com/puppetlabs/infinitory which gives us a web interface to browse this information. These serve us fairly well but an in-built solution would be way better and could easily enhance what we are already doing - I could absolutely see utilizing what is proposed here to enhance one or both of our modules and to enhance infinitory. Feel free to hit me up if you'd like to see a live demo of what this looks like in our environment. 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.357687.1588699805000.149810.1633610820032%40Atlassian.JIRA.
Jira (PUP-10957) Support ruby 3
Title: Message Title Gene Liverman commented on PUP-10957 Re: Support ruby 3 FWIW, I was pointed towards https://github.com/puppetlabs/puppet/blob/7.6.1/lib/puppet/util.rb#L469-L476 in slack as a key issue as a by product of https://github.com/ruby/uri/issues/14 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.390422.161530306.16487.1619106900037%40Atlassian.JIRA.
Jira (PUP-10959) Lock loaders using a single central lock
Title: Message Title Gene Liverman updated an issue Puppet / PUP-10959 Lock loaders using a single central lock Change By: Gene Liverman Labels: customer0 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.390496.1615338623000.162190.1615391640191%40Atlassian.JIRA.
Jira (PUP-10958) Load everything in an environment upfront before first compile
Title: Message Title Gene Liverman updated an issue Puppet / PUP-10958 Load everything in an environment upfront before first compile Change By: Gene Liverman Labels: customer0 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.390453.1615313252000.161057.1615313520494%40Atlassian.JIRA.
Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title Gene Liverman updated an issue Facter / FACT-2937 'puppet facts show' logs error when stdlib is installed Change By: Gene Liverman Labels: customer0 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.386159.1612446678000.155065.1614704220195%40Atlassian.JIRA.
Jira (FACT-2882) Facter 4.0.x on Windows does not return the domain when set in the registry
Title: Message Title Gene Liverman commented on FACT-2882 Re: Facter 4.0.x on Windows does not return the domain when set in the registry Has the fixed code landed in an agent yet? 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.379598.1606874598000.109762.1610028600096%40Atlassian.JIRA.
Jira (FACT-2882) Facter 4.0.x on Windows does not return the domain when set in the registry
Title: Message Title Gene Liverman updated an issue Facter / FACT-2882 Facter 4.0.x on Windows does not return the domain when set in the registry Change By: Gene Liverman Labels: customer0 doc_reviewed platform_7.2 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.379598.1606874598000.107840.1609865160058%40Atlassian.JIRA.
Jira (PUP-9644) Improve documentation around sensitive data in puppet
Title: Message Title Gene Liverman commented on PUP-9644 Re: Improve documentation around sensitive data in puppet Happy to help. Ben Ford also has a lot of good insight into 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.304741.1555347266000.79244.1591293360137%40Atlassian.JIRA.
Jira (PUP-10498) host resources don't support stock Linux configurations
Title: Message Title Gene Liverman created an issue Puppet / PUP-10498 host resources don't support stock Linux configurations Issue Type: Bug Assignee: Unassigned Created: 2020/05/11 5:53 AM Priority: Normal Reporter: Gene Liverman For all version of Puppet that I am aware of, the host resource type does not support a stock configuration of Linux. In particular, both RHEL/CentOS and Debian/Ubuntu flavors come with IPv6 enabled by default. This results in two stock entries in /etc/hosts that resemble this: 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback As it stands today, running "puppet resource host" will not return both of these entries - it will only return the IPv4 variant. Additionally, it seems to be impossible to precisely recreate this pair of entries, or any other entry for which a name has both an IPv4 and an IPv6 address.
Jira (FACT-2354) Provide fact fixtures on new facter releases to facterdb
Title: Message Title Gene Liverman commented on FACT-2354 Re: Provide fact fixtures on new facter releases to facterdb I am game for owning this. Is Nights Watch who I would need to coordinate with? cc: Christopher Thorn David Hayden Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.345749.158135502.21453.1581438121183%40Atlassian.JIRA.
Jira (PUP-9213) Puppet agent should indicate which HTTP timeout has expired
Title: Message Title Gene Liverman commented on PUP-9213 Re: Puppet agent should indicate which HTTP timeout has expired Awesome thanks. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.279317.1539016372000.7754.1580432580379%40Atlassian.JIRA.
Jira (PUP-9213) Puppet agent should indicate which HTTP timeout has expired
Title: Message Title Gene Liverman commented on PUP-9213 Re: Puppet agent should indicate which HTTP timeout has expired Is there a separate process that’s getting rid of the lib/puppet one Melissa Stone ? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.279317.1539016372000.7633.1580429880611%40Atlassian.JIRA.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Gene Liverman commented on PDOC-273 Re: puppet-strings should pull documentation from the lib folder too Thanks for the info Jorie Tappa! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.294635.1549292365000.89532.1567803120132%40Atlassian.JIRA.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Gene Liverman commented on PDOC-273 Re: puppet-strings should pull documentation from the lib folder too Jorie Tappa - I saw that you made a small edit on this and was curious where it sat on the priority list. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.294635.1549292365000.89366.1567797120151%40Atlassian.JIRA.
Jira (PUP-9254) Agent Functions - add eval() function
Title: Message Title Gene Liverman commented on PUP-9254 Re: Agent Functions - add eval() function As a sidebar, I have often wanted to be able to use puppet functions on agented nodes while calling puppet apply to test something so pluginsync'ing them is something that sounds appealing to me (totally leaving out other implications). Just my $0.02 on that idea. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9254) Agent Functions - add eval() function
Title: Message Title
Gene Liverman commented on PUP-9254
Re: Agent Functions - add eval() function
I am very much in favor of this or something like it. I have already run into instance where I want to use Deferred to call a function so that the call is coming from the agent and then transform that data. Here is an example of what I am doing in a non-Deferred manor and:
$consul_name_servers = consul_data::get_service_nodes($consul_server, 'consul')
$consul_dns_port = pick(consul_data::get_key($consul_server, 'consul-dns/port'), '8600')
$nameserver_hash = $consul_name_servers.reduce( {} ) |$memo, $nameserver| {
$memo + { "${nameserver['Node']}" => "${nameserver['Address']}:${consul_dns_port}" }
}
haproxy::resolver { 'consul':
nameservers => $nameserver_hash,
resolve_retries => 3,
timeout => {
'retry' => '2s',
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Gene Liverman commented on PDOC-273 Re: puppet-strings should pull documentation from the lib folder too I have been updating the docs for another module and noticed that not all the tags listed in https://puppet.com/docs/puppet/6.0/puppet_strings.html are actually picked up from ruby functions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Gene Liverman commented on PDOC-273 Re: puppet-strings should pull documentation from the lib folder too Pinging Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Gene Liverman updated an issue Puppet Strings / PDOC-273 puppet-strings should pull documentation from the lib folder too Change By: Gene Liverman Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Gene Liverman commented on PDOC-273 Re: puppet-strings should pull documentation from the lib folder too An example of a module where parts of it get documented and others don't is https://github.com/ploperations/ploperations-classification An example of puppet strings providing zero help is https://github.com/ploperations/ploperations-consul_data Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-273) puppet-strings should pull documentation from the lib folder too
Title: Message Title Gene Liverman created an issue Puppet Strings / PDOC-273 puppet-strings should pull documentation from the lib folder too Issue Type: Bug Assignee: Unassigned Created: 2019/02/04 6:59 AM Priority: Normal Reporter: Gene Liverman As a module author I write my documentation in a format compatible with puppet strings. I expect that when I run puppet strings generate that all that documentation will end up in REFERENCE.md however none of the docs that I write on the ruby files in the lib folder are processed. The end result of this is a need to manually document part of my module while having the rest of the docs auto-generated. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Gene Liverman commented on PUP-8376 Re: Revert to production when agent-specified environment doesn't exist Henrik Lindberg well that sounds interesting Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1898) Provide core facts or supported module with commonWindows paths
Title: Message Title Gene Liverman commented on FACT-1898 Re: Provide core facts or supported module with common Windows paths Glenn Sarti turned me on to https://forge.puppet.com/puppet/windows_env#facts which seems to already implement what I am after. That module is an approved one so I think the best course of action would to be promote the functionality Genn added to it and that the module is pulled in by in https://forge.puppet.com/puppetlabs/windows already. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Gene Liverman commented on PUP-8376 Re: Revert to production when agent-specified environment doesn't exist Not sure what I think about the ENC idea as that would be a layer between Puppet and PE (this is an off-the-cuff thought) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1898) Provide core facts or supported module with common Windows paths
Title: Message Title Gene Liverman commented on FACT-1898 Re: Provide core facts or supported module with common Windows paths Happy to chat any time! Are you around tomorrow? On Wed, Dec 19, 2018 at 5:21 PM Branan Riley (JIRA) < – Gene Liverman Sr. Site Reliability Engineer gene.liver...@puppet.com Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1898) Provide core facts or supported module with common Windows paths
Title: Message Title Gene Liverman commented on FACT-1898 Re: Provide core facts or supported module with common Windows paths https://github.com/ploperations/ploperations-system_facts is up with a readme. More to come. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1898) Provide core facts or supported module with common Windows paths
Title: Message Title Gene Liverman commented on FACT-1898 Re: Provide core facts or supported module with common Windows paths After discussion in the Puppet Windows HipChat room it sounds like a module is the path forward here. I am going to start creating one in the ploperations namespace to get the ball rolling. /cc James Pogran Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1898) Provide core facts or supported module with common Windows paths
Title: Message Title Gene Liverman created an issue Facter / FACT-1898 Provide core facts or supported module with common Windows paths Issue Type: Improvement Assignee: Unassigned Created: 2018/12/19 6:54 AM Labels: customer0 Priority: Normal Reporter: Gene Liverman A core part of writing a good script on Windows is using some of the stock environment variables instead of assuming you always know what drive is the system drive and where Windows itself are installed. The same reasons that this is important when scripting are important when writing Puppet code yet there is no way for us to use this info. I am requesting that we provide this info as core facts or, if that is not acceptable, as part of a supported module. People such as Ethan Brown, Glenn Sarti, John O'Connor, William Hurt, and Michael Lombardi will likely know more of what should be contained in something like this but, at a minimum, I think it should the file paths listed on https://ss64.com/nt/syntax-variables.html Having this info in Puppet contributes directly to Windows being a first-class part of our ecosystem. FWIW, I am happy to contribute to the work to make this happen once a decision about where it should live has been reached. I imagine Daniel Parks would be too due to recent work he's been doing.
Jira (BOLT-921) Updates to Bolt installation docs
Title: Message Title Gene Liverman commented on BOLT-921 Re: Updates to Bolt installation docs Looks good now Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-921) Updates to Bolt installation docs
Title: Message Title Gene Liverman commented on BOLT-921 Re: Updates to Bolt installation docs My only thought is that I would make a single Linux heading like there is for Windows and macOS. I also think putting the repo type in the heading for the Linux ones is overkill. Overall, much better and thank you! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9213) Puppet agent should indicate which HTTP timeout has expired
Title: Message Title Gene Liverman updated an issue Puppet / PUP-9213 Puppet agent should indicate which HTTP timeout has expired Change By: Gene Liverman Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-615) I want to install a puppet-agent with bolt
Title: Message Title Gene Liverman commented on BOLT-615 Re: I want to install a puppet-agent with bolt is this intended to work with both foss agents and pe agents? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast ACPL String results to Sensitive for Sensitive-typed class parameters
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast ACPL String results to Sensitive for Sensitive-typed class parameters Reid Vandewiele I noticed some changes in title... this isn't limited to strings but also to wrapping the other types too. I believe this includes arrays, hashes, and integers. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Gotcha Reid Vandewiele. With much help from others, I also realized the hiera side of this is doable via a regex on key names like so in common.yaml: --- lookup_options: '^profile::.+::sensitive_\w+$': convert_to: 'Sensitive' # that would cover keys like this: profile::some_web_app::sensitive_db_password: ENC[PKCS7,] # and would skip keys like this: profile::some_web_app::table_of_sensitive_stuff_name: 'foo' Learning this makes me feel better about the idea of PUP-8946 not being done.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Reid Vandewiele fwiw, I assumed PUP-8946 would be a toggle, not a default, as I think was already talked about in that ticket. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Josh Cooper I don't think this ticket and PUP-8946 are mutually exclusive. The other one is the one I am most excited about but I think this one would provide real value also. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Henrik Lindberg - can you elaborate on using a regex for the key in lookup_options? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8946) Return all eyaml encrypted values from hiera as Sensitive
Title: Message Title Gene Liverman updated an issue Puppet / PUP-8946 Return all eyaml encrypted values from hiera as Sensitive Change By: Gene Liverman Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman updated an issue Puppet / PUP-8947 Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Change By: Gene Liverman Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title
Gene Liverman created an issue
Puppet / PUP-8947
Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/06/15 6:29 AM
Priority:
Normal
Reporter:
Gene Liverman
It seems that when doing a hiera lookup for a class parameter that is of type Sensitive that the string being returned should automatically be cast to Sensitive. The use case here is that I store sensitive data in hiera encrypted in eyaml. I have corresponding profiles that have class parameters defined like so:
class profile::some_profile (
Sensitive[String[1]] $some_sensitive_value,
) {
# puppet code here
}
It is currently a significant amount of extra work to mark each hiera
Jira (PUP-8946) Return all eyaml encrypted values from hiera as Sensitive
Title: Message Title Gene Liverman created an issue Puppet / PUP-8946 Return all eyaml encrypted values from hiera as Sensitive Issue Type: Improvement Assignee: Unassigned Created: 2018/06/15 6:27 AM Priority: Normal Reporter: Gene Liverman It seems to me that it would be logical to assume that if a value is encrypted via eyaml in hiera that it is sensitive. Based on this, I think all such values should be returned wrapped in the Sensitive type. The result would be that if a String is looked up that a Sensitive[String] would be returned. The same kind of wrapping would hold true for Array, Hash, and Integer too. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-380) Support ed25519 out-of-the-box
Title: Message Title Gene Liverman commented on BOLT-380 Re: Support ed25519 out-of-the-box Nothing really. I kinda like the idea of a gem that works out the other things to pull in though for people who do need the support. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1820) facter os is missing fields on arm
Title: Message Title
Gene Liverman created an issue
Facter / FACT-1820
facter os is missing fields on arm
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/02/19 2:08 AM
Priority:
Normal
Reporter:
Gene Liverman
When I run facter os on an x86_64 system I get this output:
{
architecture => "x86_64",
family => "RedHat",
hardware => "x86_64",
name => "CentOS",
release => {
full => "7.4.1708",
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Gene Liverman commented on PUP-8376 Re: Revert to production when agent-specified environment doesn't exist I will let Daniel Parks answer your specific question Henrik Lindberg but, before coming to Puppet, we used FOSS puppet in a master-based environment and the inability for an agent to deal with its environment not existing caused us much pain. We did all of our work on our control repo and internal modules via the Git Flow workflow which is much the same as previously described. More than once we missed the step of moving a node back to production before deleting the branch and ended up having to connect directly to that node and manually change its branch back. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8103) Structured facts in metadata.json
Title: Message Title
Gene Liverman created an issue
Puppet / PUP-8103
Structured facts in metadata.json
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2017/10/30 1:38 PM
Priority:
Normal
Reporter:
Gene Liverman
While removing legacy facts from my personal modules I found that I still have to use them in metadata.json at least according to https://puppet.com/docs/puppet/5.3/modules_metadata.html It would be nice to be able to use structured facts in the operatingsystem_support section.
For example, to be able to replace this
"operatingsystem_support": [
{
"operatingsystem": "RedHat",
"operatingsystemrelease": [
Jira (PUP-8059) rake validate fails on modules with plans
Title: Message Title Gene Liverman commented on PUP-8059 Re: rake validate fails on modules with plans Ah, didn't realize that. Thanks Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8059) rake validate fails on modules with plans
Title: Message Title Gene Liverman commented on PUP-8059 Re: rake validate fails on modules with plans Ideally the parser would just recognize the keyword plan and not need --tasks passed to it but instead adapt accordingly. On Tue, Oct 17, 2017 at 3:10 PM Henrik Lindberg (JIRA) < – Gene Liverman Sr. Site Reliability Engineer gene.liver...@puppet.com Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8059) rake validate fails on modules with plans
Title: Message Title Gene Liverman created an issue Puppet / PUP-8059 rake validate fails on modules with plans Issue Type: Bug Affects Versions: PUP 5.3.2 Assignee: Unassigned Created: 2017/10/16 9:55 AM Environment: Bunder-based environment used by Travis CI Priority: Normal Reporter: Gene Liverman puppetlabs_spec_helper provides a task named validate that now fails on modules containing plans. I have traced the calls this makes down and it seems that, in the end, each .pp file in a project that is not excluded manually via PuppetSyntax.exclude_paths is passed to puppet parser validate via the code below: def validate_manifest(file) Puppet[:parser] = 'future' if
Jira (PUP-7763) Fresh install uses deprecated setting
Title: Message Title Gene Liverman commented on PUP-7763 Re: Fresh install uses deprecated setting Josh Cooper the link in the real default config file does still point to a page saying to set this to true though https://docs.puppet.com/puppet/latest/config_important_settings.html#getting-new-features-early Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7763) Fresh install uses deprecated setting
Title: Message Title Gene Liverman commented on PUP-7763 Re: Fresh install uses deprecated setting Josh Cooper You are totally correct, my apologies. That is a goof in my personal packer template that I shall now fix. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7763) Fresh install uses deprecated setting
Title: Message Title Gene Liverman updated an issue Puppet / PUP-7763 Fresh install uses deprecated setting Change By: Gene Liverman Environment: CentOS 7 [root@localhost vagrant]# rpm -qa|grep puppetpuppet5-release-5.0.0-1.el7.noarchpuppet-agent-5.0.0-1.el7.x86_64 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7763) Fresh install uses deprecated setting
Title: Message Title Gene Liverman created an issue Puppet / PUP-7763 Fresh install uses deprecated setting Issue Type: Bug Assignee: Unassigned Created: 2017/07/08 11:26 PM Environment: CentOS 7 Priority: Normal Reporter: Gene Liverman Upon playing around with Puppet 5 tonight I found that a default install gives the error message below on each run: Warning: Setting trusted_server_facts is deprecated. (at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/settings.rb:1159:in `issue_deprecation_warning') The default /etc/puppetlabs/puppet/puppet.conf is below:
Jira (PUP-7750) puppet resource service fails on FreeBSD 11
Title: Message Title Gene Liverman commented on PUP-7750 Re: puppet resource service fails on FreeBSD 11 After some guidance on where to look, it seems the offending code is likely around provider/service/freebsd.rb line 47 as there is no error handling for when there is no name. I'm planning to take a stab at fixing this in the next week or so. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7750) puppet resource service fails on FreeBSD 11
Title: Message Title Gene Liverman commented on PUP-7750 Re: puppet resource service fails on FreeBSD 11 Geoff Nichols Can you point me in the direction of where in the code base to look for the code related to this? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7750) puppet resource service fails on FreeBSD 11
Title: Message Title Gene Liverman created an issue Puppet / PUP-7750 puppet resource service fails on FreeBSD 11 Issue Type: Bug Affects Versions: PUP 5.0.0, PUP 4.10.0 Assignee: Unassigned Attachments: freebsd11-bluetooth.txt, freebsd11-sshd.txt Created: 2017/07/04 10:51 AM Environment: FreeBSD 11 Priority: Normal Reporter: Gene Liverman I was playing around with FreeBSD 11 today and found that running puppet resource service failed with the error Error: Could not run: undefined method `gsub' for nil:NilClass. After doing some testing I believe it is due to Puppet not handling the results of running /etc/rc.d/bluetooth rcvar. Details and related examples below:
