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

Title: Message Title

PUP-4485

After lots of discussions and back and forth on this. I think this is the best:

---

:version: 4

:hierarchy:

  - { name: 'yaml1'

      backend: yaml,

      datadir: 'some path',

      paths:

      - "path"

      - "path"

  - { name: 'yaml2'

       backend: yaml,

       datadir: 'some other path',

       path: "a single path"

  - { name: 'yaml3',

       backend: yaml,

       datadir: "some path",

       paths:

         - "path"

         - "path"

  - { name:  'json3',

       backend: json,

       datadir: "some path"

       paths:

         - "path"

         - "path"

:datadir: 'default datadir path if missing in other entries'

Also:

the default default datadir is <root>/data
a relative datadir path is relative to <root>
<root> is the root of an environment, or a module respectively
relative path are relative to the effective datadir for that entry
absolute paths are not allowed in datadir or in paths for an environment or a module (they only make sense for a global-across-all-environments)
validation of the above rules is a bit tricky because 'datadir' and 'paths' are really generic arguments to a provider - i.e. they may be opaque URIs - thus each backend must be able to validate its configuration and know if it is used for a module, environment (and later global).

Add Comment

This message was sent by Atlassian JIRA

--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Reply via email to