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

Make the new lookup logic understand Hiera v3 configurations

    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

      That a global hiera 3 configuration continues to work as it does now, albeit controlled by the new lookup logic. The following must be asserted:

      • yaml and json backends will be automatically rerouted to data_hash functions.
      • other backends will be rerouted to a function that calls existing Hiera 3 backends.
      • merge_behavior and deep_merge options found in the configuration are considered.
      • the scope used for interpolation is a Hiera v3 scope (provides calling_class, calling_class_path, calling_module, and module_name).
      • the lookup explainer outputs detailed information about global lookups.
      Show
      That a global hiera 3 configuration continues to work as it does now, albeit controlled by the new lookup logic. The following must be asserted: yaml and json backends will be automatically rerouted to data_hash functions. other backends will be rerouted to a function that calls existing Hiera 3 backends. merge_behavior and deep_merge options found in the configuration are considered. the scope used for interpolation is a Hiera v3 scope (provides calling_class , calling_class_path , calling_module , and module_name ). covered in PUP-7018 the lookup explainer outputs detailed information about global lookups.
    • Team:
      Puppet Developer Experience
    • Story Points:
      3
    • Sprint:
      PDE 2016-12-14, PDE 2017-01-11, PDE 2017-01-25
    • Release Notes:
      Not Needed
    • Release Notes Summary:
      This is part of a major feature that needs to be release noted separately with references to documentation. The notes would otherwise be swamped with details about hiera 5.
    • QA Risk Assessment:
      Automate
    • QA Risk Assessment Reason:
      mostly covered by units. needs simple acceptance to ensure v3 config is picked up, and yaml/json datafiles used

      Description

      In order to provide a smooth migration from Hiera 3 and incorporate a global data provider, the new lookup logic must be made to understand the Hiera 3 configuration format.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                thomas.hallgren Thomas Hallgren
                QA Contact:
                Eric Thompson
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support