Jira (HI-496) Hiera subkeys lookup should be configurable
Title: Message Title Adrian Muraru commented on HI-496 Re: Hiera subkeys lookup should be configurable HI-504 solves this issue Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title O'Shaughnessy Evans commented on HI-496 Re: Hiera subkeys lookup should be configurable Just to add another data point, this bit me, too. We had some top-level hiera keys (in the YAML backend) that used domain names. I was able to migrate away from them, but it did take quite a bit of looking just to figure out what the problem was. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Kylo Ginsberg commented on HI-496 Re: Hiera subkeys lookup should be configurable Yes, we intend to release hiera 3.1.0 (including HI-471 ) with puppet 4.4.0 in puppet-agent 1.4.0. Probably not this week, but next. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg commented on HI-496 Re: Hiera subkeys lookup should be configurable Ping Kylo Ginsberg - if not already on the radar; we should release Hiera 3.1.0 with Puppet 4.4.0. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Adrian Muraru commented on HI-496 Re: Hiera subkeys lookup should be configurable Henrik Lindberg Using a custom backend helps disabling subkey lookup. Got one question though - HI-471 doesn't seem to be integrated in the latest Puppet4 puppet-agent package (1.3.5). require "hiera/backend/yaml_backend" class Hiera module Backend class Yaml_nosubkeys_backend < Yaml_backend # When hiera backends define lookup_with_segments method # subkey lookup is delegated to it. # See HI-471 - https://github.com/puppetlabs/hiera/commit/5b4b8f # We use this to disable subkey lookup (and thus allow dot separated keys in yaml files) def lookup_with_segments(segments, scope, order_override, resolution_type, context)
Jira (HI-496) Hiera subkeys lookup should be configurable
Title: Message Title Andreas Ntaflos commented on HI-496 Re: Hiera subkeys lookup should be configurable Will do, thanks for the pointer! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg commented on HI-496 Re: Hiera subkeys lookup should be configurable Please file a ticket for hiera-file backend. It should simply use the option to receive raw keys. It is dead simple to add that. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Andreas Ntaflos commented on HI-496 Re: Hiera subkeys lookup should be configurable To add a related perspective: this also hits those who use the hiera-file. We don't have dots in any of our normal Hiera lookup keys but the content of files in the hiera-file backend is looked up using the file name as key, and that will almost invariably and naturally contain at least one dot. For example: ssldata/projects.d/www.example.com.crt.pem ssldata/mcollective.d/mcollective-servers.crt.pem ssldata/mcollective.d/mcollective-servers.key.pem Looking up mcollective-servers.crt.pem with Hiera returns the contents of the file ssldata/mcollective.d/mcollective-servers.crt.pem which we then pass to content of a File resource that manages that certificate on the target systems. To make this work with Hiera 2/3 we have to rename all files so something like this: ssldata/projects.d/www_example_com_crt_pem ssldata/mcollective.d/mcollective-servers_crt_pem ssldata/mcollective.d/mcollective-servers_key_pem Not exactly a showstopper but a PITA and somewhat unnatural for files.
Jira (HI-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg commented on HI-496 Re: Hiera subkeys lookup should be configurable I have not looked at the implementation of the hiera-wrapper, but the user reported it as working for them. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg commented on HI-496 Re: Hiera subkeys lookup should be configurable The ticket HI-421 is about a "whitelist filter". That ended with the user writing a hiera-wrapper backend. You can find that here: https://github.com/senax/hiera-wrapper (that is the white list wrapper), which you can probably use as a model for how to do what you want. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg commented on HI-496 Re: Hiera subkeys lookup should be configurable The feature to let a backend take over is HI-471 . There is no example of a wrapping backend related to that. One other users created a wrapping backend for another purpose IIRC. Will try to find that ticket as well. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Adrian Muraru commented on HI-496 Re: Hiera subkeys lookup should be configurable Please link this jira to the original request to see how the bacjend would look like. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg commented on HI-496 Re: Hiera subkeys lookup should be configurable I understand the pain but that will be very difficult to achieve as the defaults are using subkey lookup to get into trusted facts. Note that '.' in keys were never intended to be supported, they just happened to work. Since this has been out now for quite some time, and there has only been one earlier issue-report where this was troublesome enough to file a ticket which we closed that with a Won't Fix (it did suggest we revert the change though), I am also going to close this the same way. What you can do, if you are on one of the latest versions of puppet is to write a wrapper hiera backend. We now support that a hiera backend can be responsible for interpretation of subkeys. It needs to have a method that declares that it wants to do subkey handling on its own, and then the keys will be passed verbatim to the backend (instead of now, being interpreted by hiera itself). Once you have changed all of the keys with a period in them, you can change back to the standard backend. If you are interested in doing this, I can point you to the ticket that describes how it works. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-496 Hiera subkeys lookup should be configurable Change By: Henrik Lindberg Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-496) Hiera subkeys lookup should be configurable
Title: Message Title Adrian Muraru created an issue Hiera / HI-496 Hiera subkeys lookup should be configurable Issue Type: Bug Affects Versions: HI 3.0.6 Assignee: Unassigned Created: 2016/01/28 7:19 AM Priority: Normal Reporter: Adrian Muraru Hiera 3 introduced support for subkeys lookup: Qualified keys are composed of a top-level lookup key along with any number of additional subkeys, separated by dots. While this is a cool feature it is breaking existing hiera configuration where . was used in the yaml key, e.g. my.key.with.dot: "text"
