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.4.1.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.4.1.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.4.1.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.4.1.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:

716,300

Downloads of v 1.16.1:

290

Last Update:

10 Jul 2018

Package Maintainer(s):

jfrog

Software Author(s):

JFrog Ltd

Tags:

jfrog cli admin

JFrog CLI

This is not the latest version of JFrog CLI available.

1.16.1 | Updated: 10 Jul 2018

Downloads:

716,300

Downloads of v 1.16.1:

290

Maintainer(s):

jfrog

Software Author(s):

JFrog Ltd

Tags:

jfrog cli admin

JFrog CLI 1.16.1

This is not the latest version of JFrog CLI available.

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by JFrog Ltd. The inclusion of JFrog Ltd trademark(s), if any, upon this webpage is solely to identify JFrog Ltd goods or services and not for commercial purposes.

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:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install JFrog CLI, run the following command from the command line or from PowerShell:

To upgrade JFrog CLI, run the following command from the command line or from PowerShell:

To uninstall JFrog CLI, 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 jfrog-cli --internalize --version=1.16.1 --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 jfrog-cli -y --source="'INTERNAL REPO URL'" --version="'1.16.1'" [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 jfrog-cli -y --source="'INTERNAL REPO URL'" --version="'1.16.1'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install jfrog-cli
  win_chocolatey:
    name: jfrog-cli
    version: '1.16.1'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'jfrog-cli' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.16.1'
end

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


cChocoPackageInstaller jfrog-cli
{
    Name     = "jfrog-cli"
    Version  = "1.16.1"
    Source   = "INTERNAL REPO URL"
}

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


package { 'jfrog-cli':
  ensure   => '1.16.1',
  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.

NOTE

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

Package Approved

This package was approved as a trusted package on 11 Jul 2018.

Description

JFrog CLI is a compact and smart client that provides a simple interface that automates access to JFrog products simplifying your automation scripts and making them more readable and easier to maintain. JFrog CLI works with JFrog Artifactory, JFrog Mission Control, JFrog Bintray and JFrog Xray (through their respective REST APIs) making your scripts more efficient and reliable in several ways.

Files

tools\chocolateyinstall.ps1

#JFrog CLI is completely contained within an .exe that is provided by the team at JFrog.
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
Get-ChocolateyWebFile `
    -PackageName 'JFrog CLI' `
    -FileFullPath "$env:ProgramData\JFrog\jfrog.exe" `
    -Url 'https://bintray.com/jfrog/jfrog-cli-go/download_file?file_path=1.16.1%2Fjfrog-cli-windows-amd64%2Fjfrog.exe' `
    -Checksum '64F631787D2740EA2E94EBC3875BECAF540BAF00B189197DEC8377A0E92F0747C54BD549DA9AAB71D2AEBDFE50ED5471C0B2C268E1396FA951BAFFD563DBC891' `
    -ChecksumType 'sha512' `
    -ForceDownload
    
Install-ChocolateyPath -PathToInstall "$env:ProgramData\JFrog\" -PathType 'Machine'
Update-SessionEnvironment

Write-Warning ('jfrog added to PATH. It might be required to restart your session in order to use new the environment variable.')

tools\chocolateyuninstall.ps1

$jfrogDir = "$env:ProgramData\Jfrog"
if(Test-Path -Path "$jfrogDir\jfrog.exe" -ErrorAction SilentlyContinue)
{
    Remove-Item -Path $jfrogDir -Force -Recurse > $null
}
else
{
    Write-Warning ("Cannot locate jfrog.exe at $jFrogDir.")
}

$jfrogDir = $jfrogDir -replace '\\','\\' #this formats the path to work with -replace
$path     = "Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment"
$oldPath  = (Get-ItemProperty -Path $path -Name PATH).Path
if($oldPath | Select-String -Pattern 'jfrog')
{
    $newPath  = $oldPath -replace ";$jfrogDir\\",";"
    Set-ItemProperty -Path $path -Name PATH –Value $newPath

    &"C:\ProgramData\Chocolatey\bin\RefreshEnv.cmd"
}
else
{
    Write-Warning ('Cannot locate jfrog in PATH variable.')   
}

Virus Scan Results

jfrog.exe (76f39e01bb08) - ## / 68
jfrog-cli.1.16.1.nupkg (df0195cd6d03) - ## / 60

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
JFrog CLI V2 2.73.0	4630	Tuesday, January 7, 2025	Approved
JFrog CLI V2 2.72.5	3857	Thursday, December 26, 2024	Approved
JFrog CLI V2 2.72.4	15	Thursday, December 26, 2024	Approved
JFrog CLI V2 2.72.3	1064	Sunday, December 22, 2024	Approved
JFrog CLI V2 2.72.2	8067	Friday, November 29, 2024	Approved
JFrog CLI V2 2.72.1	374	Thursday, November 28, 2024	Approved
JFrog CLI V2 2.72.0	564	Wednesday, November 27, 2024	Approved
JFrog CLI V2 2.71.5	3341	Tuesday, November 19, 2024	Approved
JFrog CLI V2 2.71.4	1905	Wednesday, November 13, 2024	Approved
JFrog CLI V2 2.71.3	4316	Monday, November 4, 2024	Approved
JFrog CLI V2 2.71.2	1334	Monday, October 28, 2024	Approved
JFrog CLI V2 2.71.1	1381	Friday, October 25, 2024	Approved
JFrog CLI V2 2.71.0	4145	Friday, October 11, 2024	Approved
JFrog CLI V2 2.70.0	3166	Friday, September 27, 2024	Approved
JFrog CLI V2 2.69.0	586	Tuesday, September 24, 2024	Approved
JFrog CLI V2 2.68.0	1008	Thursday, September 19, 2024	Approved
JFrog CLI V2 2.67.0	2396	Wednesday, September 4, 2024	Approved
JFrog CLI V2 2.66.0	1481	Sunday, September 1, 2024	Approved
JFrog CLI V2 2.65.0	365	Thursday, August 29, 2024	Approved
JFrog CLI V2 2.64.1	516	Tuesday, August 27, 2024	Approved
JFrog CLI V2 2.64.0	845	Thursday, August 22, 2024	Approved
JFrog CLI V2 2.63.2	1034	Thursday, August 15, 2024	Approved
JFrog CLI V2 2.63.1	367	Wednesday, August 14, 2024	Approved
JFrog CLI V2 2.63.0	1334	Tuesday, August 6, 2024	Approved
JFrog CLI V2 2.62.2	73	Tuesday, August 6, 2024	Approved
JFrog CLI V2 2.62.1	727	Thursday, August 1, 2024	Approved
JFrog CLI V2 2.62.0	298	Wednesday, July 31, 2024	Approved
JFrog CLI V2 2.61.2	896	Friday, July 26, 2024	Approved
JFrog CLI V2 2.61.1	215	Thursday, July 25, 2024	Approved
JFrog CLI V2 2.61.0	372	Wednesday, July 24, 2024	Approved
JFrog CLI V2 2.60.0	60	Wednesday, July 24, 2024	Approved
JFrog CLI V2 2.59.1	4278	Thursday, June 27, 2024	Approved
JFrog CLI V2 2.59.0	589	Monday, June 24, 2024	Approved
JFrog CLI V2 2.58.2	2221	Tuesday, June 11, 2024	Approved
JFrog CLI V2 2.58.1	174	Monday, June 10, 2024	Approved
JFrog CLI V2 2.57.1	1270	Sunday, June 2, 2024	Approved
JFrog CLI V2 2.57.0	1285	Thursday, May 23, 2024	Approved
JFrog CLI V2 2.56.1	2096	Thursday, May 9, 2024	Approved
JFrog CLI V2 2.56.0	3278	Wednesday, April 17, 2024	Approved
JFrog CLI V2 2.55.0	2738	Thursday, March 28, 2024	Approved
JFrog CLI V2 2.54.0	1575	Tuesday, March 19, 2024	Approved
JFrog CLI V2 2.53.2	2504	Tuesday, March 5, 2024	Approved
JFrog CLI V2 2.53.1	2167	Wednesday, February 21, 2024	Approved
JFrog CLI V2 2.52.10	83685	Tuesday, January 23, 2024	Approved
JFrog CLI V2 2.52.9	2534	Sunday, January 7, 2024	Approved
JFrog CLI V2 2.52.8	1502	Wednesday, December 27, 2023	Approved
JFrog CLI V2 2.52.7	230	Monday, December 25, 2023	Approved
JFrog CLI V2 2.52.6	471	Thursday, December 21, 2023	Approved
JFrog CLI V2 2.52.5	346	Tuesday, December 19, 2023	Approved
JFrog CLI V2 2.52.4	40	Tuesday, December 19, 2023	Approved
JFrog CLI V2 2.52.3	496	Friday, December 15, 2023	Approved
JFrog CLI V2 2.52.2	1085	Monday, December 11, 2023	Approved
JFrog CLI V2 2.52.1	1237	Tuesday, December 5, 2023	Approved
JFrog CLI V2 2.52.0	309	Monday, December 4, 2023	Approved
JFrog CLI V2 2.51.1	4163	Thursday, November 9, 2023	Approved
JFrog CLI V2 2.51.0	345	Wednesday, November 8, 2023	Approved
JFrog CLI V2 2.50.4	2521	Monday, October 23, 2023	Approved
JFrog CLI V2 2.50.2	767	Wednesday, October 18, 2023	Approved
JFrog CLI V2 2.50.1	1295	Wednesday, October 11, 2023	Approved
JFrog CLI V2 2.50.0	930	Thursday, October 5, 2023	Approved
JFrog CLI V2 2.49.2	594	Thursday, October 5, 2023	Approved
JFrog CLI V2 2.49.1	147	Thursday, October 5, 2023	Approved
JFrog CLI V2 2.49.0	151	Wednesday, October 4, 2023	Approved
JFrog CLI V2 2.48.0	2543	Thursday, September 14, 2023	Approved
JFrog CLI V2 2.47.0	340	Wednesday, September 13, 2023	Approved
JFrog CLI V2 2.46.3	458	Monday, September 11, 2023	Approved
JFrog CLI V2 2.46.2	2545	Friday, August 25, 2023	Approved
JFrog CLI V2 2.46.1	183	Thursday, August 24, 2023	Approved
JFrog CLI V2 2.46.0	178	Wednesday, August 23, 2023	Approved
JFrog CLI V2 2.44.1	18115	Monday, July 31, 2023	Approved
JFrog CLI V2 2.44.0	2671	Sunday, July 23, 2023	Approved
JFrog CLI V2 2.43.1	3844	Wednesday, July 12, 2023	Approved
JFrog CLI V2 2.42.1	2948	Tuesday, July 4, 2023	Approved
JFrog CLI V2 2.41.1	1465	Wednesday, June 28, 2023	Approved
JFrog CLI V2 2.41.0	416	Tuesday, June 27, 2023	Approved
JFrog CLI V2 2.40.0	4925	Saturday, June 10, 2023	Approved
JFrog CLI V2 2.39.1	1979	Sunday, June 4, 2023	Approved
JFrog CLI V2 2.39.0	855	Thursday, June 1, 2023	Approved
JFrog CLI V2 2.38.5	473	Wednesday, May 31, 2023	Approved
JFrog CLI V2 2.38.4	263	Wednesday, May 31, 2023	Approved
JFrog CLI V2 2.38.3	389	Sunday, May 28, 2023	Approved
JFrog CLI V2 2.38.2	394	Wednesday, May 24, 2023	Approved
JFrog CLI V2 2.38.1	245	Tuesday, May 23, 2023	Approved
JFrog CLI V2 2.38.0	137	Tuesday, May 23, 2023	Approved
JFrog CLI V2 2.37.3	578	Wednesday, May 17, 2023	Approved
JFrog CLI V2 2.37.1	849	Tuesday, May 9, 2023	Approved
JFrog CLI V2 2.37.0	763	Wednesday, May 3, 2023	Approved
JFrog CLI V2 2.36.0	2666	Thursday, March 30, 2023	Approved
JFrog CLI V2 2.35.0	2107	Thursday, March 16, 2023	Approved
JFrog CLI V2 2.34.6	2678	Thursday, March 2, 2023	Approved
JFrog CLI V2 2.34.5	780	Monday, February 27, 2023	Approved
JFrog CLI V2 2.34.4	214	Sunday, February 26, 2023	Approved
JFrog CLI V2 2.34.3	885	Wednesday, February 22, 2023	Approved
JFrog CLI V2 2.34.2	1134	Thursday, February 16, 2023	Approved
JFrog CLI V2 2.34.0	3730	Thursday, January 26, 2023	Approved
JFrog CLI V2 2.33.0	1017	Sunday, January 22, 2023	Approved
JFrog CLI V2 2.32.0	3533	Tuesday, January 3, 2023	Approved
JFrog CLI V2 2.31.0	2929	Thursday, December 15, 2022	Approved
JFrog CLI V2 2.29.2	8786	Tuesday, November 8, 2022	Approved
JFrog CLI V2 2.29.0	1316	Thursday, November 3, 2022	Approved
JFrog CLI V2 2.28.2	2284	Thursday, October 27, 2022	Approved
JFrog CLI V2 2.28.1	1659	Friday, October 21, 2022	Approved
JFrog CLI V2 2.28.0	269	Wednesday, October 19, 2022	Approved
JFrog CLI V2 2.27.1	4906	Monday, October 3, 2022	Approved
JFrog CLI V2 2.27.0	375	Sunday, October 2, 2022	Approved
JFrog CLI V2 2.26.2	1505	Tuesday, September 27, 2022	Approved
JFrog CLI V2 2.26.1	2229	Monday, September 19, 2022	Approved
JFrog CLI V2 2.26.0	297	Sunday, September 18, 2022	Approved
JFrog CLI V2 2.25.5	1583	Tuesday, September 13, 2022	Approved
JFrog CLI V2 2.25.4	422	Monday, September 12, 2022	Approved
JFrog CLI V2 2.25.3	1813	Monday, September 5, 2022	Approved
JFrog CLI V2 2.25.2	1693	Tuesday, August 30, 2022	Approved
JFrog CLI V2 2.25.1	97	Tuesday, August 30, 2022	Approved
JFrog CLI V2 2.25.0	2628	Sunday, August 21, 2022	Approved
JFrog CLI V2 2.24.3	1317	Tuesday, August 16, 2022	Approved
JFrog CLI V2 2.24.2	1833	Tuesday, August 9, 2022	Approved
JFrog CLI V2 2.24.1	298	Monday, August 8, 2022	Approved
JFrog CLI V2 2.22.0	3134	Wednesday, July 27, 2022	Approved
JFrog CLI V2 2.21.5	720	Monday, July 25, 2022	Approved
JFrog CLI V2 2.21.4	1498	Tuesday, July 19, 2022	Approved
JFrog CLI V2 2.21.3	606	Sunday, July 17, 2022	Approved
JFrog CLI V2 2.21.2	652	Thursday, July 14, 2022	Approved
JFrog CLI V2 2.21.1	525	Wednesday, July 13, 2022	Approved
JFrog CLI V2 2.21.0	1442	Thursday, July 7, 2022	Approved
JFrog CLI V2 2.20.0	1109	Sunday, July 3, 2022	Approved
JFrog CLI V2 2.18.2	7536	Monday, May 30, 2022	Approved
JFrog CLI V2 2.17.0	1996	Sunday, May 22, 2022	Approved
JFrog CLI V2 2.16.4	2955	Tuesday, May 10, 2022	Approved
JFrog CLI V2 2.16.3	605	Sunday, May 8, 2022	Approved
JFrog CLI V2 2.16.2	2823	Thursday, April 28, 2022	Approved
JFrog CLI V2 2.16.1	1727	Thursday, April 21, 2022	Approved
JFrog CLI V2 2.15.1	2430	Tuesday, April 12, 2022	Approved
JFrog CLI V2 2.15.0	5216	Thursday, March 31, 2022	Approved
JFrog CLI V2 2.14.2	1221	Sunday, March 27, 2022	Approved
JFrog CLI V2 2.14.1	777	Thursday, March 24, 2022	Approved
JFrog CLI V2 2.14.0	1535	Friday, March 18, 2022	Approved
JFrog CLI V2 2.13.0	5979	Thursday, February 24, 2022	Approved
JFrog CLI V2 2.12.1	3705	Tuesday, February 8, 2022	Approved
JFrog CLI V2 2.12.0	1915	Sunday, January 30, 2022	Approved
JFrog CLI V2 2.11.1	1006	Monday, January 24, 2022	Approved
JFrog CLI V2 2.11.0	1321	Thursday, January 13, 2022	Approved
JFrog CLI V2 2.10.1	1009	Tuesday, January 4, 2022	Approved
JFrog CLI V2 2.10.0	293	Friday, December 31, 2021	Approved
JFrog CLI V2 2.8.3	1507	Monday, December 6, 2021	Approved
JFrog CLI V2 2.8.1	293	Thursday, December 2, 2021	Approved
JFrog CLI V2 2.8.0	104	Tuesday, November 30, 2021	Approved
JFrog CLI V2 2.7.0	291	Monday, November 29, 2021	Approved
JFrog CLI V2 2.6.2	12863	Thursday, November 25, 2021	Approved
JFrog CLI V2 2.6.1	387	Monday, November 22, 2021	Approved
JFrog CLI V2 2.6.0	238	Sunday, November 21, 2021	Approved
JFrog CLI V2 2.5.1	128527	Tuesday, November 9, 2021	Approved
JFrog CLI V2 2.5.0	20754	Saturday, October 23, 2021	Approved
JFrog CLI 2.4.1	4811	Sunday, October 10, 2021	Approved
JFrog CLI 1.53.1	4298	Monday, January 31, 2022	Approved
JFrog CLI 1.53.0	6986	Tuesday, January 18, 2022	Approved
JFrog CLI 1.52.0	43935	Sunday, October 10, 2021	Approved
JFrog CLI 1.51.1	16408	Saturday, August 28, 2021	Approved
JFrog CLI 1.51.0	4475	Monday, August 9, 2021	Approved
JFrog CLI 1.50.2	6150	Wednesday, July 14, 2021	Approved
JFrog CLI 1.50.1	425	Wednesday, July 14, 2021	Approved
JFrog CLI 1.50.0	5724	Wednesday, June 23, 2021	Approved
JFrog CLI 1.49.0	2007	Thursday, June 17, 2021	Approved
JFrog CLI 1.48.1	4158	Friday, May 28, 2021	Approved
JFrog CLI 1.48.0	1426	Sunday, May 23, 2021	Approved
JFrog CLI 1.47.3	1689	Saturday, May 15, 2021	Approved
JFrog CLI 1.47.2	1979	Wednesday, May 5, 2021	Approved
JFrog CLI 1.47.1	1034	Thursday, April 29, 2021	Approved
JFrog CLI 1.47.0	346	Wednesday, April 28, 2021	Approved
JFrog CLI 1.46.4	1877	Monday, April 19, 2021	Approved
JFrog CLI 1.46.3	355	Friday, April 16, 2021	Approved
JFrog CLI 1.46.2	414	Thursday, April 15, 2021	Approved
JFrog CLI 1.46.1	2085	Monday, April 5, 2021	Approved
JFrog CLI 1.46.0	150	Sunday, April 4, 2021	Approved
JFrog CLI 1.45.2	3193	Thursday, March 18, 2021	Approved
JFrog CLI 1.45.1	1760	Wednesday, March 10, 2021	Approved
JFrog CLI 1.45.0	401	Tuesday, March 9, 2021	Approved
JFrog CLI 1.44.0	6608	Sunday, January 31, 2021	Approved
JFrog CLI 1.43.2	3824	Wednesday, January 6, 2021	Approved
JFrog CLI 1.43.1	857	Thursday, December 31, 2020	Approved
JFrog CLI 1.43.0	233	Wednesday, December 30, 2020	Approved
JFrog CLI 1.42.3	8066	Friday, December 18, 2020	Approved
JFrog CLI 1.42.2	211	Thursday, December 17, 2020	Approved
JFrog CLI 1.42.1	327	Wednesday, December 16, 2020	Approved
JFrog CLI 1.42.0	257	Tuesday, December 15, 2020	Approved
JFrog CLI 1.41.2	3200	Wednesday, November 25, 2020	Approved
JFrog CLI 1.41.1	1479	Friday, November 13, 2020	Approved
JFrog CLI 1.41.0	181	Thursday, November 12, 2020	Approved
JFrog CLI 1.40.1	1790	Monday, November 2, 2020	Approved
JFrog CLI 1.40.0	1087	Monday, October 26, 2020	Approved
JFrog CLI 1.39.7	3609	Tuesday, October 13, 2020	Approved
JFrog CLI 1.39.6	215	Tuesday, October 13, 2020	Approved
JFrog CLI 1.39.5	1604	Wednesday, September 23, 2020	Approved
JFrog CLI 1.39.4	1452	Thursday, September 10, 2020	Approved
JFrog CLI 1.39.3	810	Thursday, September 3, 2020	Approved
JFrog CLI 1.39.2	827	Saturday, August 29, 2020	Approved
JFrog CLI 1.39.1	504	Monday, August 24, 2020	Approved
JFrog CLI 1.39.0	596	Monday, August 17, 2020	Approved
JFrog CLI 1.38.4	636	Monday, August 10, 2020	Approved
JFrog CLI 1.38.3	341	Wednesday, August 5, 2020	Approved
JFrog CLI 1.38.2	1145	Monday, July 20, 2020	Approved
JFrog CLI 1.38.1	1203	Sunday, July 19, 2020	Approved
JFrog CLI 1.38.0	1191	Wednesday, July 1, 2020	Approved
JFrog CLI 1.37.1	800	Thursday, June 18, 2020	Approved
JFrog CLI 1.37.0	641	Tuesday, June 9, 2020	Approved
JFrog CLI 1.36.0	1352	Monday, May 25, 2020	Approved
JFrog CLI 1.35.5	622	Thursday, May 14, 2020	Approved
JFrog CLI 1.35.4	312	Wednesday, May 13, 2020	Approved
JFrog CLI 1.35.3	2232	Monday, March 30, 2020	Approved
JFrog CLI 1.35.2	282	Sunday, March 29, 2020	Approved
JFrog CLI 1.35.1	793	Wednesday, March 18, 2020	Approved
JFrog CLI 1.35.0	127	Wednesday, March 18, 2020	Approved
JFrog CLI 1.34.1	683	Thursday, March 5, 2020	Approved
JFrog CLI 1.34.0	1626	Saturday, February 29, 2020	Approved
JFrog CLI 1.33.2	1531	Monday, January 27, 2020	Approved
JFrog CLI 1.33.1	418	Sunday, January 19, 2020	Approved
JFrog CLI 1.32.4	8457	Tuesday, December 24, 2019	Approved
JFrog CLI 1.32.3	216	Friday, December 20, 2019	Approved
JFrog CLI 1.32.2	372	Monday, December 16, 2019	Approved
JFrog CLI 1.31.2	932	Wednesday, November 27, 2019	Approved
JFrog CLI 1.31.0	1263	Wednesday, November 27, 2019	Approved
JFrog CLI 1.30.4	1224	Tuesday, November 12, 2019	Approved
JFrog CLI 1.30.3	410	Thursday, November 7, 2019	Approved
JFrog CLI 1.30.2	383	Sunday, November 3, 2019	Approved
JFrog CLI 1.30.1	250	Thursday, October 31, 2019	Approved
JFrog CLI 1.30.0	457	Thursday, October 24, 2019	Approved
JFrog CLI 1.29.2	864	Wednesday, October 16, 2019	Approved
JFrog CLI 1.29.1	652	Thursday, September 26, 2019	Approved
JFrog CLI 1.29.0	273	Tuesday, September 24, 2019	Approved
JFrog CLI 1.28.0	912	Sunday, September 1, 2019	Approved
JFrog CLI 1.27.0	575	Friday, August 16, 2019	Approved
JFrog CLI 1.26.3	1490	Sunday, July 28, 2019	Approved
JFrog CLI 1.26.2	637	Wednesday, July 10, 2019	Approved
JFrog CLI 1.26.1	658	Monday, June 17, 2019	Approved
JFrog CLI 1.26.0	306	Wednesday, June 12, 2019	Approved
JFrog CLI 1.25.0	1742	Thursday, April 18, 2019	Approved
JFrog CLI 1.24.3	1743	Wednesday, March 6, 2019	Approved
JFrog CLI 1.24.2	301	Sunday, March 3, 2019	Approved
JFrog CLI 1.24.1	427	Wednesday, February 20, 2019	Approved
JFrog CLI 1.24.0	184	Wednesday, February 20, 2019	Approved
JFrog CLI 1.23.2	1143	Wednesday, January 30, 2019	Approved
JFrog CLI 1.23.1	977	Wednesday, December 26, 2018	Approved
JFrog CLI 1.23.0	191	Wednesday, December 26, 2018	Approved
JFrog CLI 1.22.1	528	Sunday, December 9, 2018	Approved
JFrog CLI 1.21.1	10947	Saturday, November 17, 2018	Approved
JFrog CLI 1.21.0	209	Saturday, November 17, 2018	Approved
JFrog CLI 1.20.2	228	Saturday, November 17, 2018	Approved
JFrog CLI 1.20.1	188	Saturday, November 17, 2018	Approved
JFrog CLI 1.17.0	1663	Wednesday, July 11, 2018	Approved
JFrog CLI 1.16.2	234	Wednesday, July 11, 2018	Approved
JFrog CLI 1.16.1	290	Tuesday, July 10, 2018	Approved
JFrog CLI 1.11.2	3289	Monday, October 16, 2017	Approved
JFrog CLI 1.10.1	488	Wednesday, August 9, 2017	Approved
JFrog CLI 1.9.0	446	Saturday, July 8, 2017	Approved

Release Notes

https://github.com/kevinkabatra/jfrog-cli/commits/master

Dependencies

This package has no dependencies.

Discussion for the JFrog CLI Package

Ground Rules:

This discussion is only about JFrog CLI and the JFrog CLI 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 JFrog CLI, 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

716,300

290

10 Jul 2018

JFrog CLI

JFrog CLI 1.16.1

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

Ground Rules: