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

new parameter "allow_virtual"

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: PUP 3.6.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
    • UX Priority:
      Critical

      Description

      So, this whole "allow_virtual" new parameter has been extremely frustrating.

      We use puppet to manage package updates, i.e. package

      {'puppet': ensure=>latest}

      Therefore, we added Package

      {allow_virtual=>false}

      in order to remove the extraneous warning, of which because its in RED, our customers think something broke.

      Then, since not all of the puppet agent's were running 3.6.x at that time, they broke because allow_virtual is a new parameter, of which your changing the default to, when it didn't exist.

      The entire way this allow_virtual was handled has been a severe pain. It would of been much nicer if you had added the default allow_virtual=>false to maintain existing functionality, since according to semantic versioning you can add features but not break existing environments.

      Then in Puppet 4.x you change the default of allow_virtual=>true when your customers are expecting breaking changes.

      Thank you for successfully introducing non-backwards compatible changes into your stable releases.

      As for the reason I'm creating an issue, is that I would really appreciate reverting the allow_virtual "warning" and planned deprecation until 4.x.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kylo Kylo Ginsberg
                Reporter:
                ruckc Curtis Ruck
                QA Contact:
                Kurt Wall
              • Votes:
                1 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support