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

Long form Resource Type reference fools "future parser" this is an override

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 3.7.0
    • Component/s: Compiler
    • Labels:
      None
    • Template:
    • Story Points:
      3
    • Sprint:
      2014-07-23, 2014-08-06, 2014-08-20

      Description

      When setting defaults for a resource type R, the short form works:

      R { attr => value }
      

      but not the long form:

      Resource[R] { attr => value }
      Resource['r'] { attr => value }
      

      This problem is due to the static transformation of a resource expression
      since the two forms (override and default) have different rules than a regular resource expression.

      Ideally I would like to only have one form and require that defaults have a title of literal default, and that overrides specify the title of the resource that is being overridden. This would alleviate much grammar pain.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support