Jira (FACT-2138) Facts passed via environment variables not parsed as array
Title: Message Title
Kim Ausloos created an issue
Facter / FACT-2138
Facts passed via environment variables not parsed as array
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/11/26 1:25 AM
Environment:
Vagrantbox, centos 8, compiled facter manually from master: 3.14.7 (commit 479bea29b8445e1b1fe240385905a0b50e8256d4)
Priority:
Normal
Reporter:
Kim Ausloos
I'm trying to get facter accept array values as environment variables but it's not picking them up. I compiled facter based on master: 3.14.7 (commit 479bea29b8445e1b1fe240385905a0b50e8256d4) The issue actually manifested itself when using the puppet provisioner from vagrant, while passing an array to the facts hash. It's passing values as environment variables by default and we noticed this appears to be not working. Tested: FACTER_zzcustomerappl="['bla1', 'bla2', 'bla3']" facter -j zzcustomerappl {{{}} {{ "zzcustomerappl": "['bla1', 'bla2', 'bla3']"}} }FACTER_zzcustomerappl='["bla1","bla2","bla3"]' facter -j zzcustomerappl {{{}} {{ "zzcustomerappl": "[\"bla1\",\"bla2\",\"bla3\"]"}} }FACTER_zzcustomerappl="bla1\nbla2\nbla3" facter -j zzcustomerappl {{{}} {{ "zzcustomerappl": "bla1\\nbla2nbla3"}} }
Add Comment
Jira (FACT-2138) Facts passed via environment variables not parsed as array
Title: Message Title
Kim Ausloos updated an issue
Facter / FACT-2138
Facts passed via environment variables not parsed as array
Change By:
Kim Ausloos
I'm trying to get facter accept array values as environment variables but it's not picking them up. I compiled facter based on master:3.14.7 (commit 479bea29b8445e1b1fe240385905a0b50e8256d4)The issue actually manifested itself when using the puppet provisioner from vagrant, while passing an array to the facts hash. It's passing values as environment variables by default and we noticed this appears to be not working. Tested: {{ FACTER_zzcustomerappl="['bla1', 'bla2', 'bla3']" facter -j zzcustomerappl }} { {{}} {{ "zzcustomerappl": "['bla1', 'bla2', 'bla3']" }} {{ } }}{{FACTER_zzcustomerappl='["bla1","bla2","bla3"]' facter -j zzcustomerappl}} {{{}} {{ "zzcustomerappl": "[\"bla1\",\"bla2\",\"bla3\"]"}}{{}}}{{ FACTER_zzcustomerappl="bla1\nbla2\nbla3" facter -j zzcustomerappl }} { {{}} {{ "zzcustomerappl": "bla1\\nbla2\\nbla3" }} {{ } }}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Adam Buxton commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run Charlie Sharpsteen add it to the quiver of useful `PS made this` https://forge.puppet.com/laura/puppet_agent_settings 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.117656.1455921098000.45679.157470881%40Atlassian.JIRA.
Jira (PDB-4587) docs: clarify connect Puppet master page
Title: Message Title Matthew Lowy commented on PDB-4587 Re: docs: clarify connect Puppet master page May no longer be relevant as puppetdb-termini is now in the Puppetlabs repo for Debian Buster. 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.334513.1573567979000.45720.1574767620138%40Atlassian.JIRA.
Jira (FACT-2139) Implement --list-block-groups
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2139 Implement --list-block-groups Change By: Sebastian Miclea Assignee: Sebastian Miclea 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.336685.1574772324000.45776.1574772360250%40Atlassian.JIRA.
Jira (FACT-2139) Implement --list-block-groups
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2139 Implement --list-block-groups Issue Type: Task Assignee: Unassigned Created: 2019/11/26 4:45 AM Priority: Normal Reporter: Sebastian Miclea 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.336685.1574772324000
Jira (FACT-2139) Implement --list-block-groups
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2139 Implement --list-block-groups Change By: Sebastian Miclea facter --list-block-groupsExample output:EC2 - ec2_metadata - ec2_userdatafile system - mountpoints - filesystems - partitionshypervisors - hypervisors 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.336685.1574772324000.45777.1574772421579%40Atlassian.JIRA.
Jira (FACT-2139) Implement --list-block-groups
Title: Message Title
Sebastian Miclea updated an issue
Facter / FACT-2139
Implement --list-block-groups
Change By:
Sebastian Miclea
facter --list-block-groupsExample output: {code:ruby} EC2 - ec2_metadata - ec2_userdatafile system - mountpoints - filesystems - partitionshypervisors - hypervisors {code}
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.336685.1574772324000.45778.1574773140085%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Austin Blatt This is a bug in PE pe-puppetdb 's HA sync.On the local PuppetDB, when a node is purged after a deactivate node command and then a garbage collection run after node-purge-ttl time has passed, the node is deleted.The remote PuppetDB also has that deactivated node present, but has not run garbage collection, when the local PuppetDB (that has just garbage collection the node) attempts to sync from the remote it will sync back the node it just garbage collected.This will result in a ping-pong effect and the node will never be purged from PuppetDB 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
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4479 Deactivate node commands sync after garbage collection Change By: Austin Blatt Acceptance Criteria: Nodes that are garbage collected on one PuppetDB are * Does not re sync node deactivation commands that have a deactivated timestamp older than node - synced from the remote purge-ttl* Does not sync node data (agentless nodes 6 . 3.x+) that have a deactivated/expired timestamp older than node-purge-ttl 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.320599.1565648011000.46352.1574796480438%40Atlassian.JIRA.
Jira (PDB-4479) Deactivate node commands sync after garbage collection
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4479
Deactivate node commands sync after garbage collection
Change By:
Austin Blatt
This is a bug in pe-puppetdb's HA sync because we only check the value of {{producer_timestamp}} and not the timestamps named {{deactivate}} and {{expired}} in the {{certnames}} table in the {{would_be_expired_locally?}} function of {{ . ../sync/core.clj}} On the local PuppetDB, when a node is purged after a deactivate node command and then a garbage collection run after node-purge-ttl time has passed, the node is deleted.The remote PuppetDB also has that deactivated node present, but has not run garbage collection, when the local PuppetDB (that has just garbage collection the node) attempts to sync from the remote it will sync back the node it just garbage collected.This will result in a ping-pong effect and the node will never be purged from PuppetDB
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message beca
