Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
-
STEP1
Package Review
-
STEP2
Integration Method
-
STEP3
Internal Repo Url
-
STEP4
Environment Setup
-
STEP5
Install Script
Step 1: Review Your Packages
Step 2: Choose Your Integration Method
Step 3: Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
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
-
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
-
Run: (additional options)
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:
## 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.1.1.0.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.1.1.0.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.1.1.0.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.1.1.0.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 |
---|---|
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
146,286
Downloads of v 2.3.0.2565:
231
Last Update:
30 Jan 2019
Package Maintainer(s):
Software Author(s):
- Red Gate Software Ltd
Tags:
SQL Server SQL-Server Tools RedGate SqlToolbelt Toolbelt trial admin- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Mailing List
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download

SQL Toolbelt
This is not the latest version of SQL Toolbelt available.
- 1
- 2
- 3
2.3.0.2565 | Updated: 30 Jan 2019
- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Mailing List
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
146,286
Downloads of v 2.3.0.2565:
231
Software Author(s):
- Red Gate Software Ltd
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
- 1
- 2
- 3
SQL Toolbelt
2.3.0.2565
This is not the latest version of SQL Toolbelt available.
- 1
- 2
- 3
This Package Contains an Exempted Check
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install SQL Toolbelt, run the following command from the command line or from PowerShell:
To upgrade SQL Toolbelt, run the following command from the command line or from PowerShell:
To uninstall SQL Toolbelt, run the following command from the command line or from PowerShell:
Deployment Method:
📝 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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download sqltoolbelt --internalize --version=2.3.0.2565 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade sqltoolbelt -y --source="'INTERNAL REPO URL'" --version="'2.3.0.2565'" [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 sqltoolbelt -y --source="'INTERNAL REPO URL'" --version="'2.3.0.2565'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install sqltoolbelt
win_chocolatey:
name: sqltoolbelt
version: '2.3.0.2565'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'sqltoolbelt' do
action :install
source 'INTERNAL REPO URL'
version '2.3.0.2565'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller sqltoolbelt
{
Name = "sqltoolbelt"
Version = "2.3.0.2565"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'sqltoolbelt':
ensure => '2.3.0.2565',
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.
This package was approved as a trusted package on 30 Jan 2019.
Redgate's SQL Toolbelt contains the industry-standard products for SQL Server development, deployment, backup, and monitoring. Together, they make you productive, your team agile, and your data safe.
Thousands of SQL Server professionals rely on the SQL Toolbelt every day, because it’s reliable, easy to use, and plugs in to the tools they already use for application development.
Tools in the SQL Toolbelt:
- SQL Compare - Compare and synchronize database schema
- SQL Data Compare - Compare and synchronize database contents
- SQL Source Control - Connect your databases to your version control system
- SQL Prompt - Write, refactor, and explore SQL effortlessly
- SQL Search - Search your database quickly in SQL Server Management Studio
- SQL Data Generator - Generate realistic test data fast, based on column and table names
- SQL Doc - Automatically generate database documentation
- SQL Test - Write and run unit tests in SQL Server Management Studio
- DLM Dashboard - tracks your database schemas and alerts you when they change.
- SQL Multi Script - Deploy multiple scripts to multiple servers with just one click
- SQL Dependency Tracker - Explore object dependencies and visualize complex databases simply
- SQL Monitor - SQL Server performance monitoring and alerting
- SQL Backup - Compress, securely encrypt and strengthen backups - fast
- SSMS Integration Pack - Use SQL Compare and SQL Data Compare from SSMS
- SQL Change Automation Powershell - Automates database development solutions
- SQL Change Automation - Develop and deploy databases in Visual Studio with migration scripts
Package Download Fallback
This package will fallback to the Red Gate FTP site once the main fixed URL no longer matches the version for which this package was created. This is to ensure that a specific version of the Chocolatey package continues to work even after Red Gate releases newer versions.
When a newer version of the package is published, it will then revert to using the primary https download URL.
Package Parameters
The following package parameters can be set:
/FTP
- Force using the FTP download URL/NoFTP
- Don't fallback to FTP if HTTPS modified time is different (using this risks a checksum mismatch if file is actually a newer version)/products
- Only install the specified products (see tools\chocolateyinstall.ps1 for supported named)
These parameters can be passed to the installer with the use of --params
.
For example: --params "/FTP /products:'SQL Compare, SQL Data Compare'"
.
$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$primaryDownloadUrl = "https://download.red-gate.com/SQLToolbelt.exe"
$secondaryDownloadUrl = 'ftp://support.red-gate.com/patches/SQLToolbelt/29Jan2019/SQLToolbelt.exe'
$packageVersionLastModified = New-Object -TypeName DateTimeOffset 2019, 1, 29, 17, 14, 2, 0 # Last modified time corresponding to this package version
$checksum = 'A38B7A1B7D9BD78082A542E40B34BCAD3C59B22993009EF84177D9DFD1AD4684'
$validProductPackageNames = @(
"SQL Compare",
"SQL Data Compare",
"SQL Source Control",
"SQL Prompt",
"SQL Search",
"SQL Data Generator",
"SQL Doc",
"SQL Test",
"DLM Dashboard",
"SQL Multi Script",
"SQL Dependency Tracker",
"SQL Monitor Installer",
"SQL Backup",
"SSMS Integration Pack",
"SQL Change Automation Powershell",
"SQL Change Automation" )
$pp = Get-PackageParameters
$commandArgs = ""
if ($pp["products"] -ne $null -and $pp["products"] -ne ''){
$products = $pp["products"].Split(",")
foreach($product in $products){
if(!$validProductPackageNames.Contains($product.Trim())){
throw "Invalid product package name '$product', exiting installer."
}
}
$productCommand = "products ""$($pp["products"])"""
$commandArgs += "$productCommand "
} else {
$productCommand = "all products"
}
$commandArgs += "/IAgreeToTheEula"
$url = $primaryDownloadUrl
if ($pp["FTP"] -ne $null -and $pp["FTP"] -ne '') {
# FTP forced
Write-Verbose "Using $secondaryDownloadUrl because /FTP was specified"
$url = $secondaryDownloadUrl
} else {
# Red Gate has a fixed download URL, but if the binary changes we can fall back to their FTP site
# so the package doesn't break
$headers = Get-WebHeaders -url $primaryDownloadUrl
$lastModifiedHeader = $headers.'Last-Modified'
$lastModified = [DateTimeOffset]::Parse($lastModifiedHeader, [Globalization.CultureInfo]::InvariantCulture)
Write-Verbose "Package LastModified: $packageVersionLastModified"
Write-Verbose "HTTP Last Modified : $lastModified"
if ($lastModified -ne $packageVersionLastModified) {
if ($pp["NoFTP"]) {
Write-Warning "The download available at $primaryDownloadUrl has changed from what this package was expecting, but /NoFTP package parameter was supplied. Expect checksums to fail if the download is actually a newer version."
} else {
Write-Warning "The download available at $primaryDownloadUrl has changed from what this package was expecting. Falling back to FTP for version-specific URL"
$url = $secondaryDownloadUrl
}
} else {
Write-Verbose "Primary URL matches package expectation"
}
}
$packageArgs = @{
packageName = $env:ChocolateyPackageName
fileType = 'exe'
silentArgs = $commandArgs
validExitCodes= @(0)
url = $url
checksum = $checksum
checksumType = 'sha256'
destination = $toolsDir
}
Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';
# Empty placeholder uninstall script so that Chocolatey doesn't get confused by not being able to match the package name
# Auto-uninstall correctly uninstalls all individual applications in this bundle
Log in or click on link to see number of positives.
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.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
SQL Toolbelt 2022.06.28 | 55 | Thursday, June 30, 2022 | Approved | |
SQL Toolbelt 2022.06.22 | 736 | Friday, June 24, 2022 | Approved | |
SQL Toolbelt 2022.06.15 | 804 | Friday, June 17, 2022 | Approved | |
SQL Toolbelt 2022.06.13 | 513 | Wednesday, June 15, 2022 | Approved | |
SQL Toolbelt 2022.06.09 | 610 | Saturday, June 11, 2022 | Approved | |
SQL Toolbelt 2022.06.02 | 769 | Saturday, June 4, 2022 | Approved | |
SQL Toolbelt 2022.06.01 | 436 | Friday, June 3, 2022 | Approved | |
SQL Toolbelt 2022.05.26 | 700 | Saturday, May 28, 2022 | Approved | |
SQL Toolbelt 2022.05.25 | 436 | Friday, May 27, 2022 | Approved | |
SQL Toolbelt 2022.05.18 | 746 | Friday, May 20, 2022 | Approved | |
SQL Toolbelt 2022.05.16 | 501 | Wednesday, May 18, 2022 | Approved | |
SQL Toolbelt 2022.05.11 | 655 | Friday, May 13, 2022 | Approved | |
SQL Toolbelt 2022.05.05 | 722 | Saturday, May 7, 2022 | Approved | |
SQL Toolbelt 2022.05.04 | 410 | Friday, May 6, 2022 | Approved | |
SQL Toolbelt 2022.04.28 | 728 | Saturday, April 30, 2022 | Approved | |
SQL Toolbelt 2022.04.27 | 422 | Friday, April 29, 2022 | Approved | |
SQL Toolbelt 2022.04.22 | 660 | Sunday, April 24, 2022 | Approved | |
SQL Toolbelt 2022.04.21 | 400 | Saturday, April 23, 2022 | Approved | |
SQL Toolbelt 2022.04.20 | 406 | Friday, April 22, 2022 | Approved | |
SQL Toolbelt 2022.04.07 | 1023 | Saturday, April 9, 2022 | Approved | |
SQL Toolbelt 2022.03.30 | 794 | Friday, April 1, 2022 | Approved | |
SQL Toolbelt 2022.03.29 | 433 | Thursday, March 31, 2022 | Approved | |
SQL Toolbelt 2022.03.24 | 670 | Saturday, March 26, 2022 | Approved | |
SQL Toolbelt 2022.03.23 | 421 | Friday, March 25, 2022 | Approved | |
SQL Toolbelt 2022.03.21 | 409 | Wednesday, March 23, 2022 | Approved | |
SQL Toolbelt 2022.03.17 | 668 | Saturday, March 19, 2022 | Approved | |
SQL Toolbelt 2022.03.14 | 569 | Wednesday, March 16, 2022 | Approved | |
SQL Toolbelt 2022.03.10 | 624 | Saturday, March 12, 2022 | Approved | |
SQL Toolbelt 2022.03.09 | 408 | Friday, March 11, 2022 | Approved | |
SQL Toolbelt 2022.03.03 | 753 | Saturday, March 5, 2022 | Approved | |
SQL Toolbelt 2022.02.25 | 757 | Sunday, February 27, 2022 | Approved | |
SQL Toolbelt 2022.02.23 | 485 | Friday, February 25, 2022 | Approved | |
SQL Toolbelt 2022.02.17 | 758 | Saturday, February 19, 2022 | Approved | |
SQL Toolbelt 2022.02.16 | 447 | Friday, February 18, 2022 | Approved | |
SQL Toolbelt 2022.02.09 | 889 | Friday, February 11, 2022 | Approved | |
SQL Toolbelt 2022.02.02 | 1018 | Friday, February 4, 2022 | Approved | |
SQL Toolbelt 2022.02.01 | 419 | Thursday, February 3, 2022 | Approved | |
SQL Toolbelt 2022.01.26 | 861 | Friday, January 28, 2022 | Approved | |
SQL Toolbelt 2022.01.19 | 853 | Friday, January 21, 2022 | Approved | |
SQL Toolbelt 2022.01.13 | 789 | Saturday, January 15, 2022 | Approved | |
SQL Toolbelt 2022.01.10 | 37 | Wednesday, January 12, 2022 | Approved | |
SQL Toolbelt 2021.11.24 | 5402 | Friday, November 26, 2021 | Approved | |
SQL Toolbelt 2021.11.18 | 1694 | Saturday, November 20, 2021 | Approved | |
SQL Toolbelt 2021.11.10 | 2140 | Friday, November 12, 2021 | Approved | |
SQL Toolbelt 2021.11.09 | 632 | Thursday, November 11, 2021 | Approved | |
SQL Toolbelt 2021.11.08 | 572 | Wednesday, November 10, 2021 | Approved | |
SQL Toolbelt 2021.11.04 | 1444 | Saturday, November 6, 2021 | Approved | |
SQL Toolbelt 2021.10.27 | 2371 | Friday, October 29, 2021 | Approved | |
SQL Toolbelt 2021.10.20 | 2409 | Friday, October 22, 2021 | Approved | |
SQL Toolbelt 2021.10.11 | 2684 | Wednesday, October 13, 2021 | Approved | |
SQL Toolbelt 2021.09.29 | 3332 | Friday, October 1, 2021 | Approved | |
SQL Toolbelt 2021.09.23 | 1792 | Saturday, September 25, 2021 | Approved | |
SQL Toolbelt 2021.09.22 | 578 | Friday, September 24, 2021 | Approved | |
SQL Toolbelt 2021.09.16 | 1763 | Saturday, September 18, 2021 | Approved | |
SQL Toolbelt 2021.09.09 | 2040 | Saturday, September 11, 2021 | Approved | |
SQL Toolbelt 2021.09.08 | 557 | Friday, September 10, 2021 | Approved | |
SQL Toolbelt 2021.09.02 | 1760 | Saturday, September 4, 2021 | Approved | |
SQL Toolbelt 2021.09.01 | 548 | Friday, September 3, 2021 | Approved | |
SQL Toolbelt 2021.08.31 | 555 | Thursday, September 2, 2021 | Approved | |
SQL Toolbelt 2021.08.24 | 1894 | Thursday, August 26, 2021 | Approved | |
SQL Toolbelt 2021.08.18 | 1674 | Friday, August 20, 2021 | Approved | |
SQL Toolbelt 2021.08.12 | 1660 | Saturday, August 14, 2021 | Approved | |
SQL Toolbelt 2021.08.05 | 1879 | Saturday, August 7, 2021 | Approved | |
SQL Toolbelt 2021.08.04 | 585 | Friday, August 6, 2021 | Approved | |
SQL Toolbelt 2021.08.02 | 750 | Wednesday, August 4, 2021 | Approved | |
SQL Toolbelt 2021.07.29 | 1223 | Saturday, July 31, 2021 | Approved | |
SQL Toolbelt 2021.07.22 | 1678 | Saturday, July 24, 2021 | Approved | |
SQL Toolbelt 2021.07.20 | 842 | Thursday, July 22, 2021 | Approved | |
SQL Toolbelt 2021.07.14 | 1662 | Friday, July 16, 2021 | Approved | |
SQL Toolbelt 2021.07.07 | 1889 | Friday, July 9, 2021 | Approved | |
SQL Toolbelt 2021.06.23 | 3209 | Friday, June 25, 2021 | Approved | |
SQL Toolbelt 2021.06.22 | 512 | Thursday, June 24, 2021 | Approved | |
SQL Toolbelt 2021.06.16 | 1165 | Friday, June 18, 2021 | Approved | |
SQL Toolbelt 2021.06.15 | 863 | Thursday, June 17, 2021 | Approved | |
SQL Toolbelt 2021.06.09 | 38 | Friday, June 11, 2021 | Exempted | |
SQL Toolbelt 2021.06.07 | 458 | Wednesday, June 9, 2021 | Approved | |
SQL Toolbelt 2021.06.02 | 423 | Friday, June 4, 2021 | Approved | |
SQL Toolbelt 2021.06.01 | 306 | Thursday, June 3, 2021 | Approved | |
SQL Toolbelt 2021.05.27 | 386 | Saturday, May 29, 2021 | Approved | |
SQL Toolbelt 2021.05.20 | 45 | Saturday, May 22, 2021 | Exempted | |
SQL Toolbelt 2021.05.12 | 38 | Friday, May 14, 2021 | Exempted | |
SQL Toolbelt 2021.05.11 | 45 | Thursday, May 13, 2021 | Exempted | |
SQL Toolbelt 2021.05.05 | 37 | Friday, May 7, 2021 | Exempted | |
SQL Toolbelt 2021.04.28 | 875 | Friday, April 30, 2021 | Approved | |
SQL Toolbelt 2021.04.27 | 274 | Thursday, April 29, 2021 | Exempted | |
SQL Toolbelt 2021.04.26 | 66 | Wednesday, April 28, 2021 | Exempted | |
SQL Toolbelt 2021.04.21 | 56 | Friday, April 23, 2021 | Exempted | |
SQL Toolbelt 2021.04.13 | 574 | Thursday, April 15, 2021 | Approved | |
SQL Toolbelt 2021.04.12 | 265 | Wednesday, April 14, 2021 | Approved | |
SQL Toolbelt 2021.04.08 | 346 | Saturday, April 10, 2021 | Approved | |
SQL Toolbelt 2021.04.01 | 390 | Saturday, April 3, 2021 | Approved | |
SQL Toolbelt 2021.03.30 | 229 | Thursday, April 1, 2021 | Approved | |
SQL Toolbelt 2021.03.29 | 57 | Wednesday, March 31, 2021 | Approved | |
SQL Toolbelt 2021.03.25 | 46 | Saturday, March 27, 2021 | Approved | |
SQL Toolbelt 2021.03.24 | 65 | Friday, March 26, 2021 | Approved | |
SQL Toolbelt 2021.03.17 | 569 | Friday, March 19, 2021 | Approved | |
SQL Toolbelt 2021.03.12 | 351 | Sunday, March 14, 2021 | Approved | |
SQL Toolbelt 2021.03.11 | 243 | Saturday, March 13, 2021 | Approved | |
SQL Toolbelt 2021.03.10 | 256 | Friday, March 12, 2021 | Approved | |
SQL Toolbelt 2021.03.09 | 250 | Thursday, March 11, 2021 | Approved | |
SQL Toolbelt 2021.03.03 | 351 | Friday, March 5, 2021 | Approved | |
SQL Toolbelt 2021.03.01 | 267 | Wednesday, March 3, 2021 | Approved | |
SQL Toolbelt 2021.02.25 | 287 | Saturday, February 27, 2021 | Approved | |
SQL Toolbelt 2021.02.17 | 368 | Friday, February 19, 2021 | Approved | |
SQL Toolbelt 2021.02.15 | 261 | Wednesday, February 17, 2021 | Approved | |
SQL Toolbelt 2021.02.11 | 299 | Saturday, February 13, 2021 | Approved | |
SQL Toolbelt 2021.02.10 | 239 | Friday, February 12, 2021 | Approved | |
SQL Toolbelt 2021.02.04 | 321 | Saturday, February 6, 2021 | Approved | |
SQL Toolbelt 2021.02.01 | 287 | Wednesday, February 3, 2021 | Approved | |
SQL Toolbelt 2021.01.27 | 309 | Friday, January 29, 2021 | Approved | |
SQL Toolbelt 2021.01.26 | 221 | Thursday, January 28, 2021 | Approved | |
SQL Toolbelt 2021.01.22 | 276 | Sunday, January 24, 2021 | Approved | |
SQL Toolbelt 2021.01.21 | 206 | Saturday, January 23, 2021 | Approved | |
SQL Toolbelt 2021.01.20 | 208 | Friday, January 22, 2021 | Approved | |
SQL Toolbelt 2021.01.18 | 259 | Wednesday, January 20, 2021 | Approved | |
SQL Toolbelt 2021.01.13 | 307 | Friday, January 15, 2021 | Approved | |
SQL Toolbelt 2021.01.08 | 308 | Sunday, January 10, 2021 | Approved | |
SQL Toolbelt 2021.01.05 | 275 | Thursday, January 7, 2021 | Approved | |
SQL Toolbelt 2020.12.17 | 482 | Saturday, December 19, 2020 | Approved | |
SQL Toolbelt 2020.12.16 | 187 | Friday, December 18, 2020 | Approved | |
SQL Toolbelt 2020.12.10 | 274 | Saturday, December 12, 2020 | Approved | |
SQL Toolbelt 2020.12.09 | 189 | Friday, December 11, 2020 | Approved | |
SQL Toolbelt 2020.12.08 | 210 | Thursday, December 10, 2020 | Approved | |
SQL Toolbelt 2020.12.03 | 285 | Saturday, December 5, 2020 | Approved | |
SQL Toolbelt 2020.12.01 | 234 | Thursday, December 3, 2020 | Approved | |
SQL Toolbelt 2020.11.25 | 289 | Friday, November 27, 2020 | Approved | |
SQL Toolbelt 2020.11.19 | 307 | Saturday, November 21, 2020 | Approved | |
SQL Toolbelt 2020.11.18 | 179 | Friday, November 20, 2020 | Approved | |
SQL Toolbelt 2020.11.12 | 251 | Saturday, November 14, 2020 | Approved | |
SQL Toolbelt 2020.11.11 | 158 | Friday, November 13, 2020 | Approved | |
SQL Toolbelt 2020.11.09 | 209 | Wednesday, November 11, 2020 | Approved | |
SQL Toolbelt 2020.11.04 | 271 | Friday, November 6, 2020 | Approved | |
SQL Toolbelt 2020.10.29 | 282 | Saturday, October 31, 2020 | Approved | |
SQL Toolbelt 2020.10.27 | 216 | Thursday, October 29, 2020 | Approved | |
SQL Toolbelt 2020.10.26 | 175 | Wednesday, October 28, 2020 | Approved | |
SQL Toolbelt 2020.10.22 | 235 | Saturday, October 24, 2020 | Approved | |
SQL Toolbelt 2020.10.21 | 156 | Friday, October 23, 2020 | Approved | |
SQL Toolbelt 2020.10.15 | 281 | Saturday, October 17, 2020 | Approved | |
SQL Toolbelt 2020.10.09 | 282 | Sunday, October 11, 2020 | Approved | |
SQL Toolbelt 2020.10.08 | 153 | Saturday, October 10, 2020 | Approved | |
SQL Toolbelt 2020.10.06 | 199 | Thursday, October 8, 2020 | Approved | |
SQL Toolbelt 2020.10.01 | 232 | Saturday, October 3, 2020 | Approved | |
SQL Toolbelt 2020.09.28 | 196 | Wednesday, September 30, 2020 | Approved | |
SQL Toolbelt 2020.09.23 | 199 | Friday, September 25, 2020 | Approved | |
SQL Toolbelt 2020.09.22 | 145 | Thursday, September 24, 2020 | Approved | |
SQL Toolbelt 2020.09.17 | 184 | Saturday, September 19, 2020 | Approved | |
SQL Toolbelt 2020.09.16 | 130 | Friday, September 18, 2020 | Approved | |
SQL Toolbelt 2020.09.15 | 130 | Thursday, September 17, 2020 | Approved | |
SQL Toolbelt 2020.09.09 | 221 | Friday, September 11, 2020 | Approved | |
SQL Toolbelt 2020.09.08 | 130 | Thursday, September 10, 2020 | Approved | |
SQL Toolbelt 2020.09.07 | 142 | Wednesday, September 9, 2020 | Approved | |
SQL Toolbelt 2020.09.03 | 161 | Saturday, September 5, 2020 | Approved | |
SQL Toolbelt 2020.09.02 | 114 | Friday, September 4, 2020 | Approved | |
SQL Toolbelt 2020.08.28 | 168 | Sunday, August 30, 2020 | Approved | |
SQL Toolbelt 2020.08.27 | 84 | Saturday, August 29, 2020 | Approved | |
SQL Toolbelt 2020.08.25 | 152 | Thursday, August 27, 2020 | Approved | |
SQL Toolbelt 2020.08.24 | 119 | Wednesday, August 26, 2020 | Approved | |
SQL Toolbelt 2020.08.21 | 224 | Sunday, August 23, 2020 | Approved | |
SQL Toolbelt 2020.08.20 | 110 | Saturday, August 22, 2020 | Approved | |
SQL Toolbelt 2020.08.17 | 209 | Wednesday, August 19, 2020 | Approved | |
SQL Toolbelt 2020.08.13 | 139 | Saturday, August 15, 2020 | Approved | |
SQL Toolbelt 2020.08.12 | 121 | Friday, August 14, 2020 | Approved | |
SQL Toolbelt 2020.08.11 | 147 | Thursday, August 13, 2020 | Approved | |
SQL Toolbelt 2020.08.10 | 105 | Wednesday, August 12, 2020 | Approved | |
SQL Toolbelt 2020.08.04 | 149 | Thursday, August 6, 2020 | Approved | |
SQL Toolbelt 2020.07.31 | 157 | Sunday, August 2, 2020 | Approved | |
SQL Toolbelt 2020.07.29 | 126 | Friday, July 31, 2020 | Approved | |
SQL Toolbelt 2020.07.23 | 92 | Saturday, July 25, 2020 | Approved | |
SQL Toolbelt 2020.07.22 | 201 | Friday, July 24, 2020 | Approved | |
SQL Toolbelt 2020.07.16 | 210 | Saturday, July 18, 2020 | Approved | |
SQL Toolbelt 2020.07.14 | 160 | Thursday, July 16, 2020 | Approved | |
SQL Toolbelt 2020.07.10 | 135 | Sunday, July 12, 2020 | Approved | |
SQL Toolbelt 2020.07.09 | 106 | Saturday, July 11, 2020 | Approved | |
SQL Toolbelt 2020.07.07 | 102 | Thursday, July 9, 2020 | Approved | |
SQL Toolbelt 2020.07.02 | 152 | Saturday, July 4, 2020 | Approved | |
SQL Toolbelt 2020.07.01 | 126 | Friday, July 3, 2020 | Approved | |
SQL Toolbelt 2020.06.25 | 239 | Saturday, June 27, 2020 | Approved | |
SQL Toolbelt 2020.06.24 | 88 | Friday, June 26, 2020 | Approved | |
SQL Toolbelt 2020.06.17 | 133 | Friday, June 19, 2020 | Approved | |
SQL Toolbelt 2020.06.16 | 144 | Thursday, June 18, 2020 | Approved | |
SQL Toolbelt 2020.06.15 | 119 | Wednesday, June 17, 2020 | Approved | |
SQL Toolbelt 2020.06.12 | 156 | Sunday, June 14, 2020 | Approved | |
SQL Toolbelt 2020.06.11 | 116 | Saturday, June 13, 2020 | Approved | |
SQL Toolbelt 2020.06.10 | 147 | Friday, June 12, 2020 | Approved | |
SQL Toolbelt 2020.06.09 | 117 | Thursday, June 11, 2020 | Approved | |
SQL Toolbelt 2020.06.04 | 141 | Saturday, June 6, 2020 | Approved | |
SQL Toolbelt 2020.06.03 | 76 | Friday, June 5, 2020 | Approved | |
SQL Toolbelt 2020.06.02 | 94 | Thursday, June 4, 2020 | Approved | |
SQL Toolbelt 2020.06.01 | 138 | Wednesday, June 3, 2020 | Approved | |
SQL Toolbelt 2020.05.27 | 166 | Friday, May 29, 2020 | Approved | |
SQL Toolbelt 2020.05.26 | 114 | Thursday, May 28, 2020 | Approved | |
SQL Toolbelt 2020.05.22 | 188 | Sunday, May 24, 2020 | Approved | |
SQL Toolbelt 2020.05.21 | 77 | Saturday, May 23, 2020 | Approved | |
SQL Toolbelt 2020.05.19 | 137 | Thursday, May 21, 2020 | Approved | |
SQL Toolbelt 2020.05.14 | 190 | Saturday, May 16, 2020 | Approved | |
SQL Toolbelt 2020.05.12 | 142 | Thursday, May 14, 2020 | Approved | |
SQL Toolbelt 2020.05.11 | 147 | Wednesday, May 13, 2020 | Approved | |
SQL Toolbelt 2020.05.06 | 138 | Friday, May 8, 2020 | Approved | |
SQL Toolbelt 2020.05.05 | 151 | Thursday, May 7, 2020 | Approved | |
SQL Toolbelt 2020.05.04 | 150 | Wednesday, May 6, 2020 | Approved | |
SQL Toolbelt 2020.04.30 | 135 | Saturday, May 2, 2020 | Approved | |
SQL Toolbelt 2020.04.29 | 125 | Friday, May 1, 2020 | Approved | |
SQL Toolbelt 2020.04.28 | 100 | Thursday, April 30, 2020 | Approved | |
SQL Toolbelt 2020.04.27 | 130 | Wednesday, April 29, 2020 | Approved | |
SQL Toolbelt 2020.04.20 | 204 | Wednesday, April 22, 2020 | Approved | |
SQL Toolbelt 2020.04.16 | 142 | Saturday, April 18, 2020 | Approved | |
SQL Toolbelt 2020.04.15 | 149 | Friday, April 17, 2020 | Approved | |
SQL Toolbelt 2020.04.14 | 131 | Thursday, April 16, 2020 | Approved | |
SQL Toolbelt 2020.04.09 | 143 | Saturday, April 11, 2020 | Approved | |
SQL Toolbelt 2020.04.08 | 148 | Friday, April 10, 2020 | Approved | |
SQL Toolbelt 2020.04.07 | 126 | Thursday, April 9, 2020 | Approved | |
SQL Toolbelt 2020.04.03 | 164 | Sunday, April 5, 2020 | Approved | |
SQL Toolbelt 2020.04.01 | 115 | Friday, April 3, 2020 | Approved | |
SQL Toolbelt 2020.03.31 | 136 | Thursday, April 2, 2020 | Approved | |
SQL Toolbelt 2020.03.30 | 130 | Wednesday, April 1, 2020 | Approved | |
SQL Toolbelt 2020.03.25 | 146 | Friday, March 27, 2020 | Approved | |
SQL Toolbelt 2020.03.23 | 134 | Wednesday, March 25, 2020 | Approved | |
SQL Toolbelt 2020.03.18 | 173 | Friday, March 20, 2020 | Approved | |
SQL Toolbelt 2020.03.06 | 228 | Sunday, March 8, 2020 | Approved | |
SQL Toolbelt 2020.03.04 | 132 | Friday, March 6, 2020 | Approved | |
SQL Toolbelt 2020.03.03 | 142 | Thursday, March 5, 2020 | Approved | |
SQL Toolbelt 2020.02.27 | 177 | Saturday, February 29, 2020 | Approved | |
SQL Toolbelt 2020.02.26 | 138 | Friday, February 28, 2020 | Approved | |
SQL Toolbelt 2020.02.25 | 145 | Thursday, February 27, 2020 | Approved | |
SQL Toolbelt 2020.02.20 | 212 | Saturday, February 22, 2020 | Approved | |
SQL Toolbelt 2020.02.19 | 134 | Friday, February 21, 2020 | Approved | |
SQL Toolbelt 2020.02.12 | 186 | Friday, February 14, 2020 | Approved | |
SQL Toolbelt 2020.02.11 | 122 | Thursday, February 13, 2020 | Approved | |
SQL Toolbelt 2020.02.05 | 166 | Friday, February 7, 2020 | Approved | |
SQL Toolbelt 2020.01.31 | 188 | Saturday, February 1, 2020 | Approved | |
SQL Toolbelt 2020.01.29 | 115 | Thursday, January 30, 2020 | Approved | |
SQL Toolbelt 2020.01.28 | 151 | Wednesday, January 29, 2020 | Approved | |
SQL Toolbelt 2020.01.23 | 152 | Friday, January 24, 2020 | Approved | |
SQL Toolbelt 2020.01.22 | 148 | Thursday, January 23, 2020 | Approved | |
SQL Toolbelt 2020.01.16 | 172 | Friday, January 17, 2020 | Approved | |
SQL Toolbelt 2020.01.14 | 85 | Wednesday, January 15, 2020 | Approved | |
SQL Toolbelt 2020.01.13 | 141 | Tuesday, January 14, 2020 | Approved | |
SQL Toolbelt 2020.01.09 | 152 | Friday, January 10, 2020 | Approved | |
SQL Toolbelt 2020.01.07 | 160 | Wednesday, January 8, 2020 | Approved | |
SQL Toolbelt 2020.01.06 | 124 | Tuesday, January 7, 2020 | Approved | |
SQL Toolbelt 2019.12.17 | 216 | Tuesday, December 17, 2019 | Approved | |
SQL Toolbelt 2019.12.16 | 116 | Tuesday, December 17, 2019 | Approved | |
SQL Toolbelt 2019.12.05 | 273 | Friday, December 6, 2019 | Approved | |
SQL Toolbelt 2019.12.03 | 197 | Wednesday, December 4, 2019 | Approved | |
SQL Toolbelt 2019.12.02 | 148 | Tuesday, December 3, 2019 | Approved | |
SQL Toolbelt 2019.11.28 | 149 | Friday, November 29, 2019 | Approved | |
SQL Toolbelt 2019.11.27 | 138 | Thursday, November 28, 2019 | Approved | |
SQL Toolbelt 2019.11.25 | 154 | Tuesday, November 26, 2019 | Approved | |
SQL Toolbelt 2019.11.21 | 192 | Friday, November 22, 2019 | Approved | |
SQL Toolbelt 2019.11.19 | 168 | Wednesday, November 20, 2019 | Approved | |
SQL Toolbelt 2019.11.12 | 206 | Wednesday, November 13, 2019 | Approved | |
SQL Toolbelt 2019.11.11 | 170 | Tuesday, November 12, 2019 | Approved | |
SQL Toolbelt 2019.11.06 | 177 | Thursday, November 7, 2019 | Approved | |
SQL Toolbelt 2019.11.04 | 173 | Tuesday, November 5, 2019 | Approved | |
SQL Toolbelt 2019.10.30 | 169 | Thursday, October 31, 2019 | Approved | |
SQL Toolbelt 2019.10.28 | 170 | Tuesday, October 29, 2019 | Approved | |
SQL Toolbelt 2019.10.24 | 155 | Friday, October 25, 2019 | Approved | |
SQL Toolbelt 2019.10.23 | 186 | Thursday, October 24, 2019 | Approved | |
SQL Toolbelt 2019.10.21 | 144 | Tuesday, October 22, 2019 | Approved | |
SQL Toolbelt 2019.10.16 | 198 | Thursday, October 17, 2019 | Approved | |
SQL Toolbelt 2019.10.15 | 154 | Wednesday, October 16, 2019 | Approved | |
SQL Toolbelt 2019.10.07 | 186 | Tuesday, October 8, 2019 | Approved | |
SQL Toolbelt 2019.10.02 | 239 | Thursday, October 3, 2019 | Approved | |
SQL Toolbelt 2019.10.01 | 189 | Wednesday, October 2, 2019 | Approved | |
SQL Toolbelt 2019.09.27 | 182 | Saturday, September 28, 2019 | Approved | |
SQL Toolbelt 2.3.4.2670 | 228 | Wednesday, September 11, 2019 | Approved | |
SQL Toolbelt 2.3.4.2667 | 300 | Thursday, August 22, 2019 | Approved | |
SQL Toolbelt 2.3.3.2644 | 196 | Tuesday, August 6, 2019 | Approved | |
SQL Toolbelt 2.3.2.2621 | 192 | Wednesday, July 24, 2019 | Approved | |
SQL Toolbelt 2.3.2.2618 | 332 | Friday, June 21, 2019 | Approved | |
SQL Toolbelt 2.3.1.2615 | 361 | Wednesday, May 15, 2019 | Approved | |
SQL Toolbelt 2.3.1.2612 | 287 | Wednesday, May 1, 2019 | Approved | |
SQL Toolbelt 2.3.1.2610 | 204 | Friday, April 26, 2019 | Approved | |
SQL Toolbelt 2.3.1.2605 | 239 | Wednesday, April 3, 2019 | Approved | |
SQL Toolbelt 2.3.1.2601 | 201 | Friday, March 29, 2019 | Approved | |
SQL Toolbelt 2.3.1.2593 | 261 | Tuesday, March 12, 2019 | Approved | |
SQL Toolbelt 2.3.1.2583 | 162 | Thursday, March 7, 2019 | Approved | |
SQL Toolbelt 2.3.1.2581 | 224 | Thursday, February 28, 2019 | Approved | |
SQL Toolbelt 2.3.0.2579 | 169 | Saturday, February 23, 2019 | Approved | |
SQL Toolbelt 2.3.0.2573 | 200 | Friday, February 15, 2019 | Approved | |
SQL Toolbelt 2.3.0.2565 | 231 | Wednesday, January 30, 2019 | Approved | |
SQL Toolbelt 2.3.0.2563 | 304 | Thursday, January 10, 2019 | Approved | |
SQL Toolbelt 2.3.0.2561 | 306 | Friday, December 21, 2018 | Approved | |
SQL Toolbelt 2.3.0.2557 | 184 | Thursday, December 20, 2018 | Approved | |
SQL Toolbelt 2.3.0.2554 | 282 | Friday, November 16, 2018 | Approved | |
SQL Toolbelt 2.3.0.2538 | 310 | Thursday, October 18, 2018 | Approved | |
SQL Toolbelt 2.3.0.2536 | 203 | Tuesday, October 16, 2018 | Approved | |
SQL Toolbelt 2.3.0.2533 | 228 | Wednesday, October 10, 2018 | Approved | |
SQL Toolbelt 2.2.2.2527 | 211 | Wednesday, October 3, 2018 | Approved | |
SQL Toolbelt 2.2.2.2509 | 361 | Saturday, August 11, 2018 | Approved | |
SQL Toolbelt 2.2.1.2505 | 209 | Friday, August 3, 2018 | Approved | |
SQL Toolbelt 2.2.1.2502 | 213 | Thursday, August 2, 2018 | Approved | |
SQL Toolbelt 2.2.1.2496 | 201 | Thursday, July 26, 2018 | Approved | |
SQL Toolbelt 2.2.1.2493 | 274 | Thursday, July 19, 2018 | Approved | |
SQL Toolbelt 2.2.0.2473 | 318 | Tuesday, July 3, 2018 | Approved | |
SQL Toolbelt 2.2.0.2470 | 235 | Thursday, June 28, 2018 | Approved | |
SQL Toolbelt 2.2.0.2468 | 225 | Saturday, June 23, 2018 | Approved | |
SQL Toolbelt 2.1.2.2457 | 328 | Friday, June 8, 2018 | Approved | |
SQL Toolbelt 2.1.1.2447 | 261 | Tuesday, June 5, 2018 | Approved | |
SQL Toolbelt 2.1.0.2436 | 288 | Tuesday, May 22, 2018 | Approved | |
SQL Toolbelt 2.0.2.2427 | 260 | Thursday, May 10, 2018 | Approved | |
SQL Toolbelt 2.0.1.2423 | 370 | Thursday, March 22, 2018 | Approved | |
SQL Toolbelt 2.0.1.2421 | 357 | Saturday, March 10, 2018 | Approved | |
SQL Toolbelt 2.0.1.2418 | 289 | Thursday, March 8, 2018 | Approved | |
SQL Toolbelt 2.0.1.2415 | 280 | Thursday, March 1, 2018 | Approved | |
SQL Toolbelt 2.0.1.2400 | 316 | Wednesday, February 21, 2018 | Approved | |
SQL Toolbelt 2.0.1.2371 | 318 | Thursday, February 8, 2018 | Approved | |
SQL Toolbelt 2.0.1.2370 | 296 | Thursday, February 1, 2018 | Approved | |
SQL Toolbelt 2.0.1.2344 | 322 | Friday, January 19, 2018 | Approved | |
SQL Toolbelt 2.0.1.2342 | 309 | Saturday, January 13, 2018 | Approved | |
SQL Toolbelt 2.0.1.2337 | 306 | Thursday, January 11, 2018 | Approved | |
SQL Toolbelt 2.0.1.2321 | 377 | Friday, January 5, 2018 | Approved | |
SQL Toolbelt 2.0.1.2318 | 384 | Thursday, January 4, 2018 | Approved | |
SQL Toolbelt 2.0.1.2221 | 408 | Tuesday, December 19, 2017 | Approved | |
SQL Toolbelt 2.0.1.2211 | 321 | Thursday, December 14, 2017 | Approved | |
SQL Toolbelt 2.0.1.2209 | 280 | Wednesday, December 13, 2017 | Approved | |
SQL Toolbelt 2.0.1.2193 | 349 | Friday, December 8, 2017 | Approved | |
SQL Toolbelt 2.0.1.2183 | 339 | Wednesday, December 6, 2017 | Approved | |
SQL Toolbelt 2.0.1.2180 | 292 | Friday, December 1, 2017 | Approved | |
SQL Toolbelt 2.0.1.2171 | 284 | Thursday, November 30, 2017 | Approved | |
SQL Toolbelt 2.0.1.2161 | 350 | Tuesday, November 28, 2017 | Approved | |
SQL Toolbelt 2.0.1.2152 | 316 | Saturday, November 25, 2017 | Approved | |
SQL Toolbelt 2.0.1.2056 | 357 | Wednesday, November 1, 2017 | Approved | |
SQL Toolbelt 2.0.1.2050 | 337 | Tuesday, October 31, 2017 | Approved | |
SQL Toolbelt 2.0.1.2045 | 372 | Friday, October 27, 2017 | Approved | |
SQL Toolbelt 2.0.1.2043 | 370 | Thursday, October 26, 2017 | Approved | |
SQL Toolbelt 2.0.1.2032 | 291 | Tuesday, October 24, 2017 | Approved | |
SQL Toolbelt 2.0.1.2028 | 341 | Thursday, October 19, 2017 | Approved | |
SQL Toolbelt 2.0.1.2019 | 376 | Wednesday, October 18, 2017 | Approved | |
SQL Toolbelt 2.0.1.2016 | 396 | Thursday, October 12, 2017 | Approved | |
SQL Toolbelt 2.0.1.2012 | 339 | Wednesday, October 11, 2017 | Approved | |
SQL Toolbelt 2.0.1.2005 | 301 | Tuesday, October 10, 2017 | Approved | |
SQL Toolbelt 2.0.1.1988 | 331 | Thursday, October 5, 2017 | Approved | |
SQL Toolbelt 2.0.1.1985 | 366 | Wednesday, October 4, 2017 | Approved | |
SQL Toolbelt 2.0.1.1972 | 298 | Tuesday, October 3, 2017 | Approved | |
SQL Toolbelt 2.0.1.1955 | 307 | Thursday, September 28, 2017 | Approved | |
SQL Toolbelt 2.0.1.1945 | 313 | Tuesday, September 26, 2017 | Approved | |
SQL Toolbelt 2.0.1.1939 | 308 | Saturday, September 23, 2017 | Approved | |
SQL Toolbelt 2.0.1.1924 | 290 | Thursday, September 21, 2017 | Approved | |
SQL Toolbelt 2.0.1.1891 | 356 | Friday, September 15, 2017 | Approved | |
SQL Toolbelt 2.0.1.1860 | 304 | Thursday, September 14, 2017 | Approved | |
SQL Toolbelt 2.0.0.1836 | 311 | Tuesday, September 12, 2017 | Approved | |
SQL Toolbelt 2.0.0.1803 | 364 | Thursday, September 7, 2017 | Approved | |
SQL Toolbelt 2.0.0.1789 | 298 | Wednesday, September 6, 2017 | Approved | |
SQL Toolbelt 2.0.0.1785 | 288 | Tuesday, September 5, 2017 | Approved | |
SQL Toolbelt 2.0.0.1745 | 304 | Friday, September 1, 2017 | Approved | |
SQL Toolbelt 2.0.0.1718 | 304 | Thursday, August 31, 2017 | Approved | |
SQL Toolbelt 2.0.0.1662 | 325 | Friday, August 25, 2017 | Approved | |
SQL Toolbelt 1.8.3.1637 | 300 | Thursday, August 24, 2017 | Approved | |
SQL Toolbelt 1.8.3.1618 | 316 | Wednesday, August 23, 2017 | Approved | |
SQL Toolbelt 1.8.3.1592 | 292 | Tuesday, August 22, 2017 | Approved | |
SQL Toolbelt 1.8.3.1575 | 302 | Tuesday, August 15, 2017 | Approved | |
SQL Toolbelt 1.8.3.1571 | 337 | Friday, August 11, 2017 | Approved | |
SQL Toolbelt 1.8.3.1550 | 319 | Thursday, August 10, 2017 | Approved | |
SQL Toolbelt 1.8.3.1519 | 367 | Wednesday, August 9, 2017 | Approved | |
SQL Toolbelt 1.8.3.1441 | 297 | Friday, August 4, 2017 | Approved | |
SQL Toolbelt 1.8.3.1415 | 413 | Thursday, August 3, 2017 | Approved | |
SQL Toolbelt 1.8.3.1322 | 309 | Friday, July 28, 2017 | Approved | |
SQL Toolbelt 1.8.3.1318 | 298 | Thursday, July 27, 2017 | Approved | |
SQL Toolbelt 1.8.3.1230 | 383 | Wednesday, July 19, 2017 | Approved | |
SQL Toolbelt 1.8.3.1139 | 320 | Wednesday, July 12, 2017 | Approved | |
SQL Toolbelt 1.8.3.1104 | 302 | Tuesday, July 11, 2017 | Approved | |
SQL Toolbelt 1.8.3.1076 | 323 | Saturday, July 8, 2017 | Approved | |
SQL Toolbelt 1.8.3.1022 | 342 | Tuesday, July 4, 2017 | Approved | |
SqlToolbelt 1.8.2.403 | 1002 | Thursday, April 17, 2014 | Approved |
2017 Red Gate Software Ltd
-
- chocolatey-core.extension (≥ 1.1.0)
Ground Rules:
- This discussion is only about SQL Toolbelt and the SQL Toolbelt 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 SQL Toolbelt, 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.