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:

28,066

Downloads of v 2.17.0:

576

Last Update:

30 Nov 2017

Package Maintainer(s):

Software Author(s):

PicklesDoc and contributors

Tags:

specificationbyexample bdd specflow gherkin cucumber specbyex livingdocumentation documentation

Pickles UI - The Open Source Living Documentation Generator (GUI)

This is not the latest version of Pickles UI - The Open Source Living Documentation Generator (GUI) available.

2.17.0 | Updated: 30 Nov 2017

Downloads:

28,066

Downloads of v 2.17.0:

576

Maintainer(s):

Software Author(s):

PicklesDoc and contributors

Tags:

specificationbyexample bdd specflow gherkin cucumber specbyex livingdocumentation documentation

Pickles UI - The Open Source Living Documentation Generator (GUI) 2.17.0

This is not the latest version of Pickles UI - The Open Source Living Documentation Generator (GUI) available.

All Checks are Passing

3 Passing Tests

Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Pickles UI - The Open Source Living Documentation Generator (GUI), run the following command from the command line or from PowerShell:

To upgrade Pickles UI - The Open Source Living Documentation Generator (GUI), run the following command from the command line or from PowerShell:

To uninstall Pickles UI - The Open Source Living Documentation Generator (GUI), 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 picklesui --internalize --version=2.17.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 picklesui -y --source="'INTERNAL REPO URL'" --version="'2.17.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 picklesui -y --source="'INTERNAL REPO URL'" --version="'2.17.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 picklesui
  win_chocolatey:
    name: picklesui
    version: '2.17.0'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'picklesui' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.17.0'
end

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


cChocoPackageInstaller picklesui
{
    Name     = "picklesui"
    Version  = "2.17.0"
    Source   = "INTERNAL REPO URL"
}

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


package { 'picklesui':
  ensure   => '2.17.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 30 Nov 2017.

Description

Pickles is an open source living documentation generator that works on feature files written in the Gherkin language, popularized in tools like Cucumber and SpecFlow.

This GUI version of Pickles provides an easy way to produce living documentation in a format that is more accessible to your clients. Gherkin language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features.

Pickles can produce output in different formats:

Static HTML: a set of HTML files with minimal JavaScript
Dynamic HTML: a JavaScript-rich single page app with integrated search
Word: Microsoft Word
Excel: Microsoft Excel
JSON: a custom JSON format

Optionally, Pickles can integrate test results, so that your stakeholders know which scenarios pass validation. Pickles supports these test formats:

NUnit
MSTest
XUnit
SpecRun
Cucumber JSON

Files

tools\Autofac.dll

md5: 33461EDAFBADAFC898F51AEFA44066D8 | sha1: 849428E6D7D28FEEA69980DE668C7F93AF7E9758 | sha256: D98C1E2C15C7B643A48ED79942DE943194AF0CC1407DCFA762D19C874E513FA8 | sha512: C5F1A7B2B27B04A4E23972CFC65689D8FF7C20D3F4CAEF5E4458071E8A3455E38BFF29C4852E057DC05DA93B5F2D8628314CCE784FDD45D55FFE0545BFDD6459

tools\ClosedXML.dll

md5: ECACCF48C6B7534C050BE80A8CDFB0B9 | sha1: DD8D80D1DBD0420F7E7489BF31875BA1B938AE25 | sha256: 2E10C6F7535AF4F3E4AAEB891259C1B5ED921076C147B5005DF653ADFCF0B3A9 | sha512: 666166020917F83C5C790212542661FEBC391C207532579938BE22B04F43F9234044F69FDD37E73890BE782A12A9831F2F5712D54E9AEAD1BF694B863B9FD66E

tools\DocumentFormat.OpenXml.dll

md5: 8BF2D98EB3CEA4E624FBFF8E6AEC7C8F | sha1: 8604A515B29A6DB99230E5D72E6EF0924AFBBFEC | sha256: 40F293A772B3017814557BFB6FFD0077C7B81DC4FDC1CAA7498DB64C38DCC25F | sha512: 8CA3882076D50C24926A179FF87C5708040A46AEE33B5EDAD392BEF9D357BF803837F47FA6C73178EBF9C0AC189DAD79CE777FB76170E8CB91818EAE458540AE

tools\FeatureSwitcher.dll

md5: 87C7E94393317CFD6A72FFB96AA6D69F | sha1: 9FF4A4733D2925FC2CA1B74FC9448410C69FB56B | sha256: 637979879D1BA63BBB9DFBEF7D68822892C40543F2B61133709574F902D78A76 | sha512: 2668E2EFB4AEA9FA44A40D8D7E7192B967215F9215A13307E5BC174AFD0CC13A9666819DBE9435C1B4A58670C7948FF47775C5581F6319AF7F3728F271D6889F

tools\GalaSoft.MvvmLight.dll

md5: A42907A9B2D89C4C04DC3975DC17CCD2 | sha1: 63504E01D50CA045665CABF60E5883699BD06FBA | sha256: 77DDF6CF93536C2BE590C254039B11B01D97EBD718A55EDB575C4CF6BB12B107 | sha512: A76F7DD5FF98BE3E5422F501EDD3C797476A9E7DEB63AC89130AAD5B64AAC60060975AE5334F8853C8675D3014BE628598D8588A7E106C051C24044FE484D5B9

tools\GalaSoft.MvvmLight.Extras.dll

md5: 99F85EC0E471BB3D03639DC50056EFF4 | sha1: 8FC5936429E1CE626DB25ACA37FE383AFA0FAB3A | sha256: EB2AF4E82070EF8A5CADEA509F3C8FF2FFC2E093DAC48F77A96DCF89F2ED5A05 | sha512: FB26565FF7088E7FFECC234EBE1C62545FB15F236BE5059325EE89799E328F1A477CACFB470FC5B8A059D1986BB07F8C4A81322A7515103C71E9128AC7C32126

tools\Strike.Jint.dll

md5: 512B102E9DE55235FA56D6D796EB280E | sha1: 50EE4D230B198472A7D6416CE78DDB576439153F | sha256: C7A7EE1BC20CEF26D26DDA222FEA2A179197575DCDE9C2BEE9E0085B3798CBC8 | sha512: A016E40B7EBD4A05522084BAD7005D7627B7606E6DE8783BCF3A09F1ACC0D4E8C9DA110B825503ABDEF4A875CD823E86D4EA5C37103017BAD65667F521200BCE

tools\System.IO.Abstractions.dll

md5: B2E88BED3A0BCE0EBEEB008ABB0741A9 | sha1: EB4CB16B107D3C003F7B3D271928F1822BA1801E | sha256: 50FA2D0D4BAF85A5EB41FBB30C62DAD505BA9E079EBE876A80AD1BD28EF33DE3 | sha512: 455234E55FF648B628924EFA70400AA1DB72920C3DC559E145C950BB0E065CF23527DADFE916C34833B0424EB4491C6795AAE5D5F66C87CDCDDABF83258AF4A7

tools\System.Windows.Interactivity.dll

md5: 580244BC805220253A87196913EB3E5E | sha1: CE6C4C18CF638F980905B9CB6710EE1FA73BB397 | sha256: 93FBC59E4880AFC9F136C3AC0976ADA7F3FAA7CACEDCE5C824B337CBCA9D2EBF | sha512: 2666B594F13CE9DF2352D10A3D8836BF447EAF6A08DA528B027436BB4AFFAAD9CD5466B4337A3EAF7B41D3021016B53C5448C7A52C037708CAE9501DB89A73F0

tools\VERIFICATION.txt


VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
 
This package is published by the Pickles project itself. The binaries are identical to other
package types published by the project, for example the nuget.org packages or the releases
on the GitHub project page.

tools\picklesui.exe.gui

tools\PicklesUI.exe.config

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
    <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
        <section name="Pickles.UserInterface.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
    </sectionGroup>
</configSections>
<startup>
  <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
</startup>
<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Autofac" publicKeyToken="17863af14b0044da" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-3.5.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="NLog" publicKeyToken="5120e14c03d0593c" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Practices.ServiceLocation" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-1.3.0.0" newVersion="1.3.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Windows.Interactivity" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.5.0.0" newVersion="4.5.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
    <userSettings>
        <Pickles.UserInterface.Properties.Settings>
            <setting name="FeatureFolder" serializeAs="String">
                <value />
            </setting>
            <setting name="OutputFolder" serializeAs="String">
                <value />
            </setting>
            <setting name="TestResultsFile" serializeAs="String">
                <value />
            </setting>
        </Pickles.UserInterface.Properties.Settings>
    </userSettings>
</configuration>

tools\picklesui.exe

md5: AD838FAF560919B406AC23A60876CCCF | sha1: DC5ABBACC66686DBECB3ABD37872064D2B9AF7F6 | sha256: EE485AC985A7786DDBFEAAFF591B8A4688FDC997C22B6CFA542756884001320E | sha512: 5B7CE4C4D5425181692E10491AC70ACD7616B66B1D2BD2CA6C109AAC516448869539884630E8026F6BD89FA66CBB53188FF44273424016C8A8114C55DBB44894

tools\PicklesDoc.Pickles.TestFrameworks.dll

md5: F9B9F4E324A06FF48D3CECADC261B41E | sha1: 22217D325C73D5A2C5357A3C4077A59B79BDF2C5 | sha256: 844E203EB1F6898DF027A41805537E19322496C853A8B10EFF91BA0DADB8C86A | sha512: A8FFB1B3939196873CF52194FF64F7ACA406838D60718C2960558F3F611ABF87D6E49096339F0559407494E14A393A1ACF8903C65D44BC547A6ADFAE3F0B3843

tools\PicklesDoc.Pickles.ObjectModel.dll

md5: 595EAC20A6FE933941B42837E49F432C | sha1: 87D84787F57EB8DF89E0BAA1272370CFEA1B9DE8 | sha256: B6F6590F6E2E9BD8CA39D69BC289D328FA2719BCA40682B33A05D9E43BAA6FA1 | sha512: BAE2526FAB9F536A1BB7A833F05DD5060741BFEF46027D72ED2E4CDB21C383C46BEA8DE70A2EB07ACD07DC87DBA5D0F824EA71666F9162DA59D3E50DA0D02A84

tools\PicklesDoc.Pickles.Library.dll

md5: AC8840BD928D2B188B083415330C4E6C | sha1: 5C1B8D0FDCD526FB003FFB4561070FFEAF084E60 | sha256: A77FFA20A22C4BE5870B3DF4088B5752DE1C742ECF3DCCB2A316CF12E69F54D0 | sha512: 526DE71E544B8D5D3CD5A717D610330E237F083BD69B1DBF749C86896CF4FF6753FD73340897878EF681D785C0989C3CDB17DDFBAA50FC0E85DC7DA60C6DD9D2

tools\PicklesDoc.Pickles.DocumentationBuilders.Word.dll

md5: 5A670CA862D818359D1B7BBD90D5BBCC | sha1: 835F5E155617C18665137AA0A9C27F143ECFCC92 | sha256: 94DB25633CD3A346EC0864A2294803A93EA1CC6A830FEA61B0E6B369485F2155 | sha512: ACF24B26AC31540A6EF273170D0AD5FBAE9D78021CB25470F739AB11F1923C21DFF0F0F1FACCD1AE5F0904868B1E616E476E05A37445D8414C7DB0B126D6ADCB

tools\PicklesDoc.Pickles.DocumentationBuilders.Json.dll

md5: 0B23FE85F9F4EB69D42602CEA9BC5053 | sha1: 47F79F0BCE7CD6CDAFAB4F392BC5374EEFA2C85A | sha256: D3C37B53F7B2749C2533968C8439F59C0E61ECBD72E6B08F42CFD7FDB3946060 | sha512: C6E03AD65449E52469AD582D32117B727EB7B0D9D110F9B1E89C25F0F1B1744A55E779E896F33FF4B5FBC96FE72D0F8412FFBA446874036F0BE3C8C768921C80

tools\PicklesDoc.Pickles.DocumentationBuilders.Html.dll

md5: C31F10EA9B5EBB9F6269103C4EF43FB2 | sha1: 367DC2C3F91610115911E6AEB66634E16F907E68 | sha256: 39A9826D46D8B33B9227DA1B92B8476EF9DEA70C8EE195A43D7D3F5D3FC1CE1D | sha512: F2BFE20894CB30D9DF923569279FD1E505F1D57DC8716238106963923E0117305184904240A04575046A77ABE7C2C6BECFD4768268A66276777AC2EFE0DAAF01

tools\PicklesDoc.Pickles.DocumentationBuilders.Excel.dll

md5: 0345000DC3ABFB4396703D2E90C4FAEB | sha1: A5F4F2D8B147133415F221FF5E64C3C007D88C90 | sha256: 2A9E20ACC86B29FF6F3695A6131617AAF2A89258BA8593B36AE687813BBB4588 | sha512: 451CF88F8FFB51FE51B98CD6ACA9DA1FBD4F56F1860F015B4301E46C38B49BCBC03A86EFE508943CB3FA6D267442E36D6A5002B7B8E5CFA3E87E75FDFA4808AB

tools\PicklesDoc.Pickles.DocumentationBuilders.Dhtml.dll

md5: 54A6D875662BE97CCB755704D2C35782 | sha1: D397C4E16407A467A67DFDEE4CF2C32018A15545 | sha256: 15434D44FD78E292EB8F6948178B0CCB3352E0EA43896F42A6A292D7B36CFE41 | sha512: A353C3246B5DD6C21E896C761652AE776D9299242BDC903A0CE00876E1A6CFA460EF2631ECDA1588CD6F4AF6067BA6B5B046EF344D611E80A298978D81340B64

tools\PicklesDoc.Pickles.DocumentationBuilders.Cucumber.dll

md5: 23A2B355887C67A4D61FF4B6DF506D15 | sha1: 6B8712860F5D4616E53AD70A1E4469635464AF49 | sha256: 8088C6055E7E6269F1676CCE850FEEC40E11D058540D795CB03CD5AE0C167428 | sha512: 48EFF0DD607B0F92EAC5B45E9931151407531A49F3E01F4016082D2239F87EA09C87288A43DD720733812C485F38096954ECEC76FA6FC000DD7206610A1BF75E

tools\Ookii.Dialogs.Wpf.dll

md5: 5926472580C7A7B45CD611DC0FB06244 | sha1: A3B33BC8C9963F727BC2A2714EC6DE0C607BCA40 | sha256: 04B8CB55FF481A4F4F9A60BC3C5E06ED78C12A8677C211621EDCF9D8467BD823 | sha512: BE05B4695896B4A2AD2CA63836C9D05084B8AA1B71929E1B081FD47B851282438BDF8C7BC65466CE7F3FE30335E743C0BD12AA52670B12D6EAEC8B3BFD193056

tools\NlogViewer.dll

md5: 48802ECC0F75C66AC24977E7584F6F80 | sha1: 102E4CCC563FEA6C9207F0BFFDD53835A2D86082 | sha256: D5DDD439971597BA31EC804B339F49FF0583EA19C5FC7A089CFF454D782BF455 | sha512: 0D75E8824887E6B9F70622BCC09386906ACD59091C642BAE478BE06FB99787F9154269052CAB9C3C02CB3FE68B833233FA1DE989A04FF8A2249F35405C9DC460

tools\NLog.dll

md5: F7EB59AF6EEF8634F38137E4382278EC | sha1: F1A0410A8B799A9688D01DC4DDA2984C11A40291 | sha256: 9DAAC5262E8F9E930F4B4DB44DF0F983F5D258A6F03E98D9242FB9E652EBF605 | sha512: 7BB82FB6380BE6AE57411AFE346B3048D93FD101162588877B8CB31B5F55D7186820A2FEC0E25EC1C3DAD9CA264D8AB886E3A57D5CF49CDCFE51DEF96E302B4B

tools\NLog.config

<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <extensions>
    <add assembly="NlogViewer" />
  </extensions>
  <targets>
    <target xsi:type="NlogViewer" name="ctrl" />
  </targets>
  <rules>
    <logger name="*" minlevel="Trace" writeTo="ctrl" />
  </rules>
</nlog>

tools\Newtonsoft.Json.dll

md5: A6BE9EFDAA744E9947F4EE18DE5423BD | sha1: 258E57BA953CFADF9FDB00C759E8152A6AE7D883 | sha256: 6CC0CBCD5C4709C6A1C97F5581C347D93E586E7CC0D64BFFB4D32C6E753476A4 | sha512: BE94CB3D150A2066DB44031AD81921813CB841786FA827FDB36FC09BF06BF48939EE71FFFD2D76C5B805B59D6C0F9A3E2DC6927AEAF0B4AC062C92C9205F55B0

tools\Microsoft.Practices.ServiceLocation.dll

md5: 92A533BE83B7FA43A1B18F009A7D450B | sha1: E9AC62EBB0643BFFB243D889C535A8ABCD1BA52A | sha256: 34005D6A80434542780C6D192E6ABD07BEA49B2EEB7E43FBFDFE90C2889986E5 | sha512: B7AE35D9AB96C51B50998B46B8E73BA61BFC01812853C870872A18A3AA986DB8A66D3B8E173E1D7DD58097C07B07AFB64E5297B4B894B8FA1BF565773856A491

tools\MarkdownDeep.dll

md5: 8CBBD216E99B1D4D9304231235FF8C59 | sha1: CFE5C3A8BD9F2A3B814E7DFF271CD3620A04B299 | sha256: C44C392D40A05C5D1356B7F90171318BC03C766F15DE97E08E7F115D10159C87 | sha512: C7E38E07270CFB4DC66DD839D696D51CB3B4241959AD63EC391DD74ECD2C9437E8C9B4AA0F3F4A905BB3D906660597E4F142D3F34BB15E1A228B6341FA9449D7

tools\MahApps.Metro.dll

md5: A1B84E1D85EF46E744E0A492C73CEFA1 | sha1: 492240E4796D1F7B62F16B90C530BB2BB1FEB3BF | sha256: F1A8D821A17D9A38C878B6239F1C142F04495607AD17457022EF58796C127D51 | sha512: 813A63572FD0682BA57DA714402DE7FF8F250C535A0238711E6CEAEEE7BB482360E1CFD2A4BFE40D59756FF12598CA3750DF9CB34DD756E29E4E197AEA7F1B88

tools\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:

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

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

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

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

tools\Jint.dll

md5: E0F990882B2C743EA13AEB79476DEC1B | sha1: 07908FC55B93349C7C69E1BC69DAC384AD8876B9 | sha256: 897CC6D3BC67C7259D3BAE2D9246F6195474B51848490B595E2CD1AC15CF7A66 | sha512: 4A1CA286092D571C22E2C962526493308541CBCE2DC7AB680B8C2140DB9C3DAE6972F85C105423B547490D2DA43375A999E62E6519B64F7851F24E28991B793B

tools\Gherkin.dll

md5: 999C6BC2D2CE7565A861394B01B3B3A9 | sha1: 251E4AE6ED3707B6F91C05982135735D4117B973 | sha256: E44DFDBCBA8B343E9E506DE567F9F3BD236F80112B6078A07B1498DF838F90E1 | sha512: A003137E67B28ECE5E32B7A5FAD3C20395717469C0EB044D7C273D18F99C3EF01CF3CA675EDD0A730A4127F18833F7215CC033DABFD0294C347FDB07278C59D1

tools\GalaSoft.MvvmLight.Platform.dll

md5: E74E1E65C32DAFE45CDADA01F5DEFC67 | sha1: 13A49C5A588C7884035A45C893A2C98BC7A13F3E | sha256: 2B213A15FA2330BDDD575E97FB9D93656D492CF5E11D354897A6CE2FE9508573 | sha512: 83D962233EB6EE3B866E908C860826A623F361C65766BF435226F7F742F8001554FAF90A774AB3951CAEDC0E721C14C529BBFDA294A9F400EF23F7B9BEBD714C

Virus Scan Results

System.Windows.Interactivity.dll (93fbc59e4880) - ## / 68
MarkdownDeep.dll (c44c392d40a0) - ## / 66
DocumentFormat.OpenXml.dll (40f293a772b3) - ## / 68
Microsoft.Practices.ServiceLocation.dll (34005d6a8043) - ## / 68
NlogViewer.dll (d5ddd4399715) - ## / 66
Ookii.Dialogs.Wpf.dll (04b8cb55ff48) - ## / 68
FeatureSwitcher.dll (637979879d1b) - ## / 61
Gherkin.dll (e44dfdbcba8b) - ## / 62
GalaSoft.MvvmLight.dll (77ddf6cf9353) - ## / 64
GalaSoft.MvvmLight.Extras.dll (eb2af4e82070) - ## / 66
GalaSoft.MvvmLight.Platform.dll (2b213a15fa23) - ## / 65
Jint.dll (897cc6d3bc67) - ## / 70
Strike.Jint.dll (c7a7ee1bc20c) - ## / 68
Newtonsoft.Json.dll (6cc0cbcd5c47) - ## / 65
Autofac.dll (d98c1e2c15c7) - ## / 61
ClosedXML.dll (2e10c6f7535a) - ## / 69
NLog.dll (9daac5262e8f) - ## / 60
System.IO.Abstractions.dll (50fa2d0d4baf) - ## / 68
MahApps.Metro.dll (f1a8d821a17d) - ## / 66
PicklesDoc.Pickles.ObjectModel.dll (0827d5e1a2ea) - ## / 64
PicklesDoc.Pickles.DocumentationBuilders.Cucumber.dll (eaab0d1d4ad5) - ## / 67
PicklesDoc.Pickles.DocumentationBuilders.Dhtml.dll (e223166f0f70) - ## / 66
PicklesDoc.Pickles.DocumentationBuilders.Excel.dll (4c9dcb84b8c0) - ## / 66
PicklesDoc.Pickles.DocumentationBuilders.Html.dll (f00b734d17db) - ## / 67
PicklesDoc.Pickles.DocumentationBuilders.Json.dll (8f1d990a836e) - ## / 67
PicklesDoc.Pickles.DocumentationBuilders.Word.dll (30ec17234c97) - ## / 67
PicklesDoc.Pickles.Library.dll (b5c14a76033e) - ## / 66
PicklesDoc.Pickles.TestFrameworks.dll (a92b5461e0e8) - ## / 66
picklesui.exe (684d9633a904) - ## / 68
PicklesDoc.Pickles.ObjectModel.dll (b6f6590f6e2e) - ## / 67
picklesui.2.17.0.nupkg (84f00fce27f8) - ## / 62
PicklesDoc.Pickles.DocumentationBuilders.Cucumber.dll (8088c6055e7e) - ## / 67
PicklesDoc.Pickles.DocumentationBuilders.Dhtml.dll (15434d44fd78) - ## / 67
PicklesDoc.Pickles.DocumentationBuilders.Excel.dll (2a9e20acc86b) - ## / 67
PicklesDoc.Pickles.DocumentationBuilders.Html.dll (39a9826d46d8) - ## / 67
PicklesDoc.Pickles.DocumentationBuilders.Json.dll (d3c37b53f7b2) - ## / 67
PicklesDoc.Pickles.DocumentationBuilders.Word.dll (94db25633cd3) - ## / 67
PicklesDoc.Pickles.Library.dll (a77ffa20a22c) - ## / 67
PicklesDoc.Pickles.TestFrameworks.dll (844e203eb1f6) - ## / 67
picklesui.exe (ee485ac985a7) - ## / 68

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
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.21.1	1040	Monday, March 8, 2021	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.21.0	442	Tuesday, July 14, 2020	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.20.1	1589	Thursday, October 18, 2018	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.20.0	327	Tuesday, October 9, 2018	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.19.0	537	Friday, July 20, 2018	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.18.2	582	Saturday, April 28, 2018	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.18.1	379	Friday, April 20, 2018	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.18.0	610	Friday, February 2, 2018	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.17.0	576	Thursday, November 30, 2017	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.16.2	752	Sunday, August 13, 2017	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.16.1	456	Monday, August 7, 2017	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.16.0	682	Tuesday, June 6, 2017	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.15.0	672	Thursday, March 9, 2017	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.14.0	482	Friday, February 24, 2017	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.13.0	517	Friday, February 10, 2017	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.12.0	462	Thursday, January 26, 2017	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.11.1	511	Friday, December 16, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.11.0	448	Monday, December 5, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.10.0	603	Saturday, October 22, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.9.0	494	Friday, October 7, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.8.3	523	Wednesday, September 28, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.8.2	679	Thursday, August 18, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.8.1	580	Friday, July 29, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.8.0	548	Wednesday, June 29, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.7.0	459	Tuesday, June 14, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.6.3	425	Tuesday, May 24, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.6.2	421	Wednesday, May 11, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.6.1	461	Tuesday, May 10, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.6.0	535	Tuesday, April 12, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.5.0	582	Monday, March 21, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.4.1	600	Tuesday, March 1, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.4.0	466	Friday, February 26, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.3.3	126	Thursday, March 11, 2021	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.3.2	89	Thursday, March 11, 2021	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.3.0	476	Wednesday, January 27, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.2.1	478	Monday, January 25, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.2.0	493	Friday, January 15, 2016	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.1.0	476	Wednesday, December 30, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.0.4	437	Sunday, December 27, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.0.3	526	Wednesday, December 23, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.0.2	526	Saturday, November 21, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.0.1	446	Friday, November 20, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 2.0.0	532	Tuesday, November 3, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 1.2.3	491	Tuesday, October 6, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 1.2.2	471	Thursday, September 24, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 1.2.1	553	Friday, August 14, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 1.2.0	541	Tuesday, July 28, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 1.1.0	595	Tuesday, May 12, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 1.0.1	611	Tuesday, March 31, 2015	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 1.0.0	727	Monday, December 15, 2014	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 0.20.0	521	Thursday, December 11, 2014	Approved
Pickles UI - The Open Source Living Documentation Generator (GUI) 0.19.0	511	Monday, December 1, 2014	Approved

Release Notes

https://github.com/picklesdoc/pickles/blob/master/CHANGELOG.md

Dependencies

This package has no dependencies.

Discussion for the Pickles UI - The Open Source Living Documentation Generator (GUI) Package

Ground Rules:

This discussion is only about Pickles UI - The Open Source Living Documentation Generator (GUI) and the Pickles UI - The Open Source Living Documentation Generator (GUI) 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 Pickles UI - The Open Source Living Documentation Generator (GUI), 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

28,066

576

30 Nov 2017

Pickles UI - The Open Source Living Documentation Generator (GUI)

Pickles UI - The Open Source Living Documentation Generator (GUI) 2.17.0

All Checks are Passing

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: