Jira (FACT-1573) Verify, reconcile, and correct Windows OS version facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1573 Verify, reconcile, and correct Windows OS version facts Change By: Geoff Nichols Fix Version/s: FACT 4.0.0 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 (FACT-1573) Verify, reconcile, and correct Windows OS version facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1573 Verify, reconcile, and correct Windows OS version facts Change By: Geoff Nichols Sprint: Agent Grooming On-Deck 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-1526) Package type should support environment variables
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1526 Package type should support environment variables Change By: Geoff Nichols Sprint: Agent Grooming 5 Ready for Engineering 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-1526) Package type should support environment variables
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1526 Package type should support environment variables Change By: Geoff Nichols Sprint: Agent Grooming 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-7266) SPIKE: Master and Agent should not share a libdir
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7266 SPIKE: Master and Agent should not share a libdir Change By: Geoff Nichols Sprint: Agent Grooming On-Deck 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-7265) Remove file face
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7265 Remove file face Change By: Geoff Nichols Sprint: Agent Accepted Grooming 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-7331) "Unable to set ownership" error with logdest on agents
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7331 "Unable to set ownership" error with logdest on agents Change By: Geoff Nichols Sprint: Client 2016-09-07, Agent Grooming On-Deck 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-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Geoff Nichols Sprint: Agent Grooming On-Deck 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-5068) Windows - Allow logging to a different event log
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5068 Windows - Allow logging to a different event log Change By: Geoff Nichols Story Points: 2 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-6060) Change node_cache_terminus default to nil
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6060 Change node_cache_terminus default to nil Change By: Geoff Nichols Sprint: Agent 2017-04-05 5 Ready for Engineering 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 (FACT-777) Facter should not downcase fact names
Title: Message Title Geoff Nichols updated an issue Facter / FACT-777 Facter should not downcase fact names Change By: Geoff Nichols Sprint: Agent 5 Ready for Engineering 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-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' command Change By: Geoff Nichols Sprint: Agent 5 Ready for Engineering 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-7157) Remove 'semantic' shim in Puppet 5
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7157 Remove 'semantic' shim in Puppet 5 Change By: Geoff Nichols Sprint: Agent 5 Ready for Engineering 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-7134) Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7134 Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files Change By: Geoff Nichols Sprint: Agent 5 Ready for Engineering 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-6040) "puppet facts" outputs indirector object instead of simple fact list
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6040 "puppet facts" outputs indirector object instead of simple fact list Change By: Geoff Nichols Sprint: Agent 5 Ready for Engineering 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-7073) Comparisons between SELinux file categories should always translate to the numeric version
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7073 Comparisons between SELinux file categories should always translate to the numeric version Change By: Geoff Nichols Sprint: AP 2017-01-25, AP 2017-02-08, Agent 5 Ready for Engineering 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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6432 Puppet::Util::Execution.execute cannot handle Unicode output on Windows Change By: Geoff Nichols Sprint: Agent 5 Ready for Engineering 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-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Geoff Nichols Sprint: Agent 5 Ready for Engineering 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 (FACT-858) Fact ec2_user_data attempting to use proxy information when it shouldn't
Title: Message Title Branan Riley commented on FACT-858 Re: Fact ec2_user_data attempting to use proxy information when it shouldn't It looks like we don't properly clear the proxy variables from the environment in Facter 3, so this might actually still be applicable (though the code is very different now) 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 (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Jeremy Adams commented on PDOC-161 Re: As a developer I want to programmatically retrieve the name and short description from a puppet class +1 to a tag called summary that will appear at least in the context of puppet classes, though I wouldn't be opposed to it showing up in the other types as well: "puppet_classes": [ ], "defined_types": [ ], "resource_types": [ ], "providers": [ ], "puppet_functions": [ ] }
Jira (PUP-7350) Update minitar to 0.6.1
Title: Message Title Ethan Brown commented on PUP-7350 Re: Update minitar to 0.6.1 Related, we need a ticket for Puppet 5/6 to use Minitar gem everywhere, marking it as a dependency for all platforms in project_data.yaml 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-7350) Update minitar to 0.6.1
Title: Message Title Ethan Brown commented on PUP-7350 Re: Update minitar to 0.6.1 Did anyone verify the API changes from previous 0.5.z to 0.6.1? 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title Henrik Lindberg commented on PUP-7351 Re: PUP 4.9.4 `deep merge` hiera interpolation still doesn't work Alex P Well, this is disappointing We do want to help you sort this out, and if there are problems in the implementation we do want to get those fixed. From the conversation in PUP-7289 (towards the end) however, we could not reproduce your case (Several engineers and QA folks tried on our side). Without a reproducer it is really hard for us to figure out what is wrong. Is there some way we can get access to your configuration? Can you hit me up in IRC or Slack on a private channel so we can figure out how to best help you? I am 'helindbe' there. 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7351
PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Change By:
Henrik Lindberg
Coming back to my [comment|https://tickets.puppetlabs.com/browse/PUP-7289?focusedCommentId=415955=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-415955] in PUP-7289, `deep merge` option does NOT work at all. As soon as we switch to that one then:- agent would run and "apply" catalog very quickly, e.g. {{Notice: Applied catalog in 0.40 seconds}}, where a _normal_ run would be 1-2 seconds;- whatever changes would be made in {{nodes/vm01.yaml}} or any other file in hierarchy, it'll be ignored.{{unique}} and {{hash}} options are not useful and there is another bug( \ ?) that makes them non-working either.Please advise what additional information do you need. The whole environment and settings as per PUP-7289.
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-7226) Remove vendored Rgen gem
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7226 Remove vendored Rgen gem Change By: Henrik Lindberg Release Notes Summary: The earlier vendored (included) RGen meta-modeling gem has been removed from puppet. If you required RGen in experimental code and counted on puppet to install it, you must now install it yourself. If you relied on non Puppet API methods brought in by RGen monkeypatching you must revise your code. (This should not affect any normal user code in Ruby or Puppet).The RGen gem was used in puppet for the Puppet AST and for the injector/binder system. The injector/binder subsystem has been replaced in Puppet 5.0.0, and the AST is now using Puppet Pcore, a faster implementation for meta models built on the Puppet's type system.All users should see some reduction in memory use and a faster startup time for a puppet compilation as the result of this removal. Release Notes: Deprecation 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
Jira (PUP-7283) Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization
Title: Message Title Moses Mendoza commented on PUP-7283 Re: Instantiating Puppet::SSL::DefaultValidator shouldn't trigger client SSL initialization merged to master at https://github.com/puppetlabs/puppet/commit/1f8c92ee51a28331ca52dd5e7ef319643fa1ad63 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 (PDB-3353) Prototype perf regression testing harness
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3353 Prototype perf regression testing harness Change By: Russell Mull Sprint: Son of Hopper SE 2017-03-22 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 (PDB-3353) Prototype perf regression testing harness
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-3353 Prototype perf regression testing harness Change By: Russell Mull Assignee: Russell Mull 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 (PDB-3353) Prototype perf regression testing harness
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3353 Prototype perf regression testing harness Change By: Russell Mull Story Points: 2 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 (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: Lindsey Smith *Use Case:* Vendors like VMware would like a way to discover a list of role classes along with a description of the class. Right now they can pull a class name, but there isn't a standard way to retrieve a short description. puppet-strings is used to document puppet files, but it's also a great way to get easily parseable metadata about a puppet file via the JSON output option(s).*The Issue:* You can get the name from puppet-strings, but puppet-strings (and YARD itself) doesn't have a simple tag for a short description. There is the generic docstring text, but it's freeform and can be multiple lines. It's not ideal.*Solution:* Create a new puppet-strings-specific YARD "summary" tag (similar to puppet.type.param) for storing a short description with a recommended limit of 140 characters. This field should show up in the JSON output. 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-7225) Remove the Puppet Binder
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7225 Remove the Puppet Binder Change By: Henrik Lindberg Release Notes Summary: The experimental internal binder/injector system used to configure "plugins" for hiera 4 and additional syntax checkers for heredoc content has been removed and replaced by a much simpler mechanism. This should not affect anyone except those that where experimenting with this implementation. For everyone else, this reduces some of the time required to start a compilation. Release Notes: Deprecation 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 (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: William Hopper Story Points: 2 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-7224) Replace the Rgen AST model with one generated from a Pcore model
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7224 Replace the Rgen AST model with one generated from a Pcore model Change By: Henrik Lindberg Assignee: 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-7243) acceptance: utf8-in-function-args test environment not found
Title: Message Title Sean Griffin commented on PUP-7243 Re: acceptance: utf8-in-function-args test environment not found Geoff Nichols I checked, the fixed version has been merged and is running and passing in both the stable and master pipelines. Closing. -Sean 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 (PDB-3356) Use anti-join when eliminating inactive nodes from queries
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3356 Use anti-join when eliminating inactive nodes from queries Change By: Russell Mull Story Points: 2 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 (PDB-3356) Use anti-join when eliminating inactive nodes from queries
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3356 Use anti-join when eliminating inactive nodes from queries Issue Type: Improvement Assignee: Unassigned Created: 2017/03/14 3:44 PM Priority: Normal Reporter: Russell Mull We currently use a join against the certnames table with inactive nodes filtered out in order to remove inactive nodes from most queries. Because there are usually very few inactive nodes, it should nearly always be faster to do an antijoin against the inactive nodes instead. This is needed for the package inventory work because it takes one of the queries from being very, very slow to being pretty darn fast. Add Comment This message was
Jira (PDB-3356) Use anti-join when eliminating inactive nodes from queries
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3356 Use anti-join when eliminating inactive nodes from queries Change By: Russell Mull Sprint: Son of Hopper 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 (PDB-3355) Fix :unable-to-commit clause in store-in-stockpile
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3355 Fix :unable-to-commit clause in store-in-stockpile Issue Type: Bug Assignee: Unassigned Created: 2017/03/14 3:27 PM Labels: maintenance Priority: Normal Reporter: Rob Browning Should be ::stock/unable-to-commit. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3354) Stop hashing the json representation for string fact values
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3354 Stop hashing the json representation for string fact values Issue Type: Improvement Assignee: Unassigned Created: 2017/03/14 3:23 PM Labels: maintenance Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this
Jira (PDB-3306) Remove the vestigial clojure version of the PuppetDB CLI
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3306 Remove the vestigial clojure version of the PuppetDB CLI Change By: Russell Mull Sprint: Son of Hopper 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 (PDB-3310) [module PR] Fix duplicate resource errors for puppet service due to parse order
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3310 [module PR] Fix duplicate resource errors for puppet service due to parse order Change By: Russell Mull Sprint: Son of Hopper 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 (PDB-3353) Prototype perf regression testing harness
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3353 Prototype perf regression testing harness Change By: Russell Mull Sprint: Son of Hopper 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 (PDB-3353) Prototype perf regression testing harness
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3353 Prototype perf regression testing harness Issue Type: New Feature Assignee: Unassigned Created: 2017/03/14 3:09 PM Priority: Normal Reporter: Russell Mull 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
Jira (PDB-3325) Audit acceptance / integration tests for coverage gaps
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3325 Audit acceptance / integration tests for coverage gaps Change By: Russell Mull Sprint: Son of Hopper 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 (FACT-747) Improve Solaris $::ipaddress accuracy
Title: Message Title Branan Riley commented on FACT-747 Re: Improve Solaris $::ipaddress accuracy In Facter 3, we updated the Linux networking code to check the routing table and attempt to use whatever interface is the "default" route for the ipaddress fact. We should likely do the same for other platforms, including Solaris. 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 (PDB-3331) HA Replication of package inventory
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3331 HA Replication of package inventory Change By: Russell Mull Story Points: 2 3 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 (FACT-657) Solaris manufacture details should use prtpicl instead of prtdiags/sneep
Title: Message Title Branan Riley commented on FACT-657 Re: Solaris manufacture details should use prtpicl instead of prtdiags/sneep We appear to still be using prtdiag in Facter 3. I'm going to leave this open for now 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 (PDB-3331) HA Replication of package inventory
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3331 HA Replication of package inventory Change By: Russell Mull Sprint: Son of Hopper 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 (PDB-3332) Implement querying support for package inventory
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3332 Implement querying support for package inventory Change By: Russell Mull Sprint: Son of Hopper 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 (PDB-3283) Test coverage for conflicts during initial sync
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3283 Test coverage for conflicts during initial sync Change By: Russell Mull Sprint: Son of Hopper 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 (PDB-3283) Test coverage for conflicts during initial sync
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3283 Test coverage for conflicts during initial sync Change By: Russell Mull Sprint: Son of Hopper 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 (PDB-3283) Test coverage for conflicts during initial sync
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3283 Test coverage for conflicts during initial sync Change By: Russell Mull Sprint: Hopper 2 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-7134) Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7134 Convert Ruby ::File calls for open to Puppet::FileSystem and explicitly specify encoding for SSL files Change By: Geoff Nichols Sprint: Agent Grooming Ready for Engineering 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-7243) acceptance: utf8-in-function-args test environment not found
Title: Message Title Geoff Nichols commented on PUP-7243 Re: acceptance: utf8-in-function-args test environment not found Sean Griffin, does this still need review? 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 (FACT-701) Alias and vlan interface name collision
Title: Message Title Branan Riley commented on FACT-701 Re: Alias and vlan interface name collision Structured networking facts should handle most of this problem, although I'm not sure we properly report devices that are aliases or vlans. 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 (FACT-687) Xen virtual fact doesn't work on CentOS 6.5
Title: Message Title Branan Riley updated an issue Facter / FACT-687 Xen virtual fact doesn't work on CentOS 6.5 Change By: Branan Riley Labels: virtualization 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 (FACT-687) Xen virtual fact doesn't work on CentOS 6.5
Title: Message Title Branan Riley commented on FACT-687 Re: Xen virtual fact doesn't work on CentOS 6.5 This is possibly a virt-what bug, as we rely on virt-what for much of our virtualization detection. Can you confirm if this is still an issue in Facter 3? 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 (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: Lindsey Smith *Use Case:* Vendors like VMware would like a way to discover a list of role classes along with a description of the class. Right now they can pull a class name, but there isn't a standard way to retrieve a short description. puppet-strings is used to document puppet files, but it's also a great way to get easily parseable metadata about a puppet file via the JSON output option(s).*The Issue:* You can get the name from puppet-strings, but puppet-strings (and YARD itself) doesn't have a simple tag for a short description. There is the generic docstring text, but it's freeform and can be multiple lines. It's not ideal.* Proposed Solution:* Create a new puppet-strings-specific YARD tag (similar to puppet.type.param) for storing a short description with a recommended limit of 50-80 140 characters. This field should show up in the JSON output. Optionally the field can show up in the HTML. 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
Jira (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Lindsey Smith commented on PDOC-161 Re: As a developer I want to programmatically retrieve the name and short description from a puppet class I chatted with David Schmitt and we decided that we do want a standard tag built-in so that multiple solutions can take advantage of the class short name. The burden of coping with the constraints of the tag will be on the consuming solution (VRA, Foreman, PE GUI eventually, etc.). For our part we'd want to evangelize its existence so that consuming solutions have content to take advantage of. 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 (FACT-616) operatingsystemrelease incorrectly set on CentOS 7
Title: Message Title Branan Riley commented on FACT-616 Re: operatingsystemrelease incorrectly set on CentOS 7 Per the comment above, this is what operatingsystemmajrelease (and all the structured facts around OS data) are for. 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 (FACT-572) add $::isPuppetMaster fact that supports cluster of Puppet Masters
Title: Message Title Branan Riley commented on FACT-572 Re: add $::isPuppetMaster fact that supports cluster of Puppet Masters This seems impossible to detect correctly and consistently. Specific running processes or services aren't necessarily accurate measures of whether something is a puppet master. This is something that is better handled by a custom fact specific to your infrastructure, or maybe even an external fact that only gets laid down on your Puppetmasters. 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 (FACT-1590) facter built with vanagon on F25 for AArch64 has double free bug
Title: Message Title Branan Riley commented on FACT-1590 Re: facter built with vanagon on F25 for AArch64 has double free bug I'm going to guess that this is an issue with static linking causing some destructors to be run more than once. We've had issues with the way we link boost before, and it is not surprising that a port to a new architecture shook some more bugs out. Off the top of my head, I'm not sure how much work it would be to change pl-build-tools and puppet-agent to try to link Boost dynamically. It's something we'd want to do across the board if we're going to change it, rather than doing it just on one architecture. 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 (FACT-457) A $client_settings fact should exist that returns the client settings
Title: Message Title Branan Riley commented on FACT-457 Re: A $client_settings fact should exist that returns the client settings I think at least some of the agent settings are pushed into a fact in the puppet-agent module now. How close does that come to meeting your needs Trevor Vaughan? 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 (FACT-343) failure to detect if running in a VM
Title: Message Title Branan Riley commented on FACT-343 Re: failure to detect if running in a VM I'm going to close this - we're now two major versions ahead of Facter 1.7. If this affects Facter 3, please feel free to re-open or file an updated ticket. 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title
Alex P updated an issue
Puppet / PUP-7351
PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Change By:
Alex P
Coming back to my [comment ]( | https://tickets.puppetlabs.com/browse/PUP-7289?focusedCommentId=415955=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-415955 ) ] in PUP-7289, `deep merge` option does NOT work at all. As soon as we switch to that one then:- agent would run and "apply" catalog very quickly, e.g. {{Notice: Applied catalog in 0.40 seconds}}, where a _normal_ run would be 1-2 seconds;- whatever changes would be made in {{nodes/vm01.yaml}} or any other file in hierarchy, it'll be ignored.{{unique}} and {{hash}} options are not useful and there is another bug(?) that makes them non-working either.Please advise what additional information do you need. The whole environment and settings as per PUP-7289.
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 (FACT-152) Add type information to network interfaces
Title: Message Title Orion Poplawski commented on FACT-152 Re: Add type information to network interfaces And FWIW, I've switched to using ansible, so I don't need it any more. 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 (FACT-1588) Building with openssl 1.1.0 fails
Title: Message Title Branan Riley commented on FACT-1588 Re: Building with openssl 1.1.0 fails That looks like a breaking change in OpenSSL's API. It should be reasonably easy to check at compile-time and use the appropriate signature in our code. 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-7349) resource type tidy does not honor metaparameter noop
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7349 resource type tidy does not honor metaparameter noop Change By: Eric Delaney Sprint: Agent Triage 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-7349) resource type tidy does not honor metaparameter noop
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7349 resource type tidy does not honor metaparameter noop Change By: Eric Delaney Team: Agent 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7351 PUP 4.9.4 `deep merge` hiera interpolation still doesn't work Change By: Eric Delaney Team: Puppet Developer Experience 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7351 PUP 4.9.4 `deep merge` hiera interpolation still doesn't work Change By: Eric Delaney Sprint: PDE Triage 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 (FACT-152) Add type information to network interfaces
Title: Message Title Branan Riley commented on FACT-152 Re: Add type information to network interfaces Eric Sorenson What do you think of this? This is going to be a pain to implement consistently, and the old Redmine ticket doesn't have any details on use cases. I'm inclined to close this as a "won't do", unless you really want it. 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 (FACT-1589) Need to rethink behavior of specifying facter directory's or not allowing facts
Title: Message Title Eric Delaney commented on FACT-1589 Re: Need to rethink behavior of specifying facter directory's or not allowing facts So a proposed solution would be to apply the configuration files options, and then allow the command line options to override them. For example if the config file said "external-dir" is set to "/tmp/external", and then on the command line we had the option "--no-exter nal-facts" then we would drop the added external directories. The only failure cases would be if conflicting options where configured at the same level, say for example if you used the options --no-external-facts and a --external-dir on the command line, this should cause a conflict error. CLI == Command line Interface CF == configuration file CLI external-dir - external facts found CLI no-external-facts - NO external facts found CLI no-external-facts + CLI external-dir - ERROR conflicting options CF external-dir - external facts found CF external-dir + CLI external-dir - external facts from both directories CF external-dir + CLI no-external-facts - NO external facts found CF no-external-facts - no external facts found CF no-external-facts + CLI external-dir - allow external-dir to be found CF no-external-facts + CLI no-external-facts - NO external facts found CF no-external-facts + CF external-dir - ERROR conflicting options CLI custom-dir - custom facts found CLI no-custom-facts - NO custom facts found CLI no-custom-facts - NO FACTERLIB used CLI no-custom-facts + CLI custom-dir - ERROR conflicting options CF custom-dir - custom facts found CF custom-dir + CLI custom-dir - custom facts from both CF custom-dir + CLI no-custom-facts - NO custom facts found CF no-custom-facts - NO custom facts found CF no-custom-facts - NO FACTERLIB used CF no-custom-facts + CLI custom-dir - custom facts found CF no-custom-facts + CLI no-custom-facts - NO custom facts found CF no-custom-facts + CF custom-dir - ERROR conflicting options Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7119) Acceptance: utf-8 characters in module describe block (puppet describe)
Title: Message Title Eric Thompson assigned an issue to Sean Griffin Puppet / PUP-7119 Acceptance: utf-8 characters in module describe block (puppet describe) Change By: Eric Thompson Assignee: Moses Mendoza Sean Griffin 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-1334) Empty clientbucket files produce errors
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-1334 Empty clientbucket files produce errors Change By: Moses Mendoza Assignee: Moses Mendoza 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title
Alex P updated an issue
Puppet / PUP-7351
PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Change By:
Alex P
Coming back to my [comment](https://tickets.puppetlabs.com/browse/PUP-7289?focusedCommentId=415955=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-415955) in PUP-7289, `deep merge` option does NOT work at all. As soon as we switch to that one then:- agent would run and "apply" catalog very quickly, e.g. {{Notice: Applied catalog in 0.40 seconds}}, where a _normal_ run would be 1-2 seconds;- whatever changes would be made in {{nodes/vm01 , . yaml}} or any other file in hierarchy, it'll be ignored.{{unique}} and {{hash}} options are not useful and there is another bug(?) that makes them non-working either.Please advise what additional information do you need. The whole environment and settings as per PUP-7289.
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 (FACT-1590) facter built with vanagon on F25 for AArch64 has double free bug
Title: Message Title Richard Henwood created an issue Facter / FACT-1590 facter built with vanagon on F25 for AArch64 has double free bug Issue Type: Bug Assignee: Unassigned Created: 2017/03/14 11:25 AM Environment: AArch64, Fedora 25 with pl-build-tools-vanagon installed from git commit 52eb2908d2ea3767ce3c698554ac986d92427ddc . component versions include: ./output/fedora/f25/aarch64/pl-binutils-2.26-4.fedoraf25.aarch64.rpm ./output/fedora/f25/aarch64/pl-boost-1.61.0-0.fedoraf25.aarch64.rpm ./output/fedora/f25/aarch64/pl-cmake-3.5.2-0.fedoraf25.aarch64.rpm ./output/fedora/f25/aarch64/pl-gcc-6.1.0-0.fedoraf25.aarch64.rpm ./output/fedora/f25/aarch64/pl-yaml-cpp-0.5.1-6.fedoraf25.aarch64.rpm
Jira (FACT-1589) Need to rethink behavior of specifying facter directory's or not allowing facts
Title: Message Title Maggie Dreyer commented on FACT-1589 Re: Need to rethink behavior of specifying facter directory's or not allowing facts It seems that we should have the no-XXX-facts options conflict with specifying directories within any one format (CLI or config), but not across them. And the command line should always override what's in the config file. 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-7041) Add Japanese Windows to Puppet acceptance testing matrices
Title: Message Title John O'Connor assigned an issue to John O'Connor Puppet / PUP-7041 Add Japanese Windows to Puppet acceptance testing matrices Change By: John O'Connor Assignee: John O'Connor 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title Alex P created an issue Puppet / PUP-7351 PUP 4.9.4 `deep merge` hiera interpolation still doesn't work Issue Type: Bug Affects Versions: PUP 4.9.4 Assignee: Unassigned Created: 2017/03/14 10:53 AM Environment: Debian GNU/Linux 8.7 (jessie) puppet-agent 1.9.3-1jessie puppetdb 4.3.0-1puppetlabs1 puppetdb-termini 4.3.0-1puppetlabs1 puppetlabs-release-pc1 1.1.0-4jessie puppetserver 2.7.2-1puppetlabs1
Jira (PUP-7350) Update minitar to 0.6.1
Title: Message Title Sean McDonald created an issue Puppet / PUP-7350 Update minitar to 0.6.1 Issue Type: Task Assignee: Sean McDonald Created: 2017/03/14 10:41 AM Priority: Normal Reporter: Sean McDonald The agent has updated vendored minitar to 0.6.1 The version of minitar included in the gem should also use that. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7349) resource type tidy does not honor metaparameter noop
Title: Message Title
R. Schuitemaker updated an issue
Puppet / PUP-7349
resource type tidy does not honor metaparameter noop
Change By:
R. Schuitemaker
The resource type tidy ignores the noop parameter. The code below removes the matching files where it should noop that operation. {{ tidy { 'remove_dot_files': path=> '/home', matches => [ '.rhost', '.netrc', '.forward' ], recurse => true, noop=> true,} }}
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-7349) resource type tidy does not honor metaparameter noop
Title: Message Title
R. Schuitemaker updated an issue
Puppet / PUP-7349
resource type tidy does not honor metaparameter noop
Change By:
R. Schuitemaker
The resource type tidy ignores the noop parameter. The code below removes the matching files where it should noop that operation. {quote}{{ tidy { "${title}:: ' remove_dot_files " ' : path=> '/home', matches => [ '.rhost', '.netrc', '.forward' ], recurse => true, noop=> true,} }}{quote}
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-7349) resource type tidy does not honor metaparameter noop
Title: Message Title
R. Schuitemaker updated an issue
Puppet / PUP-7349
resource type tidy does not honor metaparameter noop
Change By:
R. Schuitemaker
The resource type tidy ignores the noop parameter. The code below removes the matching files where it should noop that operation.{ quote} { { tidy { "${title}::remove_dot_files": path=> '/home', matches => [ '.rhost', '.netrc', '.forward' ], recurse => true, noop=> true,} }} {quote}
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-7349) resource type tidy does not honor metaparameter noop
Title: Message Title
R. Schuitemaker updated an issue
Puppet / PUP-7349
resource type tidy does not honor metaparameter noop
Change By:
R. Schuitemaker
The resource type tidy ignores the noop parameter. The code below removes the matching files where it should noop that operation. {{ tidy { "${title}::remove_dot_files": path=> '/home', matches => [ '.rhost', '.netrc', '.forward' ], recurse => true, noop=> true,} }}
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-7349) resource type tidy does not honor metaparameter noop
Title: Message Title
R. Schuitemaker created an issue
Puppet / PUP-7349
resource type tidy does not honor metaparameter noop
Issue Type:
Bug
Affects Versions:
PUP 4.9.4
Assignee:
Unassigned
Components:
Types and Providers
Created:
2017/03/14 10:02 AM
Priority:
Normal
Reporter:
R. Schuitemaker
The resource type tidy ignores the noop parameter. The code below removes the matching files where it should noop that operation. tidy { "$ {title}
::remove_dot_files": path => '/home', matches => [ '.rhost', '.netrc', '.forward' ], recurse => true, noop => true, }
Add Comment
Jira (PUP-1334) Empty clientbucket files produce errors
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Puppet / PUP-1334 Empty clientbucket files produce errors Change By: Moses Mendoza Assignee: Sean McDonald Moses Mendoza 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 (PDOC-161) As a developer I want to programmatically retrieve the name and short description from a puppet class
Title: Message Title Lindsey Smith updated an issue Puppet Strings / PDOC-161 As a developer I want to programmatically retrieve the name and short description from a puppet class Change By: Lindsey Smith * Use Case: * Vendors like VMware would like a way to discover a list of role classes along with a description of the class. Right now they can pull a class name, but there isn't a standard way to retrieve a short description. puppet-strings is used to document puppet files, but it's also a great way to get easily parseable metadata about a puppet file via the JSON output option(s). * The Issue: * You can get the name from puppet-strings, but puppet-strings (and YARD itself) doesn't have a simple tag for a short description. There is the generic docstring text, but it's freeform and can be multiple lines. It's not ideal. * Proposed Solution: * Create a new puppet-strings-specific YARD tag (similar to puppet.type.param) for storing a short description with a limit of 50-80 characters. This field should show up in the JSON output. Optionally the field can show up in the HTML. 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-7314) Implied module namespace for PCore objects
Title: Message Title Henrik Lindberg commented on PUP-7314 Re: Implied module namespace for PCore objects Rick Sherman That seems to require using the much longer yang name paths to make the types unique. Were you thinking that + imports/aliasing would make it easier to use those longer names ? 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-7347) Loopup function merge behaviour is not optional.
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7347 Loopup function merge behaviour is not optional. Change By: Eric Delaney Team: Puppet Developer Experience 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-7347) Loopup function merge behaviour is not optional.
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7347 Loopup function merge behaviour is not optional. Change By: Eric Delaney Sprint: PDE Triage 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-7328) Duplication errors on Puppet Class "settings".
Title: Message Title Henrik Lindberg commented on PUP-7328 Re: Duplication errors on Puppet Class "settings". Waiting on PUP-7313 to avoid merge conflicts. 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-7348) 1.9.3 breaks using variables from site.pp in hiera.yaml
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7348 1.9.3 breaks using variables from site.pp in hiera.yaml Change By: Eric Delaney Team: Puppet Developer Experience 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-7348) 1.9.3 breaks using variables from site.pp in hiera.yaml
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7348 1.9.3 breaks using variables from site.pp in hiera.yaml Change By: Eric Delaney Sprint: PDE Triage 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-7343) exec path and environment attributes do not work as documented
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7343 exec path and environment attributes do not work as documented Change By: Eric Delaney Sprint: Agent Triage 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-7343) exec path and environment attributes do not work as documented
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7343 exec path and environment attributes do not work as documented Change By: Eric Delaney Team: Agent 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-7182) Do not report errors in Hiera config as errors in Puppet manifest
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7182 Do not report errors in Hiera config as errors in Puppet manifest Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-7341) Regex Lookup isn't working with Puppet 4.9
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7341
Regex Lookup isn't working with Puppet 4.9
Change By:
Henrik Lindberg
Story Points:
1
Release Notes Summary:
If all keys specifying {{lookup_options}} in hiera data files were based on regular _expression_ patterns, puppet would crash. This is now fixed. A work around while waiting for the fix is to add a lookup options for a dummy fixed key.
Team:
Puppet Developer Experience
Release Notes:
Bug Fix
{code:java}root@mbaur-hieradebug:/etc/puppetlabs/code/environments/production# cat hiera.yamlversion: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Per-node data (yaml version)"path: "nodes/%{trusted.certname}.yaml" # Add file extension.# Omitting datadir and data_hash to use defaults. - name: "Other YAML hierarchy levels"paths: # Can specify an array of paths instead of one. - "location/%{facts.whereami}/%{facts.group}.yaml" - "groups/%{facts.group}.yaml" - "os/%{facts.os.family}.yaml" - "common.yaml"root@mbaur-hieradebug:/etc/puppetlabs/code/environments/production# cat hieradata/common.yaml---classes: - foobarlookup_options: "^profile::(.*)::users$": # Regexp: `$users` parameter of any profile classmerge: # Merge behavior as a hash strategy: deep merge_hash_arrays: trueroot@mbaur-hieradebug:/etc/puppetlabs/code/environments/production# puppet lookup classesError: Could not run: undefined method `[]' for nil:NilClass{code}The following things has been changed compared to an pure puppet-agent installation:- /etc/puppetlabs/puppet/hiera.yaml deleted- /etc/puppetlabs/code/environments/production/hiera.yaml created with code from https://docs.puppet.com/puppet/4.9/hiera_migrate_v3_yaml.html#translating-built-in-backends . Only the datadir was changed to hieradata- /etc/puppetlabs/code/environments/production/hieradata/common.yaml was created. For code see above.
Jira (PUP-7341) Regex Lookup isn't working with Puppet 4.9
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7341 Regex Lookup isn't working with Puppet 4.9 Change By: Henrik Lindberg Fix Version/s: PUP 4.10.0 Fix Version/s: PUP 4.9.z 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-7318) Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10
Title: Message Title Moses Mendoza assigned an issue to Ethan Brown Assigning to ethan for revert PR of SemVer per conversation in standup Puppet / PUP-7318 Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10 Change By: Moses Mendoza Assignee: Ethan Brown 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.
