Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-1264 Allow puppetdb plugin to set host and name independently Change By: Lucy Wyman Assignee: Lucy Wyman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305930.1556035083000.5839.1557875940336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4356) Migrate db code from md5 to sha256
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-4356 Migrate db code from md5 to sha256 Change By: Robert Roland Summary: Migrate db code from md5 to sha1 sha256 There is a function and an aggregate created in psql for PE that uses MD5. These must be replaced with SHA1 SHA256 variants. 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. To view this discussion on the web visit
Jira (PDB-4356) Migrate db code from md5 to sha1
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4356 Migrate db code from md5 to sha1 Change By: Robert Roland Assignee: Robert Roland 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306364.1556211204000.5564.1557870781093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4357) Enable the Bouncy Castle FIPS provider
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4357 Enable the Bouncy Castle FIPS provider Change By: Robert Roland Assignee: Robert Roland 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306365.1556211379000.5568.1557870781294%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4305) "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors
Title: Message Title Robert Roland assigned an issue to Unassigned PuppetDB / PDB-4305 "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors Change By: Robert Roland Assignee: Robert Roland 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300026.1552508578000.5549.1557870723035%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4370) Adjust storage to accommodate catalog inputs
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4370 Adjust storage to accommodate catalog inputs Change By: Rob Browning For now, by catalog input, we mean one of the following items that might influence a given catalog: - heira key: string (name) - function: string (name) - template: string (name)Though for the first pass, we may or may not need all of these.One storage option would be a new catalog_inputs table recording [certname_id type name] for each input. There may also be some details to work out regarding timestamps ([~zachary.kent] and/or [~rob.browning] have been discussing the issues).As far as lifetime goes, the inputs should be tied to the certname, not to a given catalog, and should behave like facts (expiring, etc. with the certname). 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,
Jira (PDB-4371) Add initial support for catalog input related queries
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4371 Add initial support for catalog input related queries Change By: Rob Browning At a minimum, we need some query that can return a list of certnames whose catalogs mention any one of a provided set of inputs. Where this should end up hasn't been determined yet. Inputs would may also be returned under a new optional key in the catalog response. Whether or not we'll want/need to make that field opt-in is as yet undetermined, but our versioning policy does require clients to ignore unexpected new fields, so we're not obligated to make it opt-in, nor to increment the endpoint versions , and adding it to the catalog response means we wouldn't have to adjust sync or import/export . 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
Jira (PDB-4371) Add initial support for catalog input related queries
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4371 Add initial support for catalog input related queries Change By: Rob Browning Summary: Add at least a query to report certnames possibly affected by initial support for catalog input list related queries 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308642.155786921.5517.1557869520771%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4371) Add at least a query to report certnames possibly affected by input list
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4371 Add at least a query to report certnames possibly affected by input list Change By: Rob Browning At a minimum, some query that can return a list of certnames whose catalogs mention any one of a provided set of inputs. Inputs would be returned under a new optional key in the catalog response. Whether or not we'll want/need to make that field opt-in is as yet undetermined, but our versioning policy does require clients to ignore unexpected new fields, so we're not obligated to make it opt-in, nor to increment the endpoint versions. 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
Jira (PDB-4371) Add at least a query to report certnames possibly affected by input list
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4371 Add at least a query to report certnames possibly affected by input list Issue Type: New Feature Assignee: Unassigned Created: 2019/05/14 2:26 PM Priority: Normal Reporter: Rob Browning At a minimum, some query that can return a list of certnames whose catalogs mention any one of a provided set of inputs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4372) Store catalog inputs when they are (optionally) received by submit catalog
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4372 Store catalog inputs when they are (optionally) received by submit catalog Issue Type: New Feature Assignee: Unassigned Created: 2019/05/14 2:30 PM Priority: Normal Reporter: Rob Browning Store catalog inputs when they are sent via a new optional key in the catalog wire-format. Assuming it's feasible, this approach has the advantage that it makes updates transactional, and avoids having to augment import/export/sync to handle a new command (assuming a new command might even be appropriate). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4370) Adjust storage to accommodate catalog inputs
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4370 Adjust storage to accommodate catalog inputs Issue Type: New Feature Assignee: Unassigned Created: 2019/05/14 2:24 PM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-4369) Store "inputs" for catalogs and add query for certnames that might be affected by an input
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4369 Store "inputs" for catalogs and add query for certnames that might be affected by an input Issue Type: Epic Assignee: Unassigned Created: 2019/05/14 2:15 PM Priority: Normal Reporter: Rob Browning Initial notes: Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1269) Prompt for sensitive data from inventory.
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1269 Prompt for sensitive data from inventory. Change By: Cas Donoghue Assignee: Cas Donoghue 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306225.1556137227000.5316.1557867540646%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1185) plan examples
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1185 plan examples Change By: Lucy Wyman Labels: DOCS 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300539.1552676543000.5359.1557867963120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9495) Implement `print` method for `server_list_settings`
Title: Message Title Kris Bosland commented on PUP-9495 Re: Implement `print` method for `server_list_settings` Merged into 5.5.x at 7721e5c. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295966.1550015035000.5295.1557867300955%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1303) Provide a Bolt Docker Image
Title: Message Title Brian Maher created an issue Puppet Task Runner / BOLT-1303 Provide a Bolt Docker Image Issue Type: Task Assignee: Unassigned Created: 2019/05/14 1:36 PM Priority: Normal Reporter: Brian Maher Some bolt tasks operate on "cloud resources". For example, this article describes how to use bolt to spin up a Kubernetes cluster on EKS: https://puppet.com/blog/deploying-kubernetes-amazon-eks-bolt The ability to run bolt within a container would open the door for more usage of `bolt` in the context of "cloud native". Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1185) plan examples
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1185 plan examples Change By: Cas Donoghue Assignee: Cas Donoghue 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300539.1552676543000.5218.1557863160396%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8088) add mechanism for cache eviction callback / finalizers
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-8088 add mechanism for cache eviction callback / finalizers Change By: Henrik Lindberg Assignee: Henrik Lindberg 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.218549.150892772.4774.1557855600098%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH
Title: Message Title Thomas Kishel commented on PUP-6488 Re: Gem provider should allow alternative gem command; should not rely on $PATH Release note ready for review. Thanks for your help with this! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.140954.1468271833000.4760.1557855300492%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH
Title: Message Title
Thomas Kishel updated an issue
Puppet / PUP-6488
Gem provider should allow alternative gem command; should not rely on $PATH
Change By:
Thomas Kishel
Release Notes Summary:
Package providers now support a targeted package management commandPuppet package providers use `which` to find the first package management command (for example: `gem` for Ruby, `pip` for Python) in the `PATH`. That prevented Puppet from managing other installations of the same software.This release adds a `targetable` feature to the Package type, allowing Package providers to implement a `command` attribute. The gem and pip providers now implement that attribute.```package { 'colorize': name => 'colorize', provider => gem,}package { 'colorize-opt': name => 'colorize', provider => gem, command => '/opt/ruby/bin/gem',}```This feature allows Puppet to manages the packages in software collections (multiple versions of the same software) such as Red Hat Software Collections.PUP-1082, PUP-6488
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs
Title: Message Title Josh Cooper commented on PUP-8736 Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs As long as a recursive rm -rf /opt/puppetlabs/puppet/cache doesn't follow the symlink (and I don't think it will), then using a symlink could work. We could release that change before 7 if we create a new puppet setting pointing to the new location, in lieu of the existing devicedir, and update puppet device to create the symlink automatically. Then in puppet 7 delete the old devicedir setting and symlink logic. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251027.1526491177000.4752.1557855120476%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1270) Bolt should have an encrypted data store
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1270
Bolt should have an encrypted data store
Change By:
Alex Dreyer
Questions:- How do you interact with this feature within Bolt should support eyaml data in the inventory ? file. - Should you Users should be able to have a single file with encrypted embed bolt eyaml data in it that can be used by multiple users, or is it on a per user basis? Do you need the inventory file similar to be able to share how the data with multiple people? * prompt plugin works. The easiest solution seems like encrypted data plugin should be on called eyaml, It should have a per user basis.* single key "encrypted-value" that {noformat}nodes: - Does uri: my_node config: winrm: password: _plugin: eyaml encrypted-value: > ENC[PKCS7,Y22exl+OvjDe+drmik2XEeD3VQtl1uZJXFFF2NnrMXDWx0csyqLB/2NOWefv NBTZfOlPvMlAesyr4bUY4I5XeVbVk38XKxeriH69EFAD4CahIZlC8lkE/uDh jJGQfh052eonkungHIcuGKY/5sEbbZl/qufjAtp/ufor15VBJtsXt17tXP4y l5ZP119Fwq8xiREGOL0lVvFYJz2hZc1ppPCNG5lwuLnTekXN/OazNYpf4CMd /HjZFXwcXRtTlzewJLc+/gox2IfByQRhsI/AgogRfYQKocZgFb/DOZoXR7wm IZGeunzwhqfmEtGiqpvJJQ5wVRdzJVpTnANBA5qxeA==]{noformat}Users should configure the sensitive data live eyaml plugin in bolt yaml under the inventory or in an external file? {{plugins:eyaml}} section. relative paths to keys should be relative to the {{Boltdir}}. TODO {noformat}---ssh : host - Look at Ansible Vault key - check: falseplugins: eyaml: pkcs7_private_key: keys/private_key.pkcs7.pem pkcs7_public_key: keys/public_key.pkcs7.pem{noformat}Questions:- What should the {{encrypted-value}} key be called?- Can bolt expose the "eyaml" command directly or do we need {{bolt eyaml encrypt}} and {{bolt eyaml create-keys}} the latter seems out of scope unless documenting how does that work to use eyaml proves difficult ? Can we put eyaml in {{/opt/puppetlabs/bin/eyaml}} or does it need to be {{/opt/puppetlabs/bolt/bin/eyaml}}. - Should we leverage the hiera-eyaml's gem plugins or just support pkcs7. If we're not going to leverage eyaml plugins we should probably just call this the pkcs7 plugin. Out of scope:- Connect to third party encrypted data stores, ie. Vault . These should be separate plugins.
Jira (BOLT-1297) Bolt should raise a nice error if the private key file doesn't exist
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1297 Bolt should raise a nice error if the private key file doesn't exist Change By: Alex Dreyer If the private key file doesn't exist then we just get a permission denied error from ssh. Instead we should raise an error that the file doesn't exist and it's bolts configuration , since it's probably a typo in the key file name. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307991.1557409042000.4653.1557853440472%40Atlassian.JIRA. For more options, visit
Jira (BOLT-1297) Bolt should raise a nice error if the private key file doesn't exist
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1297 Bolt should raise a nice error if the private key file doesn't exist Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307991.1557409042000.4620.1557853201712%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs
Title: Message Title Thomas Kishel commented on PUP-8736 Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs Could we move/replace: /opt/puppetlabs/puppet/cache/devices/DEVICE/ssl with a symlink to: /etc/puppetlabs/puppet/devices/ssl/DEVICE ? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251027.1526491177000.4614.1557853145059%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently
Title: Message Title
Nick Lewis updated an issue
Puppet Task Runner / BOLT-1264
Allow puppetdb plugin to set host and name independently
Change By:
Nick Lewis
The puppetdb plugin will only accept a query that returns a certname and then set that certname to be the targets {{uri}}. For some users the node is not accessible through the certname so they need to lookup an IP address and set the name and certname of the target separately. The plugin will take a {{config}} section where each map value is the name of a fact to lookup from PuppetDB. The plugin will gather the list of certnames from the {{query}} field as well as all the facts that are used in the {{config}} mapping and automatically make a second query to retrieve all of the necessary fact values.If a fact isn't set for a node, the config setting for that fact should not be set.
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"
Jira (BOLT-1117) Powershell task helper library
Title: Message Title William Hurt commented on BOLT-1117 Re: Powershell task helper library I'm hoping to take over work on https://tickets.puppetlabs.com/browse/PDK-603 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295235.1549498793000.4487.1557852420603%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1264 Allow puppetdb plugin to set host and name independently Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305930.1556035083000.4492.1557852420812%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs
Title: Message Title David Mallon commented on PUP-8736 Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs well puppet device will still live on as the open source option for user to manage network devices 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251027.1526491177000.4467.1557852181072%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1222) Support an "apply" step.
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1222 Support an "apply" step. Change By: David Kramer Sprint: Bolt Ready for Grooming 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302484.1554141988000.4452.1557852060543%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs
Title: Message Title Geoff Nichols commented on PUP-8736 Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs If these two comments are correct, I'm wondering if there will need to be a different solution for the backup/restore use case? > File path changes are usually breaking, so this would need to wait until Puppet 7 > None of this will be relevant in the next PE, as the new integration will run devices in a completely different context. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251027.1526491177000.4436.1557851700426%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Trevor Vaughan commented on PUP-1298 Re: manage_membership for unix groups provider The gpasswd module still works and Puppet, Inc is welcome to pick up the code as it's Apache licensed. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.22682.1388437397000.4319.1557847200923%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Patrick Grant commented on PUP-1298 Re: manage_membership for unix groups provider Adding on behalf of behalf of customer: "Fundamentally, the request is to implement 'manages_members' in the 'groupadd' group provider. Based on the description from the 'groups' resource, this should be available, but this is not the case. While 'groupadd' group membership is defined in the group record, it is managed via the user resource. 1) May not be managed by puppet, such as a. Root, sys, or other OS-created users b. RPM-created users, such as the apache user c. Users federated by such features as ldap, sssd, or other centralized authentication 2) May not exist (yet) This is a level of configuration flexibility that is allowed by the underlying OS configuration, but cannot be expressed in Puppet." 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.22682.1388437397000.4185.1557845400464%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9697 Solaris Crontabs -> puppet resource cron only returns root account Change By: Mihai Buzgau Team: Platform OS Puppet Romania 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.4128.1557842280821%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1921) Facter java class incorrectly using "FACTERDIR" environment variable
Title: Message Title Mihai Buzgau commented on FACT-1921 Re: Facter java class incorrectly using "FACTERDIR" environment variable Hi Thomas Montague looks like the PR for this ticket: https://github.com/puppetlabs/facter/pull/1785 got merged. Can this ticket be closed? Thank you for your contribution! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307655.1557260973000.4123.1557842220127%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1920) Facter 3.12 binary gem
Title: Message Title Mihai Buzgau commented on FACT-1920 Re: Facter 3.12 binary gem Hi Matthias Baur, We will not be providing binary gems for facter 3.x. We apologize for the inconvenience. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307434.1557141764000.4113.1557842100201%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1919) blank/negative facter cache due to timed out EC2 metadata
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1919 blank/negative facter cache due to timed out EC2 metadata Change By: Mihai Buzgau Team: Puppet Romania 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307267.1556898834000.4106.1557841920862%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1919) blank/negative facter cache due to timed out EC2 metadata
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1919 blank/negative facter cache due to timed out EC2 metadata Change By: Mihai Buzgau Sprint: PR - Triage 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307267.1556898834000.4086.1557841080223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1916) facter fails to parse routing table
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1916 facter fails to parse routing table Change By: Mihai Buzgau Sprint: PR - Triage 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307043.155680303.4080.1557840961018%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1916) facter fails to parse routing table
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1916 facter fails to parse routing table Change By: Mihai Buzgau Team: Puppet Romania 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307043.155680303.4078.1557840960987%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9702) Improvements for facter
Title: Message Title Mihai Buzgau created an issue Puppet / PUP-9702 Improvements for facter Issue Type: Epic Assignee: Unassigned Created: 2019/05/14 6:04 AM Priority: Normal Reporter: Mihai Buzgau 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
Jira (PUP-9564) Puppet upgrades debian packages with pending updates when setting them on hold
Title: Message Title
Alexandru Popa updated an issue
Puppet / PUP-9564
Puppet upgrades debian packages with pending updates when setting them on hold
For Debian os. Issue: when defining the state of a package in a manifest with:
package {'openssl': ensure => held }
and the package is all ready installed on the system the first thing it does is to update the package to latest version instead of locking the package to a specific version. Fix: If the package is all ready installed on the system the package remains locked to the specific version. If the package is not installed on the system, it installs the latest package and locks it to that version.
Change By:
Alexandru Popa
Release Notes Summary:
Fixed bug for Debian distribution in which the ensure => held would install latest version of the package before locking it to the specific version.
Add Comment
Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH
Title: Message Title Sebastian Miclea commented on PUP-6488 Re: Gem provider should allow alternative gem command; should not rely on $PATH Thomas Kishel Could you please add documentation to this ticket so it can be closed? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.140954.1468271833000.3984.1557836100398%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9701) Gem provider uses --no-rdoc
Title: Message Title Vivek S created an issue Puppet / PUP-9701 Gem provider uses --no-rdoc Issue Type: Bug Assignee: Unassigned Components: Types and Providers Created: 2019/05/14 3:32 AM Priority: Normal Reporter: Vivek S Puppet Version: 4.7.0 Puppet Server Version: OS Name/Version: Ubuntu trusty Installed ruby 2.6 and trying to install ruby gems. gem provider always executes with flag --no-rdoc which is not supported in latest ruby gem. [23.253.241.250] out: Debug: Executing '/usr/bin/gem install -v 6.4.2 --no-rdoc --no-ri puppet' [23.253.241.250] out: Error: Could not update: Execution of '/usr/bin/gem install -v 6.4.2 --no-rdoc --no-ri puppet' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption) [23.253.241.250] out: invalid option: --no-rdoc Desired Behavior: Gem should be installed without throwing invalid option error Actual Behavior: Throws the following error: [23.253.241.250] out: Debug: Executing '/usr/bin/gem install -v 6.4.2 --no-rdoc --no-ri puppet' [23.253.241.250] out: Error: Could not update: Execution of '/usr/bin/gem install -v 6.4.2 --no-rdoc --no-ri puppet' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption) [23.253.241.250] out: invalid option: --no-rdoc
Jira (PUP-4930) Provide helpful error message when provider does not have instances defined
Title: Message Title David Schmitt assigned an issue to Rob Braden A really simple change. I've put up https://github.com/puppetlabs/puppet/pull/7522 to address this. Assigning to Rob Braden for hand-holding through the process. Puppet / PUP-4930 Provide helpful error message when provider does not have instances defined Change By: David Schmitt Assignee: Rob Braden Release Notes Summary: Improved a developer error on `provider.instances`. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1301) multi-threaded/parallel execution of plans within a plan
Title: Message Title Nathan Giuliani commented on BOLT-1301 Re: multi-threaded/parallel execution of plans within a plan Yes, what you've described is how I see it. Using the example above with a plan module::patch_and_reboot, I'd expect to be able to call it from another plan as follows: pan module:patch_lots_of_servers is run on 10 nodes, which does the following: Perform some global pre-patching steps like taking vm snapshots, and emailing users that patching is starting run_plan module::patch_and_reboot on all 10 nodes i'd like puppet to run 10 parallel processes here, each executing the plan on an individual node each node will work through the steps in that plan independently, but execution of this 'top-level' plan won't continue until all 10 parallel processes have been completed Perform some global post-patching steps like removing vm snapshots, and emailing users that patching has finished I did try searching for an existing issue here and didn't come across BOLT-176, but I believe that it is a very similar request, it's just that this one relates to execution of a plan, not a task (which already happens in parallel across nodes based on the concurrency parameter). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
