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

Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.9.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

      A custom Hiera 3 backend can be delcared in a hiera.yaml version 5.

      Show
      A custom Hiera 3 backend can be delcared in a hiera.yaml version 5.
    • Team:
      Puppet Developer Experience
    • Story Points:
      1
    • Sprint:
      PDE 2017-01-11, PDE 2017-01-25, PDE 2017-02-08, PDE 2017-02-22
    • Release Notes:
      Not Needed
    • Release Notes Summary:
      Part of the new hiera 5 feature.
    • QA Risk Assessment:
      Automate
    • QA Risk Assessment Reason:
      partially covered by unit tests, needs acceptance. high risk for migrations

      Description

      It is currently only possible to migrate to a global Hiera version 5 configuration when the current version 3 configuration declares backends that are supported in version 5 (currently yaml, json, and hocon). There is no way to add a custom hiera version 3 backend.

      In order to always enable a migration of the configuration, it should be possible for a Hiera 5 configuration to also declare a reference to a custom Hiera 3 backend. A new entry hiera3_backend should be added that is mutually exclusive to the currently known function types data_hash, lookup_key, and data_dig.

      The ability to declare a hiera 3 backend in a named Hiera version 5 hierarchy entry will also make it possible to identify and override entries declared in a bottom_hierarchy (a planned future addition) and removes the need to introduce the bottom_hierarchy in version 3.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              thomas.hallgren Thomas Hallgren
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support