Jira (HI-234) Hiera should be able to include external files within the YAML/JSON hierarchy.
Title: Message Title Henrik Lindberg commented on HI-234 Re: Hiera should be able to include external files within the YAML/JSON hierarchy. We have added support for "glob" in hiera version 5 to be released in Puppet 4.9.0. (The solution cannot be backported to hiera 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 (HI-234) Hiera should be able to include external files within the YAML/JSON hierarchy.
Title: Message Title K C commented on HI-234 Re: Hiera should be able to include external files within the YAML/JSON hierarchy. +1 to this. I was surprised there's currently no way to specify a directory and/or includes. I'm just getting restarted with Puppet and am new to Hiera, but I can foresee some data files, such as 'common.yaml', becoming fairly large and unwieldy. I'd really like to isolate the settings for each module/service/etc. to its own file. For example: |-- nodes | |-- node1 | | `-- httpd.yaml | `-- node2 | `-- mysql.yaml | ... `-- common |-- autofs.yaml |-- ntp.yaml |-- ssh.yaml
Jira (HI-234) Hiera should be able to include external files within the YAML/JSON hierarchy.
Title: Message Title Henrik Lindberg commented on HI-234 Re: Hiera should be able to include external files within the YAML/JSON hierarchy. I think it will fit in nicely with the option in lookup to list several paths. Then there are lookup options (per key) to control what happens. With multiple files, the priority lookup order will be based on the ascii sort order of paths. 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-234) Hiera should be able to include external files within the YAML/JSON hierarchy.
Title: Message Title Trevor Vaughan commented on HI-234 Re: Hiera should be able to include external files within the YAML/JSON hierarchy. Henrik Lindberg I'd be happy to wait for `lookup` to finalize for this feature. I would really like to move to it prior to the end of the year, but I'm a bit gun-shy of the warnings about things breaking/changing in the way it works. When this was filed, Hiera was all that existed so it makes sense to move it to the new hotness. I'm OK with either the directory recursion or globbing but I would much prefer globbing since that will allow me to be very precise in what I want to include. In terms of conflicts, since you could include multiple files with the same mappings, I would think that you would be given the option to 'fail', 'override', or 'merge'. Fail -> Conflict fails the lookup Override -> Last one included (alphabetically) wins Merge -> Merge hashes, Override everything else That would be really nice (and of course provide a lot of room to shoot yourself in the foot) but I think that it would eliminate some of the existing Hiera backends that make for untraceable data sources. 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-234) Hiera should be able to include external files within the YAML/JSON hierarchy.
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-234 Hiera should be able to include external files within the YAML/JSON hierarchy. Change By: Henrik Lindberg Team: Puppet Developer Support 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-234) Hiera should be able to include external files within the YAML/JSON hierarchy.
Title: Message Title Henrik Lindberg commented on HI-234 Re: Hiera should be able to include external files within the YAML/JSON hierarchy. This is opens up for yet additional issues that needs to be solved - the order in which the files are processed, if they should be merged or not etc. We have much better facilities to deal with this in the support for lookup. I can imagine supporting globbing given paths (expanding them, while not allowing certain patterns like .. since that is a security issue) and then searching through them in ascii sorted order. We could also, like we do for the feature that allows a site manifest to be a directory of files (recursively), simply expand a directory reference to the recursive listing of all paths under that directory in ascii order (i.e. no globbing). Doing this for hiera (the project) is not something we want to do since handling of paths is completely different. For lookup this is totally doable. It will also be very easy to expand what is provided out of the box with any such search scheme with what we are planning for lookup in Puppet 4.8.0. I would like to repurpose this ticket (I don't see this ever happening for hiera the project) to be for lookup - that is unless there are wild protests against this. 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-234) Hiera should be able to include external files within the YAML/JSON hierarchy.
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-234
Hiera should be able to include external files within the YAML/JSON hierarchy.
Change By:
Henrik Lindberg
The crux of this issue is that I would like to be able to separate my files into more logical blocks when using the YAML or JSON configurations.For instance:*hiera.yaml* {code} ---:backends: - yaml:hierarchy: - defaults:yaml: :datadir: /var/lib/hiera {code} In /var/lib/hiera, I would like to be able to place a directory 'defaults' and have hiera load everything under that directory.Such as: {code} defaults/thing1.yamldefaults/thing2.yaml {code} The syntax change that I would like to see for this is to append a trailing '/' to the hierarchy statement to indicate that the directory should be parsed.Example: {code} :hierarchy: - defaults/ {code} If this is not doable, then allowing for a universal ':hiera_include:' option that allows for file chaining would work well (if not better).In this case, defaults.yaml could have: {code} ---:hiera_include: things/* {code} This would include all YAML files under the /var/lib/hiera/things directory.
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 (HI-234) Hiera should be able to include external files within the YAML/JSON hierarchy.
Title: Message Title Trevor Vaughan commented on HI-234 Re: Hiera should be able to include external files within the YAML/JSON hierarchy. Any thoughts on this? I still think that it would be very nice to 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 (HI-234) Hiera should be able to include external files within the YAML/JSON hierarchy.
Title: Message Title redmine.exporter created an issue Hiera / HI-234 Hiera should be able to include external files within the YAML/JSON hierarchy. Issue Type: New Feature Assignee: Unassigned Created: 14/Apr/14 4:20 AM Labels: redmine Priority: Normal Reporter: redmine.exporter The crux of this issue is that I would like to be able to separate my files into more logical blocks when using the YAML or JSON configurations. For instance: hiera.yaml pre — :backends: yaml :hierarchy: defaults :yaml: :datadir: /var/lib/hiera /pre In /var/lib/hiera, I would like to be able to place a directory 'defaults' and have hiera load everything under that directory. Such as: defaults/thing1.yaml defaults/thing2.yaml The syntax change that I would like to see for this is to append a trailing '/' to the hierarchy statement to indicate that the directory should be parsed. Example: pre :hierarchy:
