Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

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

Option 2: Internalized Package (Reliable, Scalable)

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

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

### c. Other Requirements ###

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

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

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

## 2. TOP LEVEL VARIABLES ##

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

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

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.2.4.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.4.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.4.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.4.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:

2,006

Downloads of v 4.202:

2,006

Last Update:

04 Dec 2019

Package Maintainer(s):

FredHappyface

Software Author(s):

Mozilla

Tags:

fira font

Fira

4.202 | Updated: 04 Dec 2019

Downloads:

2,006

Downloads of v 4.202:

2,006

Maintainer(s):

FredHappyface

Software Author(s):

Mozilla

Tags:

fira font

Fira 4.202

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

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 Fira, run the following command from the command line or from PowerShell:

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

To uninstall Fira, 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 fira --internalize --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 fira -y --source="'INTERNAL REPO URL'" [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 fira -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install fira
  win_chocolatey:
    name: fira
    version: '4.202'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'fira' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '4.202'
end

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


cChocoPackageInstaller fira
{
    Name     = "fira"
    Version  = "4.202"
    Source   = "INTERNAL REPO URL"
}

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


package { 'fira':
  ensure   => '4.202',
  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 by moderator flcdrg on 08 Dec 2019.

Description

Mozilla's Fira Type Family

http://mozilla.github.io/Fira/

Download Fira

https://github.com/mozilla/Fira/releases/latest - Latest Release
https://github.com/mozilla/Fira/releases - All Releases

Fira Roadmap

See the https://docs.google.com/document/d/1fLxzQsULTv43umIhpB9Gv3Gi7aOBONHbqEbwZIipmxw/edit - Fira Road Map for further information on upcoming releases. Please add your comments or questions within the document.

How to Contribute to Fira

If you're interested in contributing, see our https://docs.google.com/document/d/1QfxweGktJEdBvbd94y-5hiyqu32U9-h_ICPVs76Niyw/edit - Fira Contribution Documentation. Please add your comments or questions within the document.

Usage

Use this font on your website!

link rel="stylesheet" href="https://code.cdn.mozilla.net/fonts/fira.css"/&gt;

External Resources

Further information on the design and specifications of the Fira typeface can be found at https://carrois.com/typefaces/FiraSans/ - Carrois Studio.
Fira can also be found in these foundries:
http://www.1001fonts.com/fira-sans-font.html - 1001 Fonts.
https://typekit.com/fonts/fira-sans - Adobe Typekit.
https://www.google.com/fonts/specimen/Fira+Sans - Google Fonts.
https://www.fontsquirrel.com/fonts/fira-sans - Font Squirrel.

Files

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'
$packageName = 'font-awesome-font'
$toolsDir    = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url         = "$toolsDir\firaSans.zip"

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'ZIP'
  url           = $url
  }

Install-ChocolateyZIPPackage @packageArgs

Install-ChocolateyFont "$toolsDir\otf\FiraMono-Bold.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraMono-Medium.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraMono-Regular.otf"


Install-ChocolateyFont "$toolsDir\otf\FiraSans-Bold.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-BoldItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Book.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-BookItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Eight.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-EightItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-ExtraBold.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-ExtraBoldItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-ExtraLight.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-ExtraLightItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Four.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-FourItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Hair.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-HairItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Heavy.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-HeavyItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Light.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-LightItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Medium.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-MediumItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-SemiBold.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-SemiBoldItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Thin.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-ThinItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Two.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-TwoItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Ultra.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-UltraItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-UltraLight.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-UltraLightItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Regular.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSans-Italic.otf"


Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Bold.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-BoldItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Book.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-BookItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Eight.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-EightItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-ExtraBold.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-ExtraBoldItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-ExtraLight.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-ExtraLightItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Four.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-FourItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Hair.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-HairItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Heavy.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-HeavyItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Light.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-LightItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Medium.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-MediumItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-SemiBold.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-SemiBoldItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Thin.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-ThinItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Two.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-TwoItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Ultra.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-UltraItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-UltraLight.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-UltraLightItalic.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Regular.otf"
Install-ChocolateyFont "$toolsDir\otf\FiraSansCondensed-Italic.otf"


Remove-Item "$toolsDir\otf" -Recurse -ErrorAction SilentlyContinue | Out-Null
Remove-Item "$toolsDir\*.zip" -ErrorAction SilentlyContinue | Out-Null

tools\chocolateyUninstall.ps1

$ErrorActionPreference = 'Stop'


Uninstall-ChocolateyFont "FiraMono-Bold.otf"
Uninstall-ChocolateyFont "FiraMono-Medium.otf"
Uninstall-ChocolateyFont "FiraMono-Regular.otf"


Uninstall-ChocolateyFont "FiraSans-Bold.otf"
Uninstall-ChocolateyFont "FiraSans-BoldItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Book.otf"
Uninstall-ChocolateyFont "FiraSans-BookItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Eight.otf"
Uninstall-ChocolateyFont "FiraSans-EightItalic.otf"
Uninstall-ChocolateyFont "FiraSans-ExtraBold.otf"
Uninstall-ChocolateyFont "FiraSans-ExtraBoldItalic.otf"
Uninstall-ChocolateyFont "FiraSans-ExtraLight.otf"
Uninstall-ChocolateyFont "FiraSans-ExtraLightItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Four.otf"
Uninstall-ChocolateyFont "FiraSans-FourItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Hair.otf"
Uninstall-ChocolateyFont "FiraSans-HairItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Heavy.otf"
Uninstall-ChocolateyFont "FiraSans-HeavyItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Light.otf"
Uninstall-ChocolateyFont "FiraSans-LightItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Medium.otf"
Uninstall-ChocolateyFont "FiraSans-MediumItalic.otf"
Uninstall-ChocolateyFont "FiraSans-SemiBold.otf"
Uninstall-ChocolateyFont "FiraSans-SemiBoldItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Thin.otf"
Uninstall-ChocolateyFont "FiraSans-ThinItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Two.otf"
Uninstall-ChocolateyFont "FiraSans-TwoItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Ultra.otf"
Uninstall-ChocolateyFont "FiraSans-UltraItalic.otf"
Uninstall-ChocolateyFont "FiraSans-UltraLight.otf"
Uninstall-ChocolateyFont "FiraSans-UltraLightItalic.otf"
Uninstall-ChocolateyFont "FiraSans-Regular.otf"
Uninstall-ChocolateyFont "FiraSans-Italic.otf"


Uninstall-ChocolateyFont "FiraSansCondensed-Bold.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-BoldItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Book.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-BookItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Eight.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-EightItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-ExtraBold.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-ExtraBoldItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-ExtraLight.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-ExtraLightItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Four.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-FourItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Hair.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-HairItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Heavy.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-HeavyItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Light.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-LightItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Medium.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-MediumItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-SemiBold.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-SemiBoldItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Thin.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-ThinItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Two.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-TwoItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Ultra.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-UltraItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-UltraLight.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-UltraLightItalic.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Regular.otf"
Uninstall-ChocolateyFont "FiraSansCondensed-Italic.otf"

tools\firaSans.zip

md5: 128C54A9AA5F6D17D0F43B1D58702197 | sha1: A8C7D8D80BFD3058AAF3BA66FC16C5022D8814B1 | sha256: 562E02BCDF0966376EF34EDDD8968B08A263A5F591BBA02F8757842DE896B641 | sha512: BB342C14F2792066FEC03D30990BE3F056B53033C816D528604050B7CC2D41E64EBDB2A1BF29E3DD789267AF1951AD7003FD91A42E83E0D728BDACC85520DD07

tools\LICENSE.txt

Digitized data copyright (c) 2012-2015, The Mozilla Foundation and Telefonica S.A.

This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL


-----------------------------------------------------------
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
-----------------------------------------------------------

PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide a free and
open framework in which fonts may be shared and improved in partnership
with others.

The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded, 
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply
to any document created using the fonts or their derivatives.

DEFINITIONS
"Font Software" refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.

"Reserved Font Name" refers to any names specified as such after the
copyright statement(s).

"Original Version" refers to the collection of Font Software components as
distributed by the Copyright Holder(s).

"Modified Version" refers to any derivative made by adding to, deleting,
or substituting -- in part or in whole -- any of the components of the
Original Version, by changing formats or by porting the Font Software to a
new environment.

"Author" refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.

PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:

1) Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself.

2) Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.

3) No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the corresponding
Copyright Holder. This restriction only applies to the primary font name as
presented to the users.

4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission.

5) The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.

TERMINATION
This license becomes null and void if any of the above conditions are
not met.

DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.

tools\VERIFICATION.txt

============================== Fira Sans ==============================

Downloads the fira sans otf as a .zip and installs to system fonts
courtesy of chocolatey-font-helpers.extension. Follow the step-by-step
to verify the checksums

Step 1:
Download the zip file from
https://github.com/mozilla/Fira/archive/4.202.zip

Step 2:
Extract the zip file and grab/ copy the otf directory

RouteA or RouteB
RouteA to verify the individual .otf files, RouteB to verify a zip file
containing the otf/ directory

RouteA
Step 3:
Open a powershell terminal and run
```powershell
Get-ChildItem | Get-FileHash | Export-Csv checksum.csv
```

Step 4:
Open the csv (many forms of spreadsheet software can help with this. e.g.
Microsoft Excel, LibreOffice Calc). The SHA256 will match those in the
Font List below

(Note that I have reordered the columns)


RouteB
Step 3:
Zip the otf/ directory and run
```powershell
Get-FileHash [zip-name]
```

The SHA256 Hash is 562E02BCDF0966376EF34EDDD8968B08A263A5F591BBA02F8757842DE896B641


------------------------------ Font List ------------------------------
FiraMono-Bold.otf				12B994171A99952FEAD7756658DFCF3DC69D79E07FFF3303444F003580DF9A19	SHA256
FiraMono-Medium.otf				2B3CB27B5A908BD42D8F6B0D0156B2E53EBB56B5D1ED037B5A1A52CA9EE0C402	SHA256
FiraMono-Regular.otf			1783904B9A03D1852ED185549D74526D9F6A4A643181EB591C3A69993AE42CED	SHA256
FiraSans-Bold.otf				A794BB4283AC43C9D9E8DB85B62F5AD64DBC6C28B86435A85E049E1D1B4E103F	SHA256
FiraSans-BoldItalic.otf			61A9FF9457100291C9BC4977E0D1AC79AAB33BD6FE452F34C4AACAA34DA21781	SHA256
FiraSans-Book.otf				65490D82BA3A1FB8E30D473BEC1EE72BDBF96911AB75188354C7F81E105FC800	SHA256
FiraSans-BookItalic.otf			F5C51FDD2BE49AF38057B8147250D2C61459ED43BE3A84CA021CEE93159CEAFC	SHA256
FiraSans-Eight.otf				69B56D7472D33FFABD3EFFD0037ECE1E7645BDD6842B52AE2F166AD5B1419FF9	SHA256
FiraSans-EightItalic.otf		10264035872D28B6FD9DCE4DAE859F5D5B502FE54B0D9ED439125A4EE8928857	SHA256
FiraSans-ExtraBold.otf			4C6AD2DBAEAD50EDFBCAAA84AEF049BE4FEC81A77A495F55FC19998B276F7152	SHA256
FiraSans-ExtraBoldItalic.otf	232F6A9F60F7E62DED0E01DC6FB58D5E828BC945C3788500C4782DFCB97EE4E9	SHA256
FiraSans-ExtraLight.otf			C48491573874F09B93BC609C1F16BC7142994459AFB7801B14FF05FF54AE515F	SHA256
FiraSans-ExtraLightItalic.otf	96FC841B29A167DA915F5D4D8DAEBEF7CAF08732F0061271C5F1EF15ADE6990E	SHA256
FiraSans-Four.otf				9B9FC035620141A28CC8AADB14838EC52D9018631F232BEBD1BFDBC10653774B	SHA256
FiraSans-FourItalic.otf			54D0D5DE1562BBAC770EF08B8EED9E0242AAE600EDE0ED0B7503A5F54BF5E0C3	SHA256
FiraSans-Hair.otf				EA713B1EDDA431D52714B392335E63CE5EC8690B7EE058D3F65730D8E333CE2D	SHA256
FiraSans-HairItalic.otf			139ABF6B16C609FDA83E67BAD994636B52E5AAC957545300386E89758771EEFD	SHA256
FiraSans-Heavy.otf				44A6F0F84E4815446151403FBF21F4BD432264925A40DA2F5B066B88D43601C5	SHA256
FiraSans-HeavyItalic.otf		08519BCDB02AB225A46E1B70E969EBDDD7D3F5861CEFC291A2C802DB8DB50A5B	SHA256
FiraSans-Italic.otf				F96838E0085C2E970EBD8B0D62392B227BADDF0C53485812D8071FE38ACBFEDB	SHA256
FiraSans-Light.otf				BD1BC679CC719ADECD8A64A81F6E625DED78B80BDD464DC53C422A81165F3FC2	SHA256
FiraSans-LightItalic.otf		3C45ED4A497A3DB55ADB1FF6B7B0027798B2982E06ECDBAA5D057ABF6C8EC6CA	SHA256
FiraSans-Medium.otf				305920A930B6532F2A2615D2EA62B22679E337587973F52DC1C85E834D86253A	SHA256
FiraSans-MediumItalic.otf		53E3FBF6FA3F4308132945AE6A95FC919208BD2B0392886DA440DA94739B3DE3	SHA256
FiraSans-Regular.otf			25549423CAB2600F80DE8CF5E0FB484A11D62DB7FC5858933B4DB960864556C5	SHA256
FiraSans-SemiBold.otf			9A005B22D75A57E85B5ED5DC26A9A8EFED02DDB9D08EEDA234FD057C6F86A638	SHA256
FiraSans-SemiBoldItalic.otf		19E9952926ACAAC777B8128D66963976541A98D42CDDD21F27F6C6363F0D27CD	SHA256
FiraSans-Thin.otf				BE644841097513E5ADAF93342163E4040F8FF3756000B8D1265F9907D108F89A	SHA256
FiraSans-ThinItalic.otf			FAA51CCFE323A8B27684B529959762B479688C71C1D2A6A54734201CD05756FE	SHA256
FiraSans-Two.otf				6EEB5160ED8F62E52F91D644E605CFEDEF85696C435A912118F5F5F05C8DB40F	SHA256
FiraSans-TwoItalic.otf			4AFA68CFBAD2151D6BCBA58CAF56C7453B069B7B84B3339ED31FE25EF2ECBE75	SHA256
FiraSans-Ultra.otf				B6595B89CF3D61F87E2E7A782D72EDB54494CA25D6461420AE0D6B616A247F03	SHA256
FiraSans-UltraItalic.otf		B105FD99771CAAC1AEF0136345DDAB70E63296E3A869C0E6F266BE174851B4CF	SHA256
FiraSans-UltraLight.otf			D17707AAE8EA4D09477EB3564136A5E44D9FAB5486B8742AEC64D03C68435448	SHA256
FiraSans-UltraLightItalic.otf	7BF66E8580EF71276C917A615F6487237685ACEC5878D45CBB10DC1E3A6ABDEA	SHA256
FiraSansCondensed-Bold.otf				AD76337E0601753C7E1E3D6727C500699A352E8C60611F943484BC9C4784478F	SHA256
FiraSansCondensed-BoldItalic.otf		210F4E07FEC463FAFB18074AB04F2ABD44F33122FB13447A27955AA8C7320FED	SHA256
FiraSansCondensed-Book.otf				941B0E85594583772A10E035CB37A5AF7294161D95796CCFCA2A613E908E5F02	SHA256
FiraSansCondensed-BookItalic.otf		1270B28F695CD41095A88BC88170CC879B4392F1B0B1AE6FD2FF0E0A1CF90006	SHA256
FiraSansCondensed-Eight.otf				FD202283C171718E6054E9F6E4B18A001506E28548E63D3D37EB77E9C470FFCE	SHA256
FiraSansCondensed-EightItalic.otf		94C305C665000EF580CA3A883852C4F1539E1963010DB023B521B5D810CD51FB	SHA256
FiraSansCondensed-ExtraBold.otf			3E5F3C95CECCE48C594AED9558FBCB8197949F3423DD323A3EFBE1C00D1DC0D5	SHA256
FiraSansCondensed-ExtraboldItalic.otf	6EF531BF5FEBEEACA4315B23BC36C5D6C75B740BEF751BB94549BE01BB1B00DC	SHA256
FiraSansCondensed-ExtraLight.otf		F98E46012272D4C7D194CACECD70E99DDD32FFF1D7CB0ABB147EAC5459FA840F	SHA256
FiraSansCondensed-ExtraLightItalic.otf	55FC0EE196167600B168C182A7936A6AED85E511D55EBE5195FCCA2C450A1719	SHA256
FiraSansCondensed-Four.otf				94C9D85D516E3100CBAD7180F76DE0D5AA84F9A9C6F7DB774F43F8031A2E14AD	SHA256
FiraSansCondensed-FourItalic.otf		DDF8170C825042AA367F311FA00EB60B020098E971BA65AA191BCA82D54A9D45	SHA256
FiraSansCondensed-Hair.otf				8CC60C4FCBC77B80A5729E310CBB2B68747B629FB27CC57BA268F11892C0FD22	SHA256
FiraSansCondensed-HairItalic.otf		6BABB73D02099705304F25CDA89EB3ED1709627EDE6CD4434B1DA70473C24F33	SHA256
FiraSansCondensed-Heavy.otf				8B41491212F1CB746AB7CD617033C8ED4003CDE29E2B6356BFA2BC425979961E	SHA256
FiraSansCondensed-HeavyItalic.otf		F45E643AFD31522360A0C6440CC5951A46E9FFF37D2B350221C28EB5DD194328	SHA256
FiraSansCondensed-Italic.otf			124E4CDB2CE803073D7898A8007B0CF9B3E1C32C9FBE99F4B1276983E3AFFD28	SHA256
FiraSansCondensed-Light.otf				F899778FEA497D40DA29B7E37354E3537D603514C0DE530AE85452D1F01D899C	SHA256
FiraSansCondensed-LightItalic.otf		FA21CE1AD246A80749AC2B5A96B48BB75F3906C7CE3D44B369EF7372F86F9E1B	SHA256
FiraSansCondensed-Medium.otf			851839833C9BB05C353C066FADE2D0A0D2AF15A7CF272223CB8DC0DD6895663D	SHA256
FiraSansCondensed-MediumItalic.otf		991A146511019C562CD2F76C927EE1D9BED977489C2CF945249BB8611DC9CD8C	SHA256
FiraSansCondensed-Regular.otf			33B6E27C681CED796B0BA8A5A84F97422D930D2E06539187786C2F538C3F57C9	SHA256
FiraSansCondensed-SemiBold.otf			7159EAE97AE29B712BA2829D5AB2F2F84908169F8C9937DC2BAE9153120FEAA3	SHA256
FiraSansCondensed-SemiboldItalic.otf	AFAA142AFD021B826668243318BAFD3446A899098846AA9F55480323FBB65290	SHA256
FiraSansCondensed-Thin.otf				78E6C2A744C4921F9F5727EC9A021E4B47FA93DAE2110D16BBB7B9AABCD953CC	SHA256
FiraSansCondensed-ThinItalic.otf		973DC6FF5FEDAF86F1266D0D0B93CE0508CD868676ACA5206432A43A1E0B9BBA	SHA256
FiraSansCondensed-Two.otf				4842F7B58C785A174B634EA15EADE4E3A4674C039A7DE9449972C2F4B0363B1B	SHA256
FiraSansCondensed-TwoItalic.otf			289E8B9394A85D51B17D6C2B090483F3CBF3BB3181646A42D6033EFCFFAF03F8	SHA256
FiraSansCondensed-Ultra.otf				75F729A508182303980B9B571A16DC400CE849E04C2296A06C507D355275F762	SHA256
FiraSansCondensed-UltraItalic.otf		47D9A58917340A4AF68AE9BBD71F4CC17585170A21D1AC000F71D1C30032F4C4	SHA256
FiraSansCondensed-UltraLight.otf		0529E16961B34502C105B3B3CA1A623364E9BAC915D024D0081EBE88BE89B4D4	SHA256
FiraSansCondensed-UltraLightItalic.otf	86954407750C7F14A63310C081C4873B7BFC53F7BD1D7883B990FD5B2F24B017	SHA256


============================== Fira Sans ==============================

Virus Scan Results

firaSans.zip (562e02bcdf09) - ## / 60
fira.4.202.nupkg (8368d8c65438) - ## / 62

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

Add to Builder	Version	Downloads	Last Updated	Status
	Fira 4.202	2006	Wednesday, December 4, 2019	Approved

2012-2015, The Mozilla Foundation and Telefonica S.A.

Dependencies

- chocolatey-font-helpers.extension (≥ 0.0.1)

Discussion for the Fira Package

Ground Rules:

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

2,006

2,006

04 Dec 2019

Fira

Fira 4.202

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

Mozilla's Fira Type Family

Download Fira

Fira Roadmap

How to Contribute to Fira

Usage

External Resources

Ground Rules: