Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-9741

Chocolatey: Document difference between FOSS and C4B for managing uninstallations outside of Chocolatey/Puppet

    XMLWordPrintable

    Details

    • Template:
      MODULES Bug Template
    • Team:
      Modules
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: 4.0.0
      Puppet Version: 6.7.2
      OS Name/Version: Windows 10 1903

      Desired Behavior: When I uninstall a package manually that was installed via puppet-chocolatey, I'd expect that puppet-chocolatey picks up on this and reinstalls it on the next run.

      Actual Behavior:

      When I uninstall a package manually that was installed via puppet-chocolatey and I re-run puppet, puppet says everything is fine - even though the package is no longer installed.

      I'm seeing this issue with the following puppet code:

      include chocolatey
       
      package { 'vscode':
          ensure   => installed,
          provider => 'chocolatey',
      }
      

      Now, when I (accidentally) uninstall Visual Studio Code through Windows' Settings -> Apps and re-run puppet, puppet won't reinstall VSCode.

      I'm guessing this is because when manually uninstalling VSCode, it remains "registered" in Chocolatey (i.e. choco list --local-only).

      While I understand that you shouldn't manually uninstall packages that were installed via Chocolatey, I still think the current behavior breaks the promise (expected behavior) of package in Puppet - in that one would expect that package re-installs uninstalled packages.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              skrysmanski Sebastian Krysmanski
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support