Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the packages and push them to a repository
  Download Packages

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the packages:
  Download Packages
- Follow manual internalization instructions
Package Internalizer (C4B)
- Run: (additional options)
- For package and dependencies run:
- Automate package internalization

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###

#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"

#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072

#### We use this variable for future REST calls.
$RequestArguments = @{
    UseBasicParsing = $true
}

## 2. TOP LEVEL VARIABLES ##

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
#     "username",
#     ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.2.2.2.nupkg"

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    $TempDirectory = Join-Path $env:Temp "chocolateyInstall"
    if (-not (Test-Path $TempDirectory -PathType Container)) {
        $null = New-Item -Path $TempDirectory -ItemType Directory
    }
    $DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
    Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments

    #### Extract the Nupkg, and run the chocolateyInstall script
    if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
        Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
    } else {
        # PowerShell versions <4.0 do not have this function available
        try {
            $shellApplication = New-Object -ComObject Shell.Application
            $zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
            $destinationFolder = $shellApplication.NameSpace($TempDirectory)
            $destinationFolder.CopyHere($zipPackage.Items(), 0x10)
        } catch {
            Write-Warning "Unable to unzip package using built-in compression."
            throw $_
        }
    }

    & $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}

if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    refreshenv
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums

### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400

#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress

### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
    if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
        choco source remove -n $_.Name
    }
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco source disable --name chocolatey.licensed
} else {
    Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
    Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
    choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
    choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
    if ($ChocolateyCentralManagementClientSalt) {
        choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
    }
    if ($ChocolateyCentralManagementServiceSalt) {
        choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
    }
    choco feature enable --name useChocolateyCentralManagement
    choco feature enable --name useChocolateyCentralManagementDeployments
}

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
    nuget_repository_url: INTERNAL REPO URL

### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
#    nuget_repository_username: username
#    nuget_repository_password: password

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#    chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService

#### ii. If using a Client Salt, add it here
#    chocolatey_central_management_client_salt: clientsalt

#### iii. If using a Service Salt, add it here
#    chocolatey_central_management_service_salt: servicesalt

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

  tasks:
  - name: Install chocolatey
    win_chocolatey:
      name: chocolatey
      source: ""{{ nuget_repository_url }}""
      # source_username: ""{{ nuget_repository_username }}""
      # source_password: ""{{ nuget_repository_password }}""

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#   - name: Enable FIPS compliance
#     win_chocolatey_feature:
#       name: useFipsCompliantChecksums
#       state: enabled

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
  - name: Set the cache location
    win_chocolatey_config:
      name: cacheLocation
      state: present
      value: C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
  - name: Set the command execution timeout
    win_chocolatey_config:
      name: commandExecutionTimeoutSeconds
      state: present
      value: 14400

#### Turn off download progress when running choco through integrations
  - name: Disable showing download progress
    win_chocolatey_feature:
      name: showDownloadProgress
      state: disabled

### c. Sources ###
#### Remove the default community package repository source
  - name: Remove Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey
      state: absent

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
  - name: Add Internal Repository
    win_chocolatey_source:
      name: ChocolateyInternal
      state: present
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}
      priority: 1

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
  - name: Upgrade Chocolatey
    win_chocolatey:
      name: chocolatey
      state: latest

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
  - name: Install Chocolatey License
    win_chocolatey:
      name: chocolatey-license
      source: ChocolateyInternal
      state: latest

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
  - name: Disable Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey.licensed
      state: disabled

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
  - name: Install Chocolatey Extension
    win_chocolatey:
      name: chocolatey.extension
      source: ChocolateyInternal
      state: latest

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
  - name: Hide not-elevated warnings
    win_chocolatey_feature:
      name: showNonElevatedWarnings
      state: disabled

  - name: Use background mode for self-service
    win_chocolatey_feature:
      name: useBackgroundService
      state: enabled

  - name: Use background service for non-admins
    win_chocolatey_feature:
      name: useBackgroundServiceWithNonAdministratorsOnly
      state: enabled

  - name: Allow background uninstallation for user installs
    win_chocolatey_feature:
      name: allowBackgroundServiceUninstallsFromUserInstallsOnly
      state: enabled

  - name: Set allowed background service commands
    win_chocolatey_config:
      name: backgroundServiceAllowedCommands
      state: present
      value: install,upgrade,uninstall

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
  - name: Install Chocolatey Agent
    when: chocolatey_central_management_url is defined
    win_chocolatey:
      name: chocolatey-agent
      source: ChocolateyInternal
      state: latest

  - name: Set the Central Management Service URL
    when: chocolatey_central_management_url is defined
    win_chocolatey_config:
      name: CentralManagementServiceUrl
      state: present
      value: {{ chocolatey_central_management_url }}

  - name: Set the Central Management Client Salt
    when: chocolatey_central_management_client_salt is defined
    win_chocolatey_config:
      name: centralManagementClientCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_client_salt }}

  - name: Set the Central Management Service Salt
    when: chocolatey_central_management_service_salt is defined
    win_chocolatey_config:
      name: centralManagementServiceCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_service_salt }}

  - name: Use Central Management
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagement
      state: enabled

  - name: Use Central Management Deployments
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagementDeployments
      state: enabled

See docs at https://docs.chef.io/resource_chocolatey_package.html.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"

## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.2.2.2.nupkg",

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
  'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
#   action :enable
# end

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
  value 'C:\ProgramData\chocolatey\cache'
end

#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
  value '14400'
end

#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
  action :disable
end

### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
  action :remove
end

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
  source "#{NugetRepositoryUrl}"
  priority 1
  action   :add
end

execute 'ChocolateyInternal' do
  command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
  only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
  action :upgrade
  source "#{NugetRepositoryUrl}"
end

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
  action :install
  source "#{NugetRepositoryUrl}"
end

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
  action            :disable
end

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
  action     install
  source     "#{NugetRepositoryUrl}"
end

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
  action :disable
end

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

chocolatey_config 'backgroundServiceAllowedCommands' do
  value 'install,upgrade,uninstall'
end

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
  action     install
  source     "#{NugetRepositoryUrl}"
  # user       "#{NugetRepositoryUsername}"
  # password   "#{NugetRepositoryPassword}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'CentralManagementServiceUrl' do
  value  "#{ChocolateyCentralManagementUrl}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementClientSalt}"
  only_if { ChocolateyCentralManagementClientSalt != nil }
end

chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementServiceSalt}"
  only_if { ChocolateyCentralManagementServiceSalt != nil }
end

chocolatey_feature 'useChocolateyCentralManagement' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_feature 'useChocolateyCentralManagementDeployments' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

If Applicable - Chocolatey Configuration/Installation


#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
    $null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
    }
    Install-Module -Name cChoco
    if ($PSGallery.InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
    }
}

#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1

Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
    param(
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
        $NugetRepositoryUrl      = "INTERNAL REPO URL",

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
        $ChocolateyNupkgUrl      = "INTERNAL REPO URL/package/chocolatey.2.2.2.nupkg",

### c. Internal Repository Credential ###
#### If required, add the repository access credential here
#        $NugetRepositoryCredential = [PSCredential]::new(
#            "username",
#            ("password" | ConvertTo-SecureString -AsPlainText -Force)
#        ),

### d. Install.ps1 URL
#### The path to the hosted install script:
        $ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"

### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#        $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",

#### ii. If using a Client Salt, add it here
#        $ChocolateyCentralManagementClientSalt = "clientsalt",

#### iii. If using a Service Salt, add it here
#        $ChocolateyCentralManagementServiceSalt = "servicesalt"
    )
    Import-DscResource -ModuleName PSDesiredStateConfiguration
    Import-DscResource -ModuleName cChoco

    Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
        Environment chocoDownloadUrl {
            Name  = "chocolateyDownloadUrl"
            Value = $ChocolateyNupkgUrl
        }

        cChocoInstaller installChocolatey {
            DependsOn = "[Environment]chocoDownloadUrl"
            InstallDir = Join-Path $env:ProgramData "chocolatey"
            ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
        }

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#        cChocoFeature featureFipsCompliance {
#            FeatureName = "useFipsCompliantChecksums"
#        }

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
        cChocoConfig cacheLocation {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "cacheLocation"
            Value      = "C:\ProgramData\chocolatey\cache"
        }

#### Increase timeout to at least 4 hours
        cChocoConfig commandExecutionTimeoutSeconds {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "commandExecutionTimeoutSeconds"
            Value      = 14400
        }

#### Turn off download progress when running choco through integrations
        cChocoFeature showDownloadProgress {
            DependsOn   = "[cChocoInstaller]installChocolatey"
            FeatureName = "showDownloadProgress"
            Ensure      = "Absent"
        }

### c. Sources ###
#### Remove the default community package repository source
        cChocoSource removeCommunityRepository {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name       = "chocolatey"
            Ensure     = "Absent"
        }

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
        cChocoSource addInternalSource {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name        = "ChocolateyInternal"
            Source      = $NugetRepositoryUrl
            Credentials = $NugetRepositoryCredential
            Priority    = 1
        }

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
        cChocoPackageInstaller updateChocolatey {
            DependsOn   = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
            Name        = "chocolatey"
            AutoUpgrade = $true
        }

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
        cChocoPackageInstaller chocolateyLicense {
            DependsOn = "[cChocoPackageInstaller]updateChocolatey"
            Name      = "chocolatey-license"
        }

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
        Script disableLicensedSource {
            DependsOn  = "[cChocoPackageInstaller]chocolateyLicense"
            GetScript  = {
                $Source = choco source list --limitoutput | `
                    ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
                    Where-Object Name -eq "chocolatey.licensed"

                return @{
                    Result = if ($Source) {
                        [bool]::Parse($Source.Disabled)
                    } else {
                        Write-Warning "Source 'chocolatey.licensed' was not present."
                        $true  # Source does not need disabling
                    }
                }
            }
            SetScript  = {
                $null = choco source disable --name "chocolatey.licensed"
            }
            TestScript = {
                $State = [ScriptBlock]::Create($GetScript).Invoke()
                return $State.Result
            }
        }

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
        cChocoPackageInstaller chocolateyLicensedExtension {
            DependsOn = "[Script]disableLicensedSource"
            Name      = "chocolatey.extension"
        }

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
        cChocoFeature hideElevatedWarnings {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "showNonElevatedWarnings"
            Ensure      = "Absent"
        }

        cChocoFeature useBackgroundService {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundService"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceWithNonAdmins {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
            Ensure      = "Present"
        }

        cChocoConfig allowedBackgroundServiceCommands {
            DependsOn   = "[cChocoFeature]useBackgroundService"
            ConfigName = "backgroundServiceAllowedCommands"
            Value       = "install,upgrade,uninstall"
        }

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
        if ($ChocolateyCentralManagementUrl) {
            cChocoPackageInstaller chocolateyAgent {
                DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
                Name      = "chocolatey-agent"
            }

            cChocoConfig centralManagementServiceUrl {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                ConfigName = "CentralManagementServiceUrl"
                Value       = $ChocolateyCentralManagementUrl
            }

            if ($ChocolateyCentralManagementClientSalt) {
                cChocoConfig centralManagementClientSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementClientSalt
                }
            }

            if ($ChocolateyCentralManagementServiceSalt) {
                cChocoConfig centralManagementServiceSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementServiceSalt
                }
            }

            cChocoFeature useCentralManagement {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagement"
                Ensure      = "Present"
            }

            cChocoFeature useCentralManagementDeployments {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagementDeployments"
                Ensure      = "Present"
            }
        }
    }
}

# If working this into an existing configuration with a good method for
$ConfigData = @{
    AllNodes = @(
        @{
            NodeName                    = "localhost"
            PSDscAllowPlainTextPassword = $true
        }
    )
}

try {
    Push-Location $env:Temp
    $Config = ChocolateyConfig -ConfigurationData $ConfigData
    Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
    Pop-Location
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
####  See https://forge.puppet.com/puppetlabs/chocolatey


## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.2.2.2.nupkg'

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'

#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'


## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
###  source locations. This is directly to the bare download url for the
###  chocolatey.nupkg, similar to what you see when you browse to
###  https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
  chocolatey_download_url => $_choco_download_url,
  use_7zip                => false,
}


## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations

#chocolateyfeature {'useFipsCompliantChecksums':
#  ensure => enabled,
#}

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
  value => 'C:\ProgramData\chocolatey\cache',
}

#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
  value => '14400',
}

#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
  ensure => disabled,
}

### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
  ensure   => absent,
  location => 'https://community.chocolatey.org/api/v2/',
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
  ensure             => present,
  location           => $_repository_url,
  priority           => 1,
  username           => 'optional',
  password           => 'optional,not ensured',
  bypass_proxy       => true,
  admin_only         => false,
  allow_self_service => false,
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/

package {'chocolatey':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}


## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license

# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
  ensure   => disabled,
  priority => '10',
  user     => 'customer',
  password => '1234',
  require  => Package['chocolatey-license'],
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
  require  => Package['chocolatey-license'],
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
  ensure => disabled,
}

chocolateyfeature {'useBackgroundService':
  ensure => enabled,
}

chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
  ensure => enabled,
}

chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
  ensure => enabled,
}

chocolateyconfig {'backgroundServiceAllowedCommands':
  value => 'install,upgrade,uninstall',
}

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
  package {'chocolatey-agent':
    ensure   => latest,
    provider => chocolatey,
    source   => $_repository_url,
    require  => Package['chocolatey-license'],
  }

  chocolateyconfig {'CentralManagementServiceUrl':
    value   => $_chocolatey_central_management_url,
  }

  if $_chocolatey_central_management_client_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  if $_chocolatey_central_management_service_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  chocolateyfeature {'useChocolateyCentralManagement':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }

  chocolateyfeature {'useChocolateyCentralManagementDeployments':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }
}

Need Help? View our docs or file an issue.

There is already a version of this package in your Script Builder

Current Version	New Version

Downloads:

211,964

Downloads of v 3.114.0:

986

Last Update:

26 Apr 2024

Package Maintainer(s):

Software Author(s):

Pulumi

Tags:

pulumi sdk

Pulumi (Portable)

This is not the latest version of Pulumi (Portable) available.

3.114.0 | Updated: 26 Apr 2024

Downloads:

211,964

Downloads of v 3.114.0:

986

Maintainer(s):

Software Author(s):

Pulumi

Tags:

pulumi sdk

Pulumi (Portable) 3.114.0

This is not the latest version of Pulumi (Portable) available.

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Pulumi (Portable), run the following command from the command line or from PowerShell:

To upgrade Pulumi (Portable), run the following command from the command line or from PowerShell:

To uninstall Pulumi (Portable), run the following command from the command line or from PowerShell:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions

Package Internalizer (C4B)

Run: (additional options)

choco download pulumi --internalize --version=3.114.0 --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

choco push --source="'INTERNAL REPO URL'"

Automate package internalization

3. Copy Your Script

choco upgrade pulumi -y --source="'INTERNAL REPO URL'" --version="'3.114.0'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade pulumi -y --source="'INTERNAL REPO URL'" --version="'3.114.0'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Install pulumi
  win_chocolatey:
    name: pulumi
    version: '3.114.0'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'pulumi' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.114.0'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller pulumi
{
    Name     = "pulumi"
    Version  = "3.114.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'pulumi':
  ensure   => '3.114.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 27 Apr 2024.

Description

Modern Infrastructure as Code

Declare cloud infrastructure using real languages. Enable developers and operators to work better together.

Files

legal\LICENSE.txt


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

legal\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The installer have been downloaded from their official download link listed on <>
and can be verified like this:

1. Download the following installers:
  64-Bit: <https://get.pulumi.com/releases/sdk/pulumi-v3.114.0-windows-x64.zip>
2. You can use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: sha256
  checksum64: 30ED5EE50777554B1F5D0A74E7B96AB31D918DCC640D87A2EE5250DA2D51A149

File 'LICENSE.txt' is obtained from <https://github.com/pulumi/pulumi/blob/master/LICENSE>

tools\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop';

$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  unzipLocation  = $toolsDir
  file64         = "$toolsDir\pulumi-v3.114.0-windows-x64.zip"
  checksumType   = "sha256"
  checksum64     = "30ED5EE50777554B1F5D0A74E7B96AB31D918DCC640D87A2EE5250DA2D51A149"
}

Install-ChocolateyZipPackage  @packageArgs

$bindir = Join-Path -Path $toolsDir -ChildPath "Pulumi\bin"

# create empty sidecar so shimgen ignores them.
Get-ChildItem $bindir\*.exe | ForEach-Object { Set-Content -Value "" -Path "$_.ignore" }

Install-ChocolateyPath $bindir 'Machine'

Update-SessionEnvironment

tools\chocolateyUninstall.ps1

$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$bindir   = Join-Path -Path $toolsDir -ChildPath "Pulumi\bin"

$unPath = Join-Path $toolsDir 'Uninstall-ChocolateyPath.psm1'
Import-Module $unPath
Uninstall-ChocolateyPath $bindir 'Machine'

$pulumiDir = Join-Path -Path $toolsDir -ChildPath "Pulumi"

if (Test-Path $pulumiDir) {
    Remove-Item $pulumiDir -Recurse -Force
}

Update-SessionEnvironment

tools\pulumi-v3.114.0-windows-x64.zip

md5: 95C888614F31D8CCC4D42F2B9986CB0B | sha1: C772494CED90EFF345574ABEBE1FAC65C03D0B9C | sha256: 30ED5EE50777554B1F5D0A74E7B96AB31D918DCC640D87A2EE5250DA2D51A149 | sha512: D612ADC9884221286DDCE821789EBEE3A2891AF082EE607AA531128444BD63BA4C92EBCA511B2E57B85B47D1249FB16CDC577D50AB2BE312D181873F820BC7D5

tools\Uninstall-ChocolateyPath.psm1

function Uninstall-ChocolateyPath {
    param(
        [string] $pathToUninstall,
        [System.EnvironmentVariableTarget] $pathType = [System.EnvironmentVariableTarget]::User
    )
    Write-Debug "Running 'Uninstall-ChocolateyPath' with pathToUninstall:`'$pathToUninstall`'";

    #get the PATH variable
    $envPath = $env:PATH
    #$envPath = [Environment]::GetEnvironmentVariable('Path', $pathType)
    if (!$envPath.ToLower().Contains($pathToUninstall.ToLower())) {
        Write-Host "PATH environment variable does not have $pathToUninstall in it."
        return
    }

    Write-Host "PATH environment variable has $pathToUninstall in it. Removing..."
    $actualPath = [Environment]::GetEnvironmentVariable('Path', $pathType)

    # escape regex metachars, match possible backslash and item separator at eol
    $pathToUninstallRegex = ($pathToUninstall -replace '([\\().])', '\$1') + '\\?(;|$)'

    # remove pathToUninstall from actualPath
    $actualPath = $actualPath -replace "$pathToUninstallRegex", ''

    if ($pathType -eq [System.EnvironmentVariableTarget]::Machine) {
        $psArgs = "[Environment]::SetEnvironmentVariable('Path',`'$actualPath`', `'$pathType`')"
        Start-ChocolateyProcessAsAdmin "$psArgs"
    } else {
        [Environment]::SetEnvironmentVariable('Path', $actualPath, $pathType)
    }

    # remove from path of current powershell session
    $envPSPath = $env:PATH
    $env:Path = $envPSPath -replace "$pathToUninstallRegex", ''
}

Virus Scan Results

pulumi.3.114.0.nupkg (74a5775ca568) - ## / 62
pulumiInstall.zip (30ed5ee50777) - ## / 63
pulumi-language-go.exe (2b9d8e21b097) - ## / 70
pulumi-language-nodejs.exe (374ac4c6e729) - ## / 71
pulumi-language-python.exe (aab19ef0da95) - ## / 71
pulumi.exe (1d68439d55b8) - ## / 70

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version History

Version	Downloads	Last Updated	Status
Pulumi (Portable) 3.116.1	471	Wednesday, May 15, 2024	Approved
Pulumi (Portable) 3.116.0	307	Monday, May 13, 2024	Approved
Pulumi (Portable) 3.115.2	932	Monday, May 6, 2024	Approved
Pulumi (Portable) 3.115.1	44	Monday, May 6, 2024	Approved
Pulumi (Portable) 3.115.0	489	Friday, May 3, 2024	Approved
Pulumi (Portable) 3.114.0	986	Friday, April 26, 2024	Approved
Pulumi (Portable) 3.113.3	1101	Friday, April 19, 2024	Approved
Pulumi (Portable) 3.113.2	114	Friday, April 19, 2024	Approved
Pulumi (Portable) 3.113.1	184	Thursday, April 18, 2024	Approved
Pulumi (Portable) 3.113.0	454	Monday, April 15, 2024	Approved
Pulumi (Portable) 3.112.0	2035	Thursday, March 28, 2024	Approved
Pulumi (Portable) 3.111.1	1606	Saturday, March 16, 2024	Approved
Pulumi (Portable) 3.111.0	76	Friday, March 15, 2024	Approved
Pulumi (Portable) 3.110.0	223	Thursday, March 14, 2024	Approved
Pulumi (Portable) 3.109.0	959	Thursday, March 7, 2024	Approved
Pulumi (Portable) 3.108.1	795	Friday, March 1, 2024	Approved
Pulumi (Portable) 3.108.0	150	Friday, March 1, 2024	Approved
Pulumi (Portable) 3.107.0	1193	Thursday, February 22, 2024	Approved
Pulumi (Portable) 3.106.0	583	Friday, February 16, 2024	Approved
Pulumi (Portable) 3.105.0	1285	Thursday, February 8, 2024	Approved
Pulumi (Portable) 3.104.2	765	Friday, February 2, 2024	Approved
Pulumi (Portable) 3.104.1	98	Thursday, February 1, 2024	Approved
Pulumi (Portable) 3.104.0	147	Wednesday, January 31, 2024	Approved
Pulumi (Portable) 3.103.1	1062	Thursday, January 25, 2024	Approved
Pulumi (Portable) 3.103.0	66	Thursday, January 25, 2024	Approved
Pulumi (Portable) 3.102.0	933	Thursday, January 18, 2024	Approved
Pulumi (Portable) 3.101.1	1218	Wednesday, January 10, 2024	Approved
Pulumi (Portable) 3.101.0	148	Wednesday, January 10, 2024	Approved
Pulumi (Portable) 3.100.0	716	Thursday, January 4, 2024	Approved
Pulumi (Portable) 3.99.0	1673	Thursday, December 21, 2023	Approved
Pulumi (Portable) 3.98.0	254	Tuesday, December 19, 2023	Approved
Pulumi (Portable) 3.97.0	763	Thursday, December 14, 2023	Approved
Pulumi (Portable) 3.96.2	1037	Friday, December 8, 2023	Approved
Pulumi (Portable) 3.96.1	216	Friday, December 8, 2023	Approved
Pulumi (Portable) 3.96.0	76	Thursday, December 7, 2023	Approved
Pulumi (Portable) 3.95.0	992	Friday, December 1, 2023	Approved
Pulumi (Portable) 3.94.2	2000	Friday, November 17, 2023	Approved
Pulumi (Portable) 3.94.1	111	Thursday, November 16, 2023	Approved
Pulumi (Portable) 3.94.0	339	Wednesday, November 15, 2023	Approved
Pulumi (Portable) 3.93.0	751	Friday, November 10, 2023	Approved
Pulumi (Portable) 3.92.0	1323	Friday, November 3, 2023	Approved
Pulumi (Portable) 3.91.1	1073	Saturday, October 28, 2023	Approved
Pulumi (Portable) 3.91.0	352	Thursday, October 26, 2023	Approved
Pulumi (Portable) 3.90.1	270	Tuesday, October 24, 2023	Approved
Pulumi (Portable) 3.90.0	627	Monday, October 23, 2023	Approved
Pulumi (Portable) 3.89.0	1323	Tuesday, October 17, 2023	Approved
Pulumi (Portable) 3.88.1	813	Thursday, October 12, 2023	Approved
Pulumi (Portable) 3.88.0	440	Tuesday, October 10, 2023	Approved
Pulumi (Portable) 3.87.0	486	Friday, October 6, 2023	Approved
Pulumi (Portable) 3.86.0	2273	Tuesday, September 26, 2023	Approved
Pulumi (Portable) 3.85.0	863	Saturday, September 23, 2023	Approved
Pulumi (Portable) 3.84.0	673	Tuesday, September 19, 2023	Approved
Pulumi (Portable) 3.83.0	678	Friday, September 15, 2023	Approved
Pulumi (Portable) 3.82.1	494	Wednesday, September 13, 2023	Approved
Pulumi (Portable) 3.82.0	162	Tuesday, September 12, 2023	Approved
Pulumi (Portable) 3.81.0	736	Thursday, September 7, 2023	Approved
Pulumi (Portable) 3.80.0	799	Friday, September 1, 2023	Approved
Pulumi (Portable) 3.79.0	1057	Saturday, August 26, 2023	Approved
Pulumi (Portable) 3.78.1	2168	Friday, August 11, 2023	Approved
Pulumi (Portable) 3.78.0	261	Thursday, August 10, 2023	Approved
Pulumi (Portable) 3.77.1	810	Saturday, August 5, 2023	Approved
Pulumi (Portable) 3.77.0	59	Friday, August 4, 2023	Approved
Pulumi (Portable) 3.76.1	1255	Wednesday, July 26, 2023	Approved
Pulumi (Portable) 3.76.0	1150	Thursday, July 20, 2023	Approved
Pulumi (Portable) 3.75.0	1295	Wednesday, July 12, 2023	Approved
Pulumi (Portable) 3.74.0	1586	Friday, June 30, 2023	Approved
Pulumi (Portable) 3.73.0	1213	Thursday, June 22, 2023	Approved
Pulumi (Portable) 3.72.2	936	Saturday, June 17, 2023	Approved
Pulumi (Portable) 3.72.1	149	Friday, June 16, 2023	Approved
Pulumi (Portable) 3.72.0	148	Friday, June 16, 2023	Approved
Pulumi (Portable) 3.71.0	542	Tuesday, June 13, 2023	Approved
Pulumi (Portable) 3.70.0	782	Thursday, June 8, 2023	Approved
Pulumi (Portable) 3.69.0	1139	Thursday, June 1, 2023	Approved
Pulumi (Portable) 3.68.0	2171	Friday, May 19, 2023	Approved
Pulumi (Portable) 3.67.1	588	Monday, May 15, 2023	Approved
Pulumi (Portable) 3.67.0	619	Thursday, May 11, 2023	Approved
Pulumi (Portable) 3.66.0	969	Friday, May 5, 2023	Approved
Pulumi (Portable) 3.65.1	1242	Friday, April 28, 2023	Approved
Pulumi (Portable) 3.65.0	387	Wednesday, April 26, 2023	Approved
Pulumi (Portable) 3.64.0	1266	Wednesday, April 19, 2023	Approved
Pulumi (Portable) 3.63.0	724	Friday, April 14, 2023	Approved
Pulumi (Portable) 3.62.0	1264	Thursday, April 6, 2023	Approved
Pulumi (Portable) 3.61.1	102	Thursday, April 6, 2023	Approved
Pulumi (Portable) 3.61.0	622	Monday, April 3, 2023	Approved
Pulumi (Portable) 3.60.1	649	Thursday, March 30, 2023	Approved
Pulumi (Portable) 3.60.0	649	Monday, March 27, 2023	Approved
Pulumi (Portable) 3.59.1	464	Friday, March 24, 2023	Approved
Pulumi (Portable) 3.59.0	512	Thursday, March 23, 2023	Approved
Pulumi (Portable) 3.58.0	738	Friday, March 17, 2023	Approved
Pulumi (Portable) 3.57.1	1338	Thursday, March 9, 2023	Approved
Pulumi (Portable) 3.57.0	171	Thursday, March 9, 2023	Approved
Pulumi (Portable) 3.56.0	971	Thursday, March 2, 2023	Approved
Pulumi (Portable) 3.55.0	2362	Tuesday, February 14, 2023	Approved
Pulumi (Portable) 3.54.0	1043	Tuesday, February 7, 2023	Approved
Pulumi (Portable) 3.53.1	1561	Wednesday, January 25, 2023	Approved
Pulumi (Portable) 3.53.0	190	Wednesday, January 25, 2023	Approved
Pulumi (Portable) 3.52.1	781	Thursday, January 19, 2023	Approved
Pulumi (Portable) 3.52.0	40	Wednesday, January 18, 2023	Exempted
Pulumi (Portable) 3.51.1	1225	Thursday, January 12, 2023	Approved
Pulumi (Portable) 3.51.0	1209	Wednesday, January 4, 2023	Approved
Pulumi (Portable) 3.49.0	2600	Thursday, December 8, 2022	Approved
Pulumi (Portable) 3.48.0	1605	Wednesday, November 23, 2022	Approved
Pulumi (Portable) 3.47.2	153	Wednesday, November 23, 2022	Approved
Pulumi (Portable) 3.47.1	610	Saturday, November 19, 2022	Approved
Pulumi (Portable) 3.47.0	148	Thursday, November 17, 2022	Approved
Pulumi (Portable) 3.46.1	1406	Wednesday, November 9, 2022	Approved
Pulumi (Portable) 3.46.0	854	Thursday, November 3, 2022	Approved
Pulumi (Portable) 3.45.0	604	Monday, October 31, 2022	Approved
Pulumi (Portable) 3.44.3	415	Friday, October 28, 2022	Approved
Pulumi (Portable) 3.44.2	377	Wednesday, October 26, 2022	Approved
Pulumi (Portable) 3.44.0	379	Monday, October 24, 2022	Approved
Pulumi (Portable) 3.43.1	1150	Saturday, October 15, 2022	Approved
Pulumi (Portable) 3.43.0	133	Friday, October 14, 2022	Approved
Pulumi (Portable) 3.42.0	1181	Friday, October 7, 2022	Approved
Pulumi (Portable) 3.41.1	364	Wednesday, October 5, 2022	Approved
Pulumi (Portable) 3.40.2	1209	Tuesday, September 27, 2022	Approved
Pulumi (Portable) 3.40.1	869	Monday, September 19, 2022	Approved
Pulumi (Portable) 3.40.0	770	Wednesday, September 14, 2022	Approved
Pulumi (Portable) 3.39.3	850	Thursday, September 8, 2022	Approved
Pulumi (Portable) 3.39.2	187	Wednesday, September 7, 2022	Approved
Pulumi (Portable) 3.39.1	567	Friday, September 2, 2022	Approved
Pulumi (Portable) 3.39.0	65	Thursday, September 1, 2022	Approved
Pulumi (Portable) 3.38.0	1629	Tuesday, August 16, 2022	Approved
Pulumi (Portable) 3.37.2	1608	Monday, August 1, 2022	Approved
Pulumi (Portable) 3.37.1	645	Wednesday, July 27, 2022	Approved
Pulumi (Portable) 3.36.0	1609	Thursday, July 14, 2022	Approved
Pulumi (Portable) 3.35.3	1574	Friday, July 1, 2022	Approved
Pulumi (Portable) 3.35.2	326	Wednesday, June 29, 2022	Approved
Pulumi (Portable) 3.35.1	663	Friday, June 24, 2022	Approved
Pulumi (Portable) 3.35.0	347	Wednesday, June 22, 2022	Approved
Pulumi (Portable) 3.34.1	1336	Friday, June 10, 2022	Approved
Pulumi (Portable) 3.34.0	386	Wednesday, June 8, 2022	Approved
Pulumi (Portable) 3.33.2	1385	Friday, May 27, 2022	Approved
Pulumi (Portable) 3.33.1	1103	Thursday, May 19, 2022	Approved
Pulumi (Portable) 3.32.1	1829	Thursday, May 5, 2022	Approved
Pulumi (Portable) 3.32.0	273	Wednesday, May 4, 2022	Approved
Pulumi (Portable) 3.31.1	189	Tuesday, May 3, 2022	Approved
Pulumi (Portable) 3.31.0	577	Friday, April 29, 2022	Approved
Pulumi (Portable) 3.30.0	1345	Wednesday, April 20, 2022	Approved
Pulumi (Portable) 3.29.1	933	Thursday, April 14, 2022	Approved
Pulumi (Portable) 3.28.0	1815	Friday, April 1, 2022	Approved
Pulumi (Portable) 3.27.0	1206	Friday, March 25, 2022	Approved
Pulumi (Portable) 3.26.1	2949	Thursday, March 10, 2022	Approved
Pulumi (Portable) 3.26.0	236	Wednesday, March 9, 2022	Approved
Pulumi (Portable) 3.25.1	941	Wednesday, March 2, 2022	Approved
Pulumi (Portable) 3.25.0	992	Thursday, February 24, 2022	Approved
Pulumi (Portable) 3.24.1	2249	Friday, February 4, 2022	Approved
Pulumi (Portable) 3.23.2	733	Friday, January 28, 2022	Approved
Pulumi (Portable) 3.23.0	719	Thursday, January 27, 2022	Approved
Pulumi (Portable) 3.22.1	1568	Friday, January 14, 2022	Approved
Pulumi (Portable) 3.21.1	1058	Friday, January 7, 2022	Approved
Pulumi (Portable) 3.21.0	1093	Thursday, December 30, 2021	Approved
Pulumi (Portable) 3.20.0	1094	Friday, December 17, 2021	Approved
Pulumi (Portable) 3.19.0	1933	Thursday, December 2, 2021	Approved
Pulumi (Portable) 3.18.1	1383	Tuesday, November 23, 2021	Approved
Pulumi (Portable) 3.18.0	615	Thursday, November 18, 2021	Approved
Pulumi (Portable) 3.17.1	1304	Wednesday, November 10, 2021	Approved
Pulumi (Portable) 3.17.0	1060	Wednesday, November 3, 2021	Approved
Pulumi (Portable) 3.16.0	1469	Monday, October 25, 2021	Approved
Pulumi (Portable) 3.15.0	1270	Sunday, October 17, 2021	Approved
Pulumi (Portable) 3.14.0	1489	Wednesday, October 6, 2021	Approved
Pulumi (Portable) 3.13.2	1080	Tuesday, September 28, 2021	Approved
Pulumi (Portable) 3.13.0	663	Wednesday, September 22, 2021	Approved
Pulumi (Portable) 3.12.0	1398	Thursday, September 9, 2021	Approved
Pulumi (Portable) 3.11.0	1376	Wednesday, August 25, 2021	Approved
Pulumi (Portable) 3.10.3	857	Thursday, August 19, 2021	Approved
Pulumi (Portable) 3.10.2	376	Tuesday, August 17, 2021	Approved
Pulumi (Portable) 3.10.1	515	Thursday, August 12, 2021	Approved
Pulumi (Portable) 3.10.0	163	Thursday, August 12, 2021	Approved
Pulumi (Portable) 3.9.1	1558	Friday, July 30, 2021	Approved
Pulumi (Portable) 3.9.0	183	Wednesday, July 28, 2021	Approved
Pulumi (Portable) 3.8.0	863	Thursday, July 22, 2021	Approved
Pulumi (Portable) 3.7.1	486	Monday, July 19, 2021	Approved
Pulumi (Portable) 3.7.0	524	Wednesday, July 14, 2021	Approved
Pulumi (Portable) 3.6.1	617	Wednesday, July 7, 2021	Approved
Pulumi (Portable) 3.6.0	615	Wednesday, June 30, 2021	Approved
Pulumi (Portable) 3.5.1	1374	Thursday, June 17, 2021	Approved
Pulumi (Portable) 3.4.0	1100	Sunday, June 6, 2021	Approved
Pulumi (Portable) 3.3.1	1045	Tuesday, May 25, 2021	Approved
Pulumi (Portable) 3.3.0	433	Thursday, May 20, 2021	Approved
Pulumi (Portable) 3.2.1	1061	Thursday, May 6, 2021	Approved
Pulumi (Portable) 3.2.0	232	Wednesday, May 5, 2021	Approved
Pulumi (Portable) 3.1.0	988	Friday, April 23, 2021	Approved
Pulumi (Portable) 3.0.0	597	Monday, April 19, 2021	Approved
Pulumi (Portable) 2.25.2	282	Saturday, April 17, 2021	Approved
Pulumi (Portable) 2.25.1	262	Thursday, April 15, 2021	Approved
Pulumi (Portable) 2.25.0	248	Wednesday, April 14, 2021	Approved
Pulumi (Portable) 2.24.1	842	Thursday, April 1, 2021	Approved
Pulumi (Portable) 2.24.0	113	Thursday, April 1, 2021	Approved
Pulumi (Portable) 2.23.2	169	Thursday, March 25, 2021	Approved
Pulumi (Portable) 2.23.1	1742	Thursday, March 18, 2021	Approved
Pulumi (Portable) 2.23.0	152	Wednesday, March 17, 2021	Approved
Pulumi (Portable) 2.22.0	1266	Wednesday, March 3, 2021	Approved
Pulumi (Portable) 2.21.2	922	Monday, February 22, 2021	Approved
Pulumi (Portable) 2.21.1	812	Thursday, February 18, 2021	Approved
Pulumi (Portable) 2.21.0	205	Wednesday, February 17, 2021	Approved
Pulumi (Portable) 2.20.0	13132	Wednesday, February 3, 2021	Approved
Pulumi (Portable) 2.19.0	2889	Thursday, January 28, 2021	Approved
Pulumi (Portable) 2.18.2	569	Friday, January 22, 2021	Approved
Pulumi (Portable) 2.18.1	209	Thursday, January 21, 2021	Approved
Pulumi (Portable) 2.18.0	229	Wednesday, January 20, 2021	Approved
Pulumi (Portable) 2.17.2	511	Friday, January 15, 2021	Approved
Pulumi (Portable) 2.17.1	121	Wednesday, January 13, 2021	Approved
Pulumi (Portable) 2.17.0	732	Wednesday, January 6, 2021	Approved
Pulumi (Portable) 2.16.2	718	Wednesday, December 23, 2020	Approved
Pulumi (Portable) 2.16.1	174	Wednesday, December 23, 2020	Approved
Pulumi (Portable) 2.16.0	237	Monday, December 21, 2020	Approved
Pulumi (Portable) 2.15.6	773	Saturday, December 12, 2020	Approved
Pulumi (Portable) 2.15.5	162	Friday, December 11, 2020	Approved
Pulumi (Portable) 2.15.4	454	Tuesday, December 8, 2020	Approved
Pulumi (Portable) 2.15.2	223	Monday, December 7, 2020	Approved
Pulumi (Portable) 2.15.1	277	Friday, December 4, 2020	Approved
Pulumi (Portable) 2.15.0	335	Wednesday, December 2, 2020	Approved
Pulumi (Portable) 2.14.0	782	Wednesday, November 18, 2020	Approved
Pulumi (Portable) 2.13.2	1048	Saturday, November 7, 2020	Approved
Pulumi (Portable) 2.13.0	703	Wednesday, November 4, 2020	Approved
Pulumi (Portable) 2.12.1	938	Friday, October 23, 2020	Approved
Pulumi (Portable) 2.12.0	526	Thursday, October 15, 2020	Approved
Pulumi (Portable) 2.11.2	1136	Thursday, October 1, 2020	Approved
Pulumi (Portable) 2.11.1	234	Thursday, October 1, 2020	Approved
Pulumi (Portable) 2.10.2	761	Monday, September 21, 2020	Approved
Pulumi (Portable) 2.10.1	444	Wednesday, September 16, 2020	Approved
Pulumi (Portable) 2.10.0	511	Thursday, September 10, 2020	Approved
Pulumi (Portable) 2.9.2	644	Monday, August 31, 2020	Approved
Pulumi (Portable) 2.9.1	280	Thursday, August 27, 2020	Approved
Pulumi (Portable) 2.9.0	647	Wednesday, August 19, 2020	Approved
Pulumi (Portable) 2.8.2	461	Monday, August 10, 2020	Approved
Pulumi (Portable) 2.8.1	283	Thursday, August 6, 2020	Approved
Pulumi (Portable) 2.8.0	141	Tuesday, August 4, 2020	Approved
Pulumi (Portable) 2.7.1	536	Thursday, July 23, 2020	Approved
Pulumi (Portable) 2.6.1	518	Thursday, July 9, 2020	Approved
Pulumi (Portable) 2.6.0	214	Thursday, July 9, 2020	Approved
Pulumi (Portable) 2.5.0	535	Thursday, June 25, 2020	Approved
Pulumi (Portable) 2.4.0	577	Wednesday, June 10, 2020	Approved
Pulumi (Portable) 2.3.0	535	Wednesday, May 27, 2020	Approved
Pulumi (Portable) 2.2.1	553	Thursday, May 14, 2020	Approved
Pulumi (Portable) 2.2.0	190	Thursday, May 14, 2020	Approved
Pulumi (Portable) 2.1.1	247	Tuesday, May 12, 2020	Approved
Pulumi (Portable) 2.1.0	503	Thursday, April 30, 2020	Approved
Pulumi (Portable) 2.0.0	498	Monday, April 20, 2020	Approved
Pulumi (Portable) 1.14.1	392	Tuesday, April 14, 2020	Approved
Pulumi (Portable) 1.14.0	462	Wednesday, April 1, 2020	Approved
Pulumi (Portable) 1.13.1	336	Friday, March 27, 2020	Approved
Pulumi (Portable) 1.13.0	429	Thursday, March 19, 2020	Approved
Pulumi (Portable) 1.12.1	2154	Thursday, March 12, 2020	Approved
Pulumi (Portable) 1.12.0	358	Thursday, March 5, 2020	Approved
Pulumi (Portable) 1.11.1	282	Friday, February 28, 2020	Approved
Pulumi (Portable) 1.11.0	305	Saturday, February 22, 2020	Approved
Pulumi (Portable) 1.10.1	429	Friday, February 7, 2020	Approved
Pulumi (Portable) 1.9.1	375	Tuesday, January 28, 2020	Approved
Pulumi (Portable) 1.9.0	234	Thursday, January 23, 2020	Approved
Pulumi (Portable) 1.8.1	407	Thursday, January 2, 2020	Approved
Pulumi (Portable) 1.7.1	370	Monday, December 16, 2019	Approved
Pulumi (Portable) 1.7.0	269	Thursday, December 12, 2019	Approved
Pulumi (Portable) 1.6.1	258	Wednesday, November 27, 2019	Approved
Pulumi (Portable) 1.6.0	234	Wednesday, November 20, 2019	Approved
Pulumi (Portable) 1.5.2	290	Thursday, November 14, 2019	Approved
Pulumi (Portable) 1.5.1	221	Monday, November 11, 2019	Approved
Pulumi (Portable) 1.5.0	178	Monday, November 11, 2019	Approved
Pulumi (Portable) 1.4.1	223	Monday, November 4, 2019	Approved
Pulumi (Portable) 1.4.0	199	Friday, October 25, 2019	Approved
Pulumi (Portable) 1.3.4	202	Monday, October 21, 2019	Approved
Pulumi (Portable) 1.3.1	235	Friday, October 11, 2019	Approved
Pulumi (Portable) 1.3.0	183	Thursday, October 10, 2019	Approved
Pulumi (Portable) 1.2.0	224	Friday, September 27, 2019	Approved
Pulumi (Portable) 1.1.0	221	Thursday, September 12, 2019	Approved
Pulumi (Portable) 1.0.0	222	Thursday, September 12, 2019	Approved
Pulumi (Portable) 0.17.24	220	Thursday, July 25, 2019	Approved

Pulumi 2016-2023

Release Notes

https://github.com/pulumi/pulumi/blob/master/CHANGELOG.md

Dependencies

This package has no dependencies.

Discussion for the Pulumi (Portable) Package

Ground Rules:

This discussion is only about Pulumi (Portable) and the Pulumi (Portable) package. If you have feedback for Chocolatey, please contact the Google Group.
This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
Tell us what you love about the package or Pulumi (Portable), or tell us what needs improvement.
Share your experiences with the package, or extra configuration or gotchas that you've found.
If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.

Resources

Events

Courses

211,964

986

26 Apr 2024

Pulumi (Portable)

Pulumi (Portable) 3.114.0

Some Checks Have Failed or Are Not Yet Complete

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Modern Infrastructure as Code

Ground Rules: