Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title adrian created an issue Hiera / HI-120 Allow wildcards in hierarchy Issue Type: Improvement Assignee: Eric Sorenson Created: 23/Dec/13 8:11 AM Priority: Normal Reporter: adrian It would be great to allow wildcards when defining the hierarchy in hiera.yaml. Example: In want to have a directory tree like this: hiera/project-name/common.json hiera/project-name/webservers.json But the number of projects is variable. So I want to define a hiera.yaml like: :backends: json :json: :datadir: /tmp/pruebas-hiera/hiera :hierarchy: "*/webservers" "*/common" In that files, for instance, will be the users that some node have to create. Add Comment
Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title adrian updated an issue Hiera / HI-120 Allow wildcards in hierarchy Change By: adrian It would be great to allow wildcards (*) when defining the hierarchy in hiera.yaml.Example:In want to have a directory tree like this:hiera/project-name/common.jsonhiera/project-name/webservers.jsonBut the number of projects is variable.So I want to define a hiera.yaml like::backends: - json:json: :datadir: /tmp/pruebas-hiera/hiera:hierarchy: - "*/webservers" - "*/common"In that files, for instance, will be the users that some node have to create. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title adrian commented on an issue Re: Allow wildcards in hierarchy I have created a pull request: https://github.com/puppetlabs/hiera/pull/169 Add Comment Hiera / HI-120 Allow wildcards in hierarchy It would be great to allow wildcards when defining the hierarchy in hiera.yaml. Example: In want to have a directory tree like this: hiera/project-name/common.json hiera/project-name/webservers.json But the number of projects is variable. So I want to define a hiera.yaml like: :backends: - json :json: :datadir: /tmp/pruebas-hiera/hie... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title Reinhard Vicinus commented on an issue Re: Allow wildcards in hierarchy I'm only another puppet/hiera user who stumbled upon your feature request and have no standing with puppetlabs whatsoever. But there are some problems I see with your request: 1.) Puppet multi master setups can generate different catalogs for the same node, because Dir.glob returns the files in an order dependent on the system it is run on. As far as i can tell, the result of Dir.glob isn't sorted in any way in your pull request, so on different masters the order can be different and therefore the hierachy. 2.) This change breaks all other hiera backends (yaml, etc) as far as I can tell. 3.) I can see only one valid use case for this behavior: To realize two or more independent projects on one node. I concede that this isn't possible at the moment, as far as I know, because it isn't possible to redeclare variables in puppet (with the exception, if all projects are configured in independent puppet modules the special variable %calling_module can be used in the hierarchy). I wrote my own puppet hiera connector to solve (among others) this problem. I considered your approach also, but discarded it because as the count of projects increase the performance will get terrible (for every hiera lookup up every time all projects have to be questioned). Also there is no hierarchy between independent projects, why create one? Add Comment Hiera / HI-120 Allow wildcards in hierarchy It would be great to allow wildcards when defining the hierarchy in hiera.yaml. Example: In want to have a directory tree like this: hiera/project-name/common.json hiera/project-name/webservers.json But the number of projects is variable. So I want to define a hiera.yaml like: :backends: - json :json: :datadir: /tmp/pruebas-hiera/hie...
Jira (HI-120) Allow wildcards in hierarchy
Title: Message Title adrian commented on an issue Re: Allow wildcards in hierarchy Yeah, you are right. 1. could be easy to fix 2. fixing yaml could be easy, but could be dozens of custom backends that will get broken 3. My problem is I want projects to define their own hostgroups, host templates, etc, and one node, Icinga/Nagios host, to implement all of them. But sure, reading and parsing dozens of json files in each lookup is definitely a bad idea. I am thinking moving to some other backend as mysql or redis. Thanks! Add Comment Hiera / HI-120 Allow wildcards in hierarchy It would be great to allow wildcards when defining the hierarchy in hiera.yaml. Example: In want to have a directory tree like this: hiera/project-name/common.json hiera/project-name/webservers.json But the number of projects is variable. So I want to define a hiera.yaml like: :backends: - json :json: :datadir: /tmp/pruebas-hiera/hie... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you a
