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

a hiera.yaml v3 in the root of an env should be under control of --strict

    Details

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

      --strict controls if a hiera.yaml v3 in an environment root leads to error or warning.

      Show
      --strict controls if a hiera.yaml v3 in an environment root leads to error or warning.
    • Team:
      Puppet Developer Experience
    • Story Points:
      1
    • Sprint:
      PDE 2017-02-08
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Having a hiera.yaml (version 3) in the root of an environment led to a hard error since hiera 5 requires that such a file has format 5 for it to be used with the new features in hiera.
      This is now changed so that a version 3 file is ignored and a warning is issued if --strict=warning, and an error is raised only if --strict==error.
      Show
      Having a hiera.yaml (version 3) in the root of an environment led to a hard error since hiera 5 requires that such a file has format 5 for it to be used with the new features in hiera. This is now changed so that a version 3 file is ignored and a warning is issued if --strict=warning, and an error is raised only if --strict==error.
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      covered by unit tests

      Description

      Many people use a pattern of having a hiera.yaml (v3) in the root of their control repo for the purpose of symlinking it to the global hiera.yaml location setting path.

      Puppet 4.9.0 takes a hiera.yaml in an environment root as an error if the file is of version 3.
      This means that users upgrading to puppet 4.9.0 may have a large number of environments to clean up before they can run puppet 4.9.0.

      We should fix this problem by letting the --strict flag control the behavior. When it is set to error it should behave as it is currently doing in 4.9.0. When set to warning it should log a warning, and continue as if the file was not there.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                henrik.lindberg Henrik Lindberg
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: