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

Make attempt to export or virtualize a class an error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 7.0.0
    • Component/s: None
    • Template:
      PUP Bug Template
    • Team:
      Coremunity
    • Sprint:
      Platform Core KANBAN
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Previously puppet would warn or error if it encountered a virtual
      class (indicated by @class) or an exported class (indicated by @@class)
      based on the Puppet[:strict] setting. By default, puppet would warn, yet
      include resources from the virtual class in the catalog. This commit makes puppet always error on virtual and exported classes.
      Show
      Previously puppet would warn or error if it encountered a virtual class (indicated by @class) or an exported class (indicated by @@class) based on the Puppet[:strict] setting. By default, puppet would warn, yet include resources from the virtual class in the catalog. This commit makes puppet always error on virtual and exported classes.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Currently (under to control of --strict), it is a warning or an error to attempt to use @class or @@class in a resource expression or a create_resources call.

      In Puppet 7.0.0 this should always be an error.

      Note the configuration for this is done twice, once for the static validation, and once for the runtime. The checker4_0 has the static validation logic, and the runtime check is in the `create_resources`. See PUP-1606 where the warnings were added.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              josh Josh Cooper
              Reporter:
              henrik.lindberg Henrik Lindberg
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support