Jira (PUP-1078) Exported resources are hard to collect by environment
Title: Message Title Wyatt Alt commented on PUP-1078 Re: Exported resources are hard to collect by environment Linked to PDB-558, which seems fundamentally related. Ryan C. will have a better sense of the roadmap questions. 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-7090) Better error message for source => puppet://foo/bar
Title: Message Title Josh Cooper commented on PUP-7090 Re: Better error message for source => puppet://foo/bar This is tricky. It is completely valid to specify a host in the URI. So puppet://foo/bar says to connect to host foo on port 8140 (the default masterport) and use the bar mount point. Whereas puppet:///foo/bar says to connect to the default server or server_list on port 8140, use the foo mount point, and the relative file path bar. In this case, we could validate that the URI path has at least two components (foo and bar corresponding to the mount point and relative path). But that wouldn't help things like puppet://foo/bar/baz. The other thing that complicates this is the user can create custom mount points. 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-7044) Add Japanese Windows to Puppet spec testing matrices
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7044 Add Japanese Windows to Puppet spec testing matrices Change By: Geoff Nichols Sprint: AP 2017-02-08 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 (HI-518) How to make hiera_xxx functions delegate to lookup()
Title: Message Title Lindsey Smith commented on HI-518 Re: How to make hiera_xxx functions delegate to lookup() OK, so we could close this after Puppet 4.9 ships? 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 (HI-518) How to make hiera_xxx functions delegate to lookup()
Title: Message Title Henrik Lindberg commented on HI-518 Re: How to make hiera_xxx functions delegate to lookup() This is relevant in as much as before hiera 5, the hiera functions were not delegating at all to lookup. Now they do without any jumping through hoops. Hence, we did deliver of this ticket's original intent. What remains is only documentation. If there are other tickets that cover that, this ticket requires no further action. 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-6958) Ship locale files as part of the Puppet gem
Title: Message Title Moses Mendoza commented on PUP-6958 Re: Ship locale files as part of the Puppet gem merged to master at https://github.com/puppetlabs/puppet/commit/210bc4a67dcbc4314322716b90bf40c630e4376b 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-5635) accessing facts via another scope
Title: Message Title Henrik Lindberg commented on PUP-5635 Re: accessing facts via another scope Eric Sorenson Any thoughts after reading Gary's conclusion? I took his conclusion as 'ok to change this' (I am also in favour of making this change in 5.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 (PUP-7021) Handle incompatible encodings in Puppet::Parameter#format
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Puppet / PUP-7021 Handle incompatible encodings in Puppet::Parameter#format 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-7098) Acceptance: utf-8 characters in catalog
Title: Message Title Sean Griffin created an issue Puppet / PUP-7098 Acceptance: utf-8 characters in catalog Issue Type: Improvement Assignee: Sean Griffin Created: 2017/01/12 3:06 PM Priority: Normal Reporter: Sean Griffin Acceptance test to verify correct behavior when utf-8 characters in the catalog. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6935) Investigate how puppet's install.rb behaves on Windows to determine localedir default
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6935 Investigate how puppet's install.rb behaves on Windows to determine localedir default Change By: Steve Barlow Labels: i18n 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-7043) Mark debug messages for externalization
Title: Message Title Steve Barlow updated an issue Puppet / PUP-7043 Mark debug messages for externalization Change By: Steve Barlow Labels: i18n 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-7042) Mark non-debug messages for externalization
Title: Message Title Steve Barlow updated an issue Puppet / PUP-7042 Mark non-debug messages for externalization Change By: Steve Barlow Labels: i18n 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-6958) Ship locale files as part of the Puppet gem
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6958 Ship locale files as part of the Puppet gem Change By: Steve Barlow Labels: i18n 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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Moses Mendoza commented on HI-519 Re: Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 hi Kenn Hussey - yes, 3.3.0 is fine 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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Moses Mendoza updated an issue Hiera / HI-519 Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 Change By: Moses Mendoza Fix Version/s: HI 3.3.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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Kenn Hussey commented on HI-519 Re: Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 Moses Mendoza which fix version should this be targeted for? 3.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 (PUP-7093) Parser Combinators
Title: Message Title Thomas Hallgren commented on PUP-7093 Re: Parser Combinators Although elegant, I don't think this proposal is feasible. A simple example like the Variant above where the Concat starts and ends with an Enum could perhaps work, but the more patterns, enums, and other types come into play and gets concatenated, the more inefficient the type checking would become. Some kind of scanner would need to be involved, attempting to resolve the first type, then the next, if next fails, go back to the first, retry with a different resolution (a pattern may match a partial string in more ways than one, especially if it's not anchored), try the next again, etc. until all types resolve (or not). The number of possible permutations that the resolver would need to go through would very quickly become very high. 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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Moses Mendoza updated an issue Hiera / HI-519 Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 Change By: Moses Mendoza Sprint: AP 2017-01-25 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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Moses Mendoza updated an issue Hiera / HI-519 Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 Change By: Moses Mendoza Story Points: 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 (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Moses Mendoza commented on HI-519 Re: Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 Ethan Brown this probably qualifies as that low-hanging fruit we talked about in planning. PR re-raised 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-5635) accessing facts via another scope
Title: Message Title Gary Larizza commented on PUP-5635 Re: accessing facts via another scope So - should we stop that last, IMO erroneous step of variable resolution of fully qualified variables? Yes, I would definitely agree with you there there should IMO be a difference between accessing $foo in the code block that is inside the class test (it should resolve to the global variable $::foo since there is no local $foo), and one that is an external request to the fully qualified name $test::foo, which should not resolve to $::foo because there is no $::test::foo variable. I would agree here too. When I write code, I have no expectation that a fully qualified variable from an outside scope will continue the resolution if it doesn't exist (and then move on to look for a fact value) that's completely surprising. We've never taught that, and I've never seen code that relies on that behavior before. 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-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2997 Logdest cannot be set in the puppet.conf Change By: Charlie Sharpsteen Affects Version/s: PUP 3.8.7 Affects Version/s: PUP 4.8.1 CS Priority: Needs Priority Team: Agent & Platform 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-481) Make variable references strict by default
Title: Message Title Henrik Lindberg commented on PUP-481 Re: Make variable references strict by default The downside is that it complicates variable resolution and that has a performance cost and cost of maintaining more complex logic. We could consider making it strict_variables by default, and users could opt-out if they have lots of problems rather than making it always strict. While that would help with their code quality it does not provide any other benefit (increased performance) until we remove the opt-out ability. I am leaning towards skipping this in Puppet 5.0.0 for the sake of a smoother upgrade. (Also thinking about our own cost as we would have to refactor aprox 70 tests in puppet, and an unknown amount of tests in supported modules). 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-7096) lookup --explain can be unclear about results
Title: Message Title Thomas Hallgren commented on PUP-7096 Re: lookup --explain can be unclear about results This might boil down to a documentation issue. The output of lookup can be controlled. It's done using the option --render-as. The default when not using --explain is to output the found value as yaml. puppet lookup --render-as json environment_key2 "env value2" puppet lookup --render-as console environment_key2 env value2 The output from --explain can also be controlled using --render-as but the default output is indented text. It shows: layer (global, env, module) hierarchy entry within layer path for specific entry
Jira (PUP-4947) Remove special handling of reserved keywords 'application', 'consumes', 'produces'
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4947 Remove special handling of reserved keywords 'application', 'consumes', 'produces' 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 (PDB-3249) Undeduplicate fact values
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3249 Undeduplicate fact values Change By: Karen Van der Veer Epic Colour: ghx-label- 3 4 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-4947) Remove special handling of reserved keywords 'application', 'consumes', 'produces'
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4947
Remove special handling of reserved keywords 'application', 'consumes', 'produces'
Change By:
Henrik Lindberg
Story Points:
1 2
Release Notes Summary:
The keywords 'site', 'application', 'consumes' and 'produces' that were earlier opt-in via the {{\-\-app_management}} setting are now always keywords. The {{\-\-app_management}} setting is now also deprecated, but will remain as a setting without any effect until Puppet 6.0.0. This means that puppet will always be enabled for application management without the earlier required opt-in.
Sprint:
PDE 2017-01-25
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
Jira (PUP-4947) Remove special handling of reserved keywords 'application', 'consumes', 'produces'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4947 Remove special handling of reserved keywords 'application', 'consumes', 'produces' Change By: Henrik Lindberg The keywords 'site', 'application', 'produces' and 'consumes' were introduced as reserved words in 3.8.2. They are opt-in as keywords in 4.x. Now in 5.0.0 the special handling should be removed as they should always be in effect. When these become regular keywords, the corresponding setting for the opt-in should be deprecated but be left as a setting to allow graceful upgrades. (A removal ticket is needed for PUP 6.0.0 for the setting as such). 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-869) Deprecate file Face
Title: Message Title Moses Mendoza commented on PUP-869 Re: Deprecate file Face Second PR merged to master at https://github.com/puppetlabs/puppet/commit/485ab7bd5b4aa6471ed480c2382902f7a40c68ed 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-4947) Remove special handling of reserved keywords 'application', 'consumes', 'produces'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4947 Remove special handling of reserved keywords 'application', 'consumes', 'produces' Change By: Henrik Lindberg The keywords ' site', ' application', 'produces' and 'consumes' were introduced as reserved words in 3.8.2. They are opt-in as keywords in 4.x. Now in 5.0.0 the special handling should be removed as they should always be in effect. 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-5635) accessing facts via another scope
Title: Message Title Henrik Lindberg commented on PUP-5635 Re: accessing facts via another scope I should add, that the problem becomes worse (i.e. total mystery) when inheritance is involved and when fully qualified variables are accessed in default value expressions as it is more unclear to the author (or person debugging the problem) in understanding where all values are/shoud-be coming from. You have to be both experienced and think hard to untangle what is going on (both of you had problems reading the code and figuring out what was wrong - which is telling given that you have extensive knowledge and experience in puppet). So - should we stop that last, IMO erroneous step of variable resolution of fully qualified variables? Is it ever a valid design to get access to top scope variables that way? And (lastly) will this cause unacceptable breakage in the PUP 5.0.0 release (it will probably break someone somewhere, but doubt it is a general problem). 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-5635) accessing facts via another scope
Title: Message Title Henrik Lindberg commented on PUP-5635 Re: accessing facts via another scope Yes, basically, the lookup of a variable value is "routed" to a named scope - if not there, it goes to its parent (inherited scope if such a scope exists), if not there the search proceeds as if it was a request for the value of a local variable in that scope. The last part is what is wrong. In the case there is a top scope variable (typically a fact) with the same (leaf) name that value is returned. That is very surprising and IMO wrong. In the example - there should IMO be a difference between accessing $foo in the code block that is inside the class test (it should resolve to the global variable $::foo since there is no local $foo), and one that is an external request to the fully qualified name $test::foo, which should not resolve to $::foo because there is no such variable. The really bad surprise is when there is an addition of a new fact that happens to have the same name as variables in classes and where logic is conditional on such variables having a value. Users would need to have made a series of bad design decisions to end up in that situation, but that is unfortunately often the case. 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-1558) Facter fails if current working directory has been removed.
Title: Message Title Michael Stahnke created an issue Facter / FACT-1558 Facter fails if current working directory has been removed. Issue Type: Bug Assignee: Unassigned Created: 2017/01/12 12:40 PM Priority: Minor Reporter: Michael Stahnke When performing some adminstrations (and messing up) I noticed that if you remove your current working directory, facter will fail [root@kerminator-new kerminator]# facter 2017-01-12 12:36:55.255862 FATAL puppetlabs.facter - unhandled exception: boost::filesystem::current_path: No such file or directory Puppet does as well [root@kerminator-new
Jira (PDB-3257) (maint) Bump to new ezbake
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3257 (maint) Bump to new ezbake Issue Type: Bug Assignee: Unassigned Created: 2017/01/12 12:01 PM Priority: Normal Reporter: gepetto-bot 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7088 deep merge options in hiera v3 config not honored Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests; deprecated behavior; low risk QA Risk Assessment: Needs Assessment No Action 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-5635) accessing facts via another scope
Title: Message Title Gary Larizza commented on PUP-5635 Re: accessing facts via another scope Ahhh, thanks for the clarification. Damn, this problem again! If I understand it correctly (now), the issue is that $test::foo doesn't exist, so it tries to use relative scoping to look for $foo and finds it in top scope - right? And this happens regardless of whether you fully-scope the variable (i.e. $::test::foo) - is that because Puppet will always attempt to do a relative lookup for a variable in the local scope? This case is unique because it will actually MATCH a top scope variable (i.e. a fact), and it's surprising because now you have a value, correct? 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-6958) Ship locale files as part of the Puppet gem
Title: Message Title Maggie Dreyer assigned an issue to Unassigned Puppet / PUP-6958 Ship locale files as part of the Puppet gem Change By: Maggie Dreyer Assignee: Maggie Dreyer 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-1583) Non ASCII comments in puppet.conf causes exception
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1583 Non ASCII comments in puppet.conf causes exception Change By: Moses Mendoza Story Points: 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-1583) Non ASCII comments in puppet.conf causes exception
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-1583 Non ASCII comments in puppet.conf causes exception Change By: Moses Mendoza Sprint: AP 2017-01-25 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-1583) Non ASCII comments in puppet.conf causes exception
Title: Message Title
Moses Mendoza commented on PUP-1583
Re: Non ASCII comments in puppet.conf causes exception
I was unable to reproduce this on a 4.8.1 agent on Ubuntu (tested with locale Japanese and locale ISO-8859-1) or a 4.7.0 agent on centos (locale UTF-8).
Added utf-8 comments to puppet.conf:
☂ : cat /etc/puppetlabs/puppet/puppet.conf
# ☃
# Что-то там
server = centos7.localdomain
☂ : : puppet apply -e " notify { 'foo' : } "
Notice: Compiled catalog for ubuntu16.localdomain in environment production in 0.06 seconds
Notice: foo
Notice: /Stage[main]/Main/Notify[foo]/message: defined 'message' as 'foo'
Notice: Applied catalog in 0.03 seconds
☂ : puppet agent -t
Jira (PUP-5635) accessing facts via another scope
Title: Message Title
Henrik Lindberg commented on PUP-5635
Re: accessing facts via another scope
the example is more complicated than what it needs to be - the problem is that an attempt to access something with a fully qualified name where the last part of the name does not reference an existing variable in that namespace the result is that it will lookup a global (top scope) variable with the same name. The inheritance in the example just makes the problem even more convoluted.
This illustrates the fundamental problem:
$foo = 100
class test {
$testvar = 10
$fooo = 10 # i.e. not foo
}
include test
notice $test::foo
There is no $test::foo (does not help to use $::test::foo) but you still get the value 100 from the top scope variable. SURPRISE !
Jira (PUP-5635) accessing facts via another scope
Title: Message Title Gary Larizza commented on PUP-5635 Re: accessing facts via another scope Lemme see if I can summarize. I see a couple of things going on: 1.) The notice prints out the timezone fact because a local variable of $timezone does not have a value, and thus it jumps to top scope to gather the value (as a result of the Puppet 3.x change to remove dynamic scoping and look in two distinct places for a value: local scope and top scope) 2.) The timezone PARAMETER has no value because none was passed and the default value is undefined 3.) Maybe it's a typo but your class is inheriting from 'params' and not 'test::params', but it doesn't matter anyway because there's no default value either way. Is it true that the surprising behavior is #2, namely because the parameter has no "value" (but a value for the variable $timezone is gathered because of #1)? If so, it seems to be an issue with the internals in Puppet ensuring that all class parameters have values, and not so much with strict_variables (though I defer to Henrik Lindberg here). Does that sound correct? 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-7095) Enable portage install and uninstall options
Title: Message Title Matthew Thode commented on PUP-7095 Re: Enable portage install and uninstall options The PR for this is in https://github.com/puppetlabs/puppet/pull/5498 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-7097) Support progress reporting for long-running commands invoked by providers during "puppet apply"
Title: Message Title Greg Larkin created an issue Puppet / PUP-7097 Support progress reporting for long-running commands invoked by providers during "puppet apply" Issue Type: New Feature Assignee: Unassigned Created: 2017/01/12 10:27 AM Priority: Normal Reporter: Greg Larkin I would be interested to know if it's possible to add a callback mechanism to the types & providers framework so a provider can supply progress information to Puppet during "puppet apply" runs. Some providers may call long-running commands, such as curl on a large download file, and where possible, it would be an improved user experience to see how much time the operation will take. I expect this would be most useful during "puppet apply" and perhaps "puppet agent -t" running in the foreground. I envision a possible implementation using a callback mechanism. If supplied by a particular T, Puppet could query its progress percentage callback and report back to the user in realtime. Of course, the T would need to be able to extract this information from the underlying command or perhaps supply an estimate based on a calculation of some kind. Feedback and criticism of this idea are welcome! Add Comment
Jira (PUP-7096) lookup --explain can be unclear about results
Title: Message Title Eric Thompson commented on PUP-7096 Re: lookup --explain can be unclear about results ping Lindsey Smith for product input on how this should work. 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-7096) lookup --explain can be unclear about results
Title: Message Title Eric Thompson created an issue Puppet / PUP-7096 lookup --explain can be unclear about results Issue Type: Improvement Assignee: Unassigned Created: 2017/01/12 10:24 AM Priority: Normal Reporter: Eric Thompson the puppet lookup command presents results in a strange format. YAML? no matter what backend/data format is used. also, --explain can make it unclear what the final result is, and is in a possibly different format (puppet?). [root@yfvz7smg1d39yfg ~]# puppet lookup --environment v3_config_and_data_v2q6tg7e environment_key2 Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5 (in /etc/puppetlabs/puppet/hiera.yaml)
Jira (PUP-5635) accessing facts via another scope
Title: Message Title Eric Sorenson commented on PUP-5635 Re: accessing facts via another scope the meaning is give me timezone as seen when being an unqualified variable in the scope ::test::params maybe I'm missing some nuance but this seems exactly right and afaik is a common pattern, though it's probably an older convention that's been overtaken by param lookup and hiera vs params class inheritance best practices. Gary Larizza any opinion? 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-4947) Remove special handling of reserved keywords 'application', 'consumes', 'produces'
Title: Message Title Eric Sorenson commented on PUP-4947 Re: Remove special handling of reserved keywords 'application', 'consumes', 'produces' They should always be in effect for puppet 5. 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-7095) Enable portage install and uninstall options
Title: Message Title Matthew Thode created an issue Puppet / PUP-7095 Enable portage install and uninstall options Issue Type: New Feature Affects Versions: PUP 4.8.1 Assignee: Unassigned Components: Types and Providers Created: 2017/01/12 9:55 AM Priority: Normal Reporter: Matthew Thode Portage (emerge) supports being run with command line options, lets allow there use. emerge --with-bdeps=y --update --deep etc Add Comment
Jira (PUP-481) Make variable references strict by default
Title: Message Title Eric Sorenson commented on PUP-481 Re: Make variable references strict by default Yes, this would be disruptive and should not go in Pup5. (Is there a downside to making it opt-in forever?) 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-7074) rabbitmq_home parameter doesn't really affect all relevant places
Title: Message Title Moses Mendoza commented on PUP-7074 Re: rabbitmq_home parameter doesn't really affect all relevant places thanks for the additional context Ira Abramov 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-5635) accessing facts via another scope
Title: Message Title Henrik Lindberg commented on PUP-5635 Re: accessing facts via another scope As much as I would like to fix this, the fix has the potential to cause mysterious errors where code that previously worked will get an undef value. I am more in favor of doing this in PUP 5.0.0 if 'strict_variables' also become the default (PUP-481) as then there is at least a clear error to act on. Ping Eric Sorenson 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-4947) Remove special handling of reserved keywords 'application', 'consumes', 'produces'
Title: Message Title Henrik Lindberg commented on PUP-4947 Re: Remove special handling of reserved keywords 'application', 'consumes', 'produces' Ping Eric Sorenson - do you like this for PUP 5.0.0, or should these keywords continue to be considered "experimental" in Puppet. 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-481) Make variable references strict by default
Title: Message Title Henrik Lindberg commented on PUP-481 Re: Make variable references strict by default Ping Eric Sorenson - this is not included in the list of deprecations/removals that has been floating around for PUP 5.0.0. I think that turning on 'strict_variables' by default may cause quite a lot of work for users - especially in their tests. Move this to PUP 6.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 (PUP-1434) Disallow manifests from declaring things outside the namespace implied by their filenames
Title: Message Title Henrik Lindberg commented on PUP-1434 Re: Disallow manifests from declaring things outside the namespace implied by their filenames PUP-4242 will not make it into a 4.y version and this (1434) ticket is therefore moved to PUP 6.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 (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4242 Add deprecation warnings for manifests declaring things in wrong namespace Change By: Henrik Lindberg Fix Version/s: PUP 4.y Fix Version/s: PUP 5.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 (PUP-1434) Disallow manifests from declaring things outside the namespace implied by their filenames
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1434 Disallow manifests from declaring things outside the namespace implied by their filenames Change By: Henrik Lindberg Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 6.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 (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Henrik Lindberg commented on PUP-4242 Re: Add deprecation warnings for manifests declaring things in wrong namespace Since there is no time left to do this in the 4.y series this ticket is moved to 5.0.0 (for possible later being moved to a 5.y as the change to make these cases into errors cannot take place until PUP 6.0.0). The ticket PUP-1434 will now also be for PUP 6.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 (PUP-7088) deep merge options in hiera v3 config not honored
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7088 deep merge options in hiera v3 config not honored Change By: Henrik Lindberg Release Notes Summary: part of hiera 5 feature, problem this ticket solves was introduced in unreleased code. Release Notes: Not Needed 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Henrik Lindberg commented on PUP-7088 Re: deep merge options in hiera v3 config not honored Reluctantly merged to master at: 38b9889 - because we "must" 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Thomas Hallgren commented on PUP-7088 Re: deep merge options in hiera v3 config not honored No, we don't need to test for parameters. The lookup API does not support :unpack_array. We removed that in PUP-6040. This only applies to the options declared in the hiera.yaml version 3 file. Nothing else. And since version 3 is deprecated already, no further deprecation needs to take place. 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Henrik Lindberg commented on PUP-7088 Re: deep merge options in hiera v3 config not honored well, that leads to more work: test that it works for a parameter like :unpack_array we need to deprecate the use of unsupported merge options in the v3 format in puppet 4.9.0 (I suppose) need to remove the special case in puppet 6.0.0 bloat have this dialog open up for potentially other wacky options that will give us/users grief later on This for a parameter that there is no practical use for whatsoever ? 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Thomas Hallgren commented on PUP-7088 Re: deep merge options in hiera v3 config not honored Henrik Lindberg, the time is already spent. A PR is up. It doesn't just cover the :unpack_arrays but also other potential differences caused by use of a more recent deep_merge gem (and of course, if we decide to upgrade the one we have). 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-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Thomas Hallgren commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error Henrik Lindberg, I have already added a release note that I think is accurate. 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-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Henrik Lindberg commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error Kenn Hussey Eric Thompson So, while we have fixed a follow on problem of "there is no environment" that caused the error seen in this ticket, the fix of that problem has not addressed the potential underlying "if there is no environment puppet sometimes blows up" problem. Without a reproducer it is impossible to tell. If we are to release note this, it would be to just note that the particular error will no longer occur. We can do that, but think further testing is required to ensure there is no root cause that now causes something else to blow up (unknown at this point because there is no reproducer). 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Henrik Lindberg commented on PUP-7088 Re: deep merge options in hiera v3 config not honored Please don't worry or spend too much time on :unpack_arrays, it is an option that has no value to anyone using puppet as it is specialized for processing data related to HTML forms. For everyone else it is just super weird. 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-7081) acceptance: defined Objects in catalog and used on the agent/apply
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7081 acceptance: defined Objects in catalog and used on the agent/apply 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-7081) acceptance: defined Objects in catalog and used on the agent/apply
Title: Message Title Thomas Hallgren commented on PUP-7081 Re: acceptance: defined Objects in catalog and used on the agent/apply Merged to master at fd15a6b. 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-7081) acceptance: defined Objects in catalog and used on the agent/apply
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7081 acceptance: defined Objects in catalog and used on the agent/apply Change By: Thomas Hallgren Assignee: Eric Thompson 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-7008) acceptance: hiera v5 can use hiera v3 config and datafiles
Title: Message Title Thomas Hallgren commented on PUP-7008 Re: acceptance: hiera v5 can use hiera v3 config and datafiles Merged to master at ab7d84b. 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-7008) acceptance: hiera v5 can use hiera v3 config and datafiles
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7008 acceptance: hiera v5 can use hiera v3 config and datafiles Change By: Thomas Hallgren Assignee: Eric Thompson 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7088 deep merge options in hiera v3 config not honored 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7088 deep merge options in hiera v3 config not honored Change By: Thomas Hallgren Story Points: 1 Sprint: PDE 2017-01-25 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7088 deep merge options in hiera v3 config not honored Change By: Thomas Hallgren Fix Version/s: PUP 4.9.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 (PUP-7088) deep merge options in hiera v3 config not honored
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7088 deep merge options in hiera v3 config not honored Change By: Thomas Hallgren Assignee: Eric Thompson 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-7088) deep merge options in hiera v3 config not honored
Title: Message Title Thomas Hallgren commented on PUP-7088 Re: deep merge options in hiera v3 config not honored Hiera v3 should not impose limit on supported options for merge options declared in the configuration. So :unpack_arrays (or any other option supported by the vendored deep_merge gem), must be supported in the v3 config to be backward compatible with classic Hiera. 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-7092) Documentation on Hiera 3.2 references the wrong documentation
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7092 Documentation on Hiera 3.2 references the wrong documentation Change By: Thomas Hallgren The Puppet documentation that [describes merge behaivor|https://docs.puppet.com/hiera/3.2/configuring.html#mergebehavior] is pointing to Github and [danielsdeleo/deep_merge|https://github.com/danielsdeleo/deep_merge/blob/master/README.md]. This gem is more recent than the gem bundled by Puppet and the referenced documentation list options that Puppet does not support.The documentation stays incorrect even if a decision is made to update the gem since Puppet limits the supported set (see PUP-6074).The current set list of supported deep merge options (the bundled gem) can be found here: https:// docs github . puppet. com/ puppetlabs/ puppet/ 4.8 tree / function.html#merge-behaviors master/lib/puppet/vendor/deep_merge 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-7092) Documentation on Hiera 3.2 references the wrong documentation
Title: Message Title Thomas Hallgren commented on PUP-7092 Re: Documentation on Hiera 3.2 references the wrong documentation Then again, on Hiera version 3, we should not impose limit on what options that are supported. Not supporting :unpack_arrays isn't backward compatible. 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-7094) Possible bug in Puppet parser
Title: Message Title Rune Juhl Jacobsen created an issue Puppet / PUP-7094 Possible bug in Puppet parser Issue Type: Bug Assignee: Unassigned Components: Language Created: 2017/01/12 12:31 AM Priority: Normal Reporter: Rune Juhl Jacobsen In testing a small parser for the AST that `puppet parser dump` outputs I stumbled upon the following oddity: runejuhl@bucaramanga:~$ puppet --version 4.8.1 runejuhl@bucaramanga:~$ cat puppet-fails.pp
Jira (PUP-7092) Documentation on Hiera 3.2 references the wrong documentation
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7092 Documentation on Hiera 3.2 references the wrong documentation Change By: Thomas Hallgren Summary: vendored deep_merge gem needs to be updated Documentation on Hiera 3 . 2 references the wrong documentation 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-7092) vendored deep_merge gem needs to be updated.
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7092 vendored deep_merge gem needs to be updated. Change By: Thomas Hallgren The deep_merge gem under lib/puppet/vendor is of version 1.0.1. The Puppet documentation that [describes merge behaivor|https://docs.puppet.com/hiera/3.2/configuring.html#mergebehavior] is however pointing to Github and [danielsdeleo/deep_merge|https://github.com/danielsdeleo/deep_merge/blob/master/README.md] which . This gem is more recent than the gem bundled by Puppet and supports more merge the referenced documentation list options . In order to support all merge options that the Puppet does not support.The documentation claims we do, we must stays incorrect even if a decision is made to update the gem or alternatively, stop vendoring it and instead add a dependency since Puppet limits the supported set (see PUP-6074) . The current set of supported deep merge options can be found here: https://docs.puppet.com/puppet/4.8/function.html#merge-behaviors 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.
