Jira (PUP-4485) Add a 'hiera' data provider

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg created an issue   Puppet / PUP-4485 Add a 'hiera' data provider Issue Type: Bug Assignee: Unassigned Created: 2015/04/29 6:04 AM Fix Versions: PUP 4.2.0 Priority: Normal Reporter: Henrik Lindberg Add DataProvider subtypes for environment and module that is hiera like. This data type should read a 'hiera.yaml' from <environment-root>/hiera.yaml, or <module-root>/hiera.yaml, respectively. The hiera.yaml is a new version of the configuration file. It should include a version entry. If the version is missing or set to a value < 3, then the current ("old") format is read and the semantics are retained (i.e. search with cartesian product of backends/hierarchy and only one data location per backend) If the version is set, it must be 3 (or an error is raised) The logger entry is not supported in either version - logging is always done using the Puppet logger If an environment is using the hiera data provider and has no hiera.yaml file a default configuration is used comparable to the current default configuration file but with a data dir referencing <environment>/data or <moduleroot>/data respectively for the two kinds of providers. New config file format: — The new config file format basically merges the backend and hierarchy settings into one common structure. --- :version: 3 :hierarchy: - { backend: {type: yaml, name: 'yaml1', datadir: 'some path'} paths: - "path" - "path" } - { backend: {type: yaml, name: 'yaml2', datadir: 'some other path'} path: "a single path" } - { backend: - { type: yaml, name: 'yaml3'} - { type: json, name: 'json3' } datadir: "common data dir for all backends in this entry" paths: - "path" - "path" } :datadir: 'default datadir path if missing in other entries' This example configuration file has three entries in the hierarchy. The entries are searched from top to bottom. An entry may have one or more backends. If multiple backends are specified, they are searched in order using a common set of paths. If they have their own paths, those are searched before the common set of paths. A datadir may be specified per backend, a hierarchy entry, or for all. This acts as a default if a more specific entry does not specify the datadir. The name of an entry is used for human "explain" output as it is not enough to identify a backend by type alone. The backends are not hiera backends as specified for hiera <= 2.0, they are data providers. Each instantiated data provider gets the datadir and the paths as arguments. This makes it possible to use other kinds of providers than file based - where datadir and paths may be irrelevant, or bad names. As an example, it is of value to be able to use a function - it could default to the data function, but other function names could be used as well and searched just like a file path is searched. (Some elaboration and decision is needed on the mechanism/naming). Cacheing and lifecycle: Since the first implementation is only for modules and environments, the data should be cached for each compilation (i.e. associated with the catalog). Data files are not watched. Validation and Schema: There should be a schema for the configuration file, and it should be validated when loaded. This is made difficult if support is retained for the old format. Alternatively we supply a utility that converts hiera.yaml version < 3 to version 3. This should be a very simple transformation that also helps user untangle/select what they really want (i.e. pruning useless combinations that are created by the current cartesian product approach). To be elaborated on and decided Add Comment   This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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/d/optout.