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

the 'site' keyword cannot be used as an attribute name when app_management is on

    Details

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

      it should be possible to use $site as a parameter name in a defined resource and set the value of this parameter in a resource expression.

      Show
      it should be possible to use $site as a parameter name in a defined resource and set the value of this parameter in a resource expression.
    • Team:
      Puppet Developer Experience
    • Story Points:
      1
    • Sprint:
      PDS 2016-11-30
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      It was not possible to use the name '$site' as the name of a parameter for a user defined type or class as this made it impossible to set that value when application_management setting was true.
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      covered well by parser unit tests

      Description

      The attribute name 'site' cannot be used as an attribute name when app_management is turned on. It works when app_management is turned off.

      This is because the grammar does not list 'SITE' as a keyword, while handling the 'SITE_R' (app managment is off) token.

      This affects some existing modules as they cannot be used with application managment (or PE where app_management is on by default).

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support