Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-7281

Add support for default options in hiera.yaml v 5

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.10.0
    • Component/s: Docs
    • Labels:
    • Template:
    • Epic Link:
    • Team:
      Puppet Developer Experience
    • Story Points:
      1
    • Sprint:
      PDE 2017-03-22, PDE 2017-04-05
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      It is now possible to set {{options}} under {{defaults}} in a {{hiera.yaml}} version 5 configuration. Those options apply to all entries in the hiera.yaml configuration that does not have an {{options}} entry. This reduces the amount of copies of the same set of options when a configuration in majority consists of the same type of data provider with the same options. Earlier, an attempt to set {{options}} under {{defaults}} would result in an error.
      Show
      It is now possible to set {{options}} under {{defaults}} in a {{hiera.yaml}} version 5 configuration. Those options apply to all entries in the hiera.yaml configuration that does not have an {{options}} entry. This reduces the amount of copies of the same set of options when a configuration in majority consists of the same type of data provider with the same options. Earlier, an attempt to set {{options}} under {{defaults}} would result in an error.
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      covered by unit tests

      Description

      When a hiera.yaml (version 5) contains heterogenous entries where only the path differs, and the backend (for example eyaml_lookup_key) requires options it becomes a chore having to specify the same options for each and every entry.

      It would be great to be able to add those as default options under the defaults key.

      This would work such that the defaults/options apply to all entries that does not specify options. If an entry does not want those it must specify an empty options hash. If an entry specifies options it overrides (completely) anything that is set in defaults/options(specifically: the options does not merge).

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            henrik.lindberg Henrik Lindberg
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support