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

Deprecate inexact resource reference matches

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.5.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      2
    • Sprint:
      Language 2016-03-23

      Description

      As described in PUP-5659 it is currently allowed to make references to resources that are inexact because they are not validated, and at runtime on the agent they may be references to the same resource . e.g. File[/tmp/foo/] and File[/tmp/foo] is considered to be the same resource.

      This is impossible to know on the Catalog Compilation side. Therefore this should not be allowed as it creates a far worse problem of not being able to validate that resources do exists in the catalog at compile time.

      This can be implemented as a warning in 4.x after having performed the validation that will be standard in 5.0.0.

      UPDATE


      This was implemented as a catalog validation after all defaults, collectors etc. have run. A warning of error is issued if --strict is set to warning or error. When strict is set to off, the behavior is as before this was added. When strict is set to warning, it is possible to suppress warnings by adding undefined_resources to the setting disable_warnings. When warning, the warning will only be made once per missing resource (irrespective of the same resource being referenced from multiple locations, and in different meta parameters).

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support