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

9,150

Downloads of v 1.4.4:

34

Last Update:

31 Dec 2024

Package Maintainer(s):

Petabridge

Software Author(s):

Petabridge
LLC

Tags:

petabridge cli akka cluster clustering distributed admin

Petabridge.Cmd

1.4.4 | Updated: 31 Dec 2024

Downloads:

9,150

Downloads of v 1.4.4:

Maintainer(s):

Petabridge

Software Author(s):

Petabridge
LLC

Tags:

petabridge cli akka cluster clustering distributed admin

Petabridge.Cmd 1.4.4

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Petabridge, LLC. The inclusion of Petabridge, LLC trademark(s), if any, upon this webpage is solely to identify Petabridge, LLC 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 Petabridge.Cmd, run the following command from the command line or from PowerShell:

To upgrade Petabridge.Cmd, run the following command from the command line or from PowerShell:

To uninstall Petabridge.Cmd, 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 petabridge-cmd --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 petabridge-cmd -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 petabridge-cmd -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 petabridge-cmd
  win_chocolatey:
    name: petabridge-cmd
    version: '1.4.4'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'petabridge-cmd' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.4.4'
end

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


cChocoPackageInstaller petabridge-cmd
{
    Name     = "petabridge-cmd"
    Version  = "1.4.4"
    Source   = "INTERNAL REPO URL"
}

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


package { 'petabridge-cmd':
  ensure   => '1.4.4',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 31 Dec 2024.

Description

Petabridge.Cmd helps you automate, manage, and monitor Akka.NET applications of all shapes and sizes. It's available as a simple commandline tool that requires minimal setup and configuration overhead.

Files

tools\Akka.dll

md5: 8D19AB41C66E601C92C47E1E5934A23C | sha1: BA007C58FDB8309E84B209ABECB7D958DB793300 | sha256: 5B125AE3D027F3ADE63BC07F01E47BBAF030428B3DA5EB7ACAF65F1FEA050575 | sha512: 3195F0A90114196C4FDF0C697C787F0927827FE905BE7100C9CF1DDD55E6D85940D2A1D801815B423A9CE53D7363ED505821635E66E1BA413733D2AB5B90AFAD

tools\Akka.Streams.dll

md5: 7D573D38D49E53846252F8288BF66AE2 | sha1: 6A953B1A645BBA490528C72A71596E6E700E82B6 | sha256: 9DDBBCE38218408ECA677150C951E1C167B3978DA88CD22E38B64D614F6280CA | sha512: F841CFFFF067DE536B75AF85F7651B9422594A6D9861DC10201C469E3DE8A4EBD3D7124632C5611C6537D19AE40AB6BF74397D679C4846826A41D61010B6A248

tools\Google.Protobuf.dll

md5: 564F08AAEAEBC4EB32F46B0C9376ACD7 | sha1: D9C3739CCAB39332D2AFE1A4BB5F13E5A7B8EA87 | sha256: 34999912D5F09C9996A079BE41A91B11ED7264A086BE249C0E9FA3F659FE8D4F | sha512: D9EC0FFAC8FA5D2D4B495C25505557F82AE63801D1AE9B1CBAB3790C50AABD1FB45349157ABB475614D750A47F58FB9ED725DE265C1F2D0329F75F3B3EA102B4

tools\license.txt

Petabridge.Cmd - Terms and conditions

Preamble: This Agreement, signed on Apr 14, 2017 (hereinafter: Effective Date) governs the relationship between the end-user of this software, (hereinafter: Licensee) and Petabridge, LLC, a duly registered company in whose principal place of business is 3310 Louisiana St., Houston, Texas 77006 (hereinafter: Licensor). This Agreement sets the terms, rights, restrictions and obligations on using Petabridge.Cmd (hereinafter: The Software) created and owned by Licensor, as detailed herein.


License Grant: Licensor hereby grants Licensee a Sublicensable, Non-assignable & non-transferable, Perpetual, Commercial, Royalty free, Without the rights to create derivative works, Non-exclusive license, all with accordance with the terms set forth and other legal restrictions set forth in 3rd party software used while running Software.

Limited: Licensee may use Software for the purpose of:
* Running Software on Licensee’s Website[s] and Server[s];
* Allowing 3rd Parties to run Software on Licensee’s Website[s] and Server[s];
* Publishing Software’s output to Licensee and 3rd Parties; and
* Create and use plugins that use Software's APIs and extensions.

This license is granted perpetually, as long as you do not materially breach it.

Binary Restricted: Licensee may sublicense Software as a part of a larger work containing more than Software, distributed solely in Object or Binary form under a personal, non-sublicensable, limited license. Such redistribution shall be limited to unlimited codebases.

Non Assignable & Non-Transferable: Licensee may not assign or transfer his rights and duties under this license.

Commercial, Royalty Free: Licensee may use Software for any purpose, including paid-services, without any royalties
Term & Termination: The Term of this license shall be until terminated. Licensor may terminate this Agreement, including Licensee’s license in the case where Licensee :
* became insolvent or otherwise entered into any liquidation process; or
* exported The Software to any jurisdiction where licensor may not enforce his rights under this agreements in; or
* Licensee was in breach of any of this license's terms and conditions and such breach was not cured, immediately upon notification; or
* Licensee in breach of any of the terms of clause 2 to this license; or
* Licensee otherwise entered into any arrangement which caused Licensor to be unable to enforce his rights under this License.

Upgrades, Updates and Fixes: Licensor may provide Licensee, from time to time, with Upgrades, Updates or Fixes, as detailed herein and according to his sole discretion. Licensee hereby warrants to keep The Software up-to-date and install all relevant updates and fixes, and may, at his sole discretion, purchase upgrades, according to the rates set by Licensor. Licensor shall provide any update or Fix free of charge; however, nothing in this Agreement shall require Licensor to provide Updates or Fixes.

Upgrades: for the purpose of this license, an Upgrade shall be a material amendment in The Software, which contains new features and or major performance improvements and shall be marked as a new version number. For example, should Licensee purchase The Software under version 1.X.X, an upgrade shall commence under number 2.0.0.

Updates: for the purpose of this license, an update shall be a minor amendment in The Software, which may contain new features or minor improvements and shall be marked as a new sub-version number. For example, should Licensee purchase The Software under version 1.1.X, an upgrade shall commence under number 1.2.0.

Fix: for the purpose of this license, a fix shall be a minor amendment in The Software, intended to remove bugs or alter minor features which impair the The Software's functionality. A fix shall be marked as a new sub-sub-version number. For example, should Licensee purchase Software under version 1.1.1, an upgrade shall commence under number 1.1.2.

Support: Software is provided under an AS-IS basis and without any support, updates or maintenance. Nothing in this Agreement shall require Licensor to provide Licensee with support or fixes to any bug, failure, mis-performance or other defect in The Software.
Bug Notification: Licensee may provide Licensor of details regarding any bug, defect or failure in The Software promptly and with no delay from such event; Licensee shall comply with Licensor's request for information regarding bugs, defects or failures and furnish him with information, screenshots and try to reproduce such bugs, defects or failures.

Feature Request: Licensee may request additional features in Software, provided, however, that (i) Licensee shall waive any claim or right in such feature should feature be developed by Licensor; (ii) Licensee shall be prohibited from developing the feature, or disclose such feature request, or feature, to any 3rd party directly competing with Licensor or any 3rd party which may be, following the development of such feature, in direct competition with Licensor; (iii) Licensee warrants that feature does not infringe any 3rd party patent, trademark, trade-secret or any other intellectual property right; and (iv) Licensee developed, envisioned or created the feature solely by himself.
Liability:  To the extent permitted under Law, The Software is provided under an AS-IS basis. Licensor shall never, and without any limit, be liable for any damage, cost, expense or any other payment incurred by Licensee as a result of Software’s actions, failure, bugs and/or any other interaction between The Software  and Licensee’s end-equipment, computers, other software or any 3rd party, end-equipment, computer or services.  Moreover, Licensor shall never be liable for any defect in source code written by Licensee when relying on The Software or using The Software’s source code.

Warranty: Intellectual Property: Licensor hereby warrants that The Software does not violate or infringe any 3rd party claims in regards to intellectual property, patents and/or trademarks and that to the best of its knowledge no legal action has been taken against it for any infringement or violation of any 3rd party intellectual property rights.
No-Warranty: The Software is provided without any warranty; Licensor hereby disclaims any warranty that The Software shall be error free, without defects or code which may cause damage to Licensee’s computers or to Licensee, and that Software shall be functional. Licensee shall be solely liable to any damage, defect or loss incurred as a result of operating software and undertake the risks contained in running The Software on License’s Server[s] and Website[s].

Prior Inspection: Licensee hereby states that he inspected The Software thoroughly and found it satisfactory and adequate to his needs, that it does not interfere with his regular operation and that it does meet the standards and scope of his computer systems and architecture. Licensee found that The Software interacts with his development, website and server environment and that it does not infringe any of End User License Agreement of any software Licensee may use in performing his services. Licensee hereby waives any claims regarding The Software's incompatibility, performance, results and features, and warrants that he inspected the The Software.
No Refunds: Licensee warrants that he inspected The Software according to clause 7(c) and that it is adequate to his needs. Accordingly, as The Software is intangible goods, Licensee shall not be, ever, entitled to any refund, rebate, compensation or restitution for any reason whatsoever, even if The Software contains material flaws.

Indemnification: Licensee hereby warrants to hold Licensor harmless and indemnify Licensor for any lawsuit brought against it in regards to Licensee’s use of The Software in means that violate, breach or otherwise circumvent this license, Licensor's intellectual property rights or Licensor's title in The Software. Licensor shall promptly notify Licensee in case of such legal action and request Licensee’s consent prior to any settlement in relation to such lawsuit or claim.

Governing Law, Jurisdiction: Licensee hereby agrees not to initiate class-action lawsuits against Licensor in relation to this license and to compensate Licensor for any legal fees, cost or attorney fees should any claim brought by Licensee against Licensor be denied, in part or in full.

tools\Microsoft.Bcl.AsyncInterfaces.dll

md5: FF34978B62D5E0BE84A895D9C30F99AE | sha1: 74DC07A8CCCEE0CA3BF5CF64320230CA1A37AD85 | sha256: 80678203BD0203A6594F4E330B22543C0DE5059382BB1C9334B7868B8F31B1BC | sha512: 7F207F2E3F9F371B465BCA5402DB0E5CEC3CB842A1F943D3E3DCEDC8E5D134F58C7C4DF99303C24501C103494B4F16160F86DB80893779CE41B287A23574EE28

tools\Microsoft.Extensions.ObjectPool.dll

md5: A13EBEFCEBCE04B44539AA3424375987 | sha1: 0FDC83FF88D59DF1FB9E7B1E591258D6C3E059D5 | sha256: CC0997C52EFF5A58ED56593F842947427EC6FF62709E422B6F8111AA96D064A3 | sha512: E9FFA0335D563CF55B7BDB7DBEF663D2AACF27E3FFE8D78F0C02427378086B24C85B78A401A2099FDD839655AEA2FB54B164D8C66ACD6EAD9C710B471B5E4E2E

tools\Newtonsoft.Json.dll

md5: 081D9558BBB7ADCE142DA153B2D5577A | sha1: 7D0AD03FBDA1C24F883116B940717E596073AE96 | sha256: B624949DF8B0E3A6153FDFB730A7C6F4990B6592EE0D922E1788433D276610F3 | sha512: 2FDF035661F349206F58EA1FEED8805B7F9517A21F9C113E7301C69DE160F184C774350A12A710046E3FF6BAA37345D319B6F47FD24FBBA4E042D54014BEE511

tools\pbm.exe

md5: F66580DA33D5AFBB56EEE07EDE1A4B13 | sha1: A8A215A14F82761170F8129271434B0A3211D06F | sha256: 46DE2E6AC8191C88372F9A038D1E174CA90BE3035677D9DE81A89B72383EEEEA | sha512: AADDE1D149A3EE44408560D33B6BA5B7D1A0535813967EE02F8D25127A9ECBB0467D75D420A7BF76E66A22C16D9A177324A4E4873B706ED55C11A3ABF1EBD300

tools\pbm.exe.config

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
  </startup>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Bcl.AsyncInterfaces" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-8.0.0.0" newVersion="8.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Extensions.ObjectPool" publicKeyToken="adb9793829ddae60" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.36.0" newVersion="6.0.36.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Collections.Immutable" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.1" newVersion="6.0.0.1" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Configuration.ConfigurationManager" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.1" newVersion="6.0.0.1" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Data.Common" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Diagnostics.StackTrace" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Diagnostics.Tracing" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Globalization.Extensions" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.IO.Compression" publicKeyToken="b77a5c561934e089" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Net.Sockets" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime.Serialization.Primitives" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Security.Cryptography.Algorithms" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.3.0.0" newVersion="4.3.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Security.SecureString" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Threading.Overlapped" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Xml.XPath.XDocument" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

tools\Petabridge.Cmd.Common.dll

md5: D47807385624B20D8CB400D8281C4E6B | sha1: D77874BE149A70D788336D54AF4E02A7ADBD74AE | sha256: 429E967FB0EBF0BF92EE141A088C353461B0D0A0EA42F986C149A5350AE28A09 | sha512: 418E1FF318F287E3046FD52B0A0560B907A8CC27BC9B310CCCD97F0E84FCB42C06D4C7A98DB3126A73957C559D210E7BDC4838CEA71498B5F7AC2190C66F03E0

tools\Petabridge.Cmd.Common.xml

<?xml version="1.0"?>
<doc>
    <assembly>
        <name>Petabridge.Cmd.Common</name>
    </assembly>
    <members>
        <member name="T:Petabridge.Cmd.Common.ArgumentsExtractor">
            <summary>
                Utility class for simplifying the process of extracting <see cref="T:Petabridge.Cmd.CommandArgument" />s
                from a <see cref="T:Petabridge.Cmd.Command" /> received by the server.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Common.ArgumentsExtractor.ExtractArgs(Petabridge.Cmd.CommandDefinition,Petabridge.Cmd.Command)">
            <summary>
                For a given <see cref="T:Petabridge.Cmd.CommandDefinition" />, extract all of the arguments from a <see cref="T:Petabridge.Cmd.Command" />
                of the same type and return them into an easily accessible <see cref="T:Petabridge.Cmd.Common.ParsedArguments" /> collection.
            </summary>
            <param name="definition">The command definition.</param>
            <param name="cmd">The command of the same type as [definition].</param>
            <returns>A <see cref="T:Petabridge.Cmd.Common.ParsedArguments" /> collection.</returns>
        </member>
        <member name="T:Petabridge.Cmd.Common.ParsedArguments">
            <summary>
                A set of parsed arguments from a <see cref="T:Petabridge.Cmd.Command" /> given its <see cref="T:Petabridge.Cmd.CommandDefinition" />.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Common.ParsedArguments.IsArgumentSet(System.String)">
            <summary>
                Check to see if this argument was set.
            </summary>
            <param name="argumentName">The name of the argument.</param>
            <returns><c>true</c> if this argument was set at all, <c>false</c> otherwise.</returns>
        </member>
        <member name="M:Petabridge.Cmd.Common.ParsedArguments.ArgumentValues(System.String)">
            <summary>
                Retrieve the values for the provided argument.
            </summary>
            <param name="argumentName">The name of the argument.</param>
            <returns>If the argument was not set by this <see cref="T:Petabridge.Cmd.Command" />, we will return an empty <see cref="T:System.Collections.Generic.List`1" />.</returns>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.CommandSession">
            <summary>
            Payload sent by a <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> when interfacing with a Petabridge.Cmd host.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Client.CommandSession.Stream">
             <summary>
             The set of results produced by the server.
            
             The materialized <see cref="T:System.Threading.Tasks.Task"/> will complete once
             the server has completed the response stream for this command instance.
             </summary>
             <remarks>
             See https://getakka.net/articles/streams/modularitycomposition.html#materialized-values for details
             on Akka.Streams materialization
             </remarks>
        </member>
        <member name="P:Petabridge.Cmd.Common.Client.CommandSession.KillSwitch">
            <summary>
            A kill switch that can be used to terminate this stream in the event that the client no longer
            wishes to receive any commands from the server.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.IPbmClient">
            <summary>
            Represents a programmatic interface for working with a Petabridge.Cmd host.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Client.IPbmClient.IsAvailable">
            <summary>
            When <c>true</c>, our connection to the Petabridge.Cmd host should be healthy.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.IPbmClient.GetAvailablePalettes">
            <summary>
            Queries the set of <see cref="T:Petabridge.Cmd.CommandPalette"/>s supported by this client.
            </summary>
            <returns>
            An enumerable containing all of the palettes that are available to this client.
            </returns>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.IPbmClient.ExecuteTextCommandAsync(System.String)">
             <summary>
             Invokes a command on the server and returns an Akka.Streams <see cref="T:Akka.Streams.ISourceRef`1"/>,
             which can be used to construct an Akka.Streams graph locally on the client.
            
             Some requests will return a stream of responses. Others will return a single response
             and the stream will complete immediately.
             </summary>
             <param name="cliText">The raw text of the pbm command - identical to what you would type on the commandline.</param>
             <returns>A <see cref="T:Petabridge.Cmd.Common.Client.CommandSession"/></returns>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.IPbmClient.ExecuteTextCommandAsync(System.String,System.Threading.CancellationToken)">
            <summary>
            Invokes a command on the server and returns an Akka.Streams <see cref="T:Akka.Streams.ISourceRef`1"/>,
            which can be used to construct an Akka.Streams graph locally on the client.
            
            Some requests will return a stream of responses. Others will return a single response
            and the stream will complete immediately.
            </summary>
            <param name="cliText">The raw text of the pbm command - identical to what you would type on the commandline.</param>
            <param name="token">CancellationToken support.</param>
            <returns>A <see cref="T:Petabridge.Cmd.Common.Client.CommandSession"/></returns>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.IPbmClient.ExecuteTextCommandAsync(Petabridge.Cmd.Command)">
             <summary>
             Invokes a command on the server and returns an Akka.Streams <see cref="T:Akka.Streams.ISourceRef`1"/>,
             which can be used to construct an Akka.Streams graph locally on the client.
            
             Some requests will return a stream of responses. Others will return a single response
             and the stream will complete immediately.
             </summary>
             <param name="cliText">A pre-tokenized <see cref="T:Petabridge.Cmd.Command"/>.</param>
             <returns>A <see cref="T:Petabridge.Cmd.Common.Client.CommandSession"/></returns>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.IPbmClient.ExecuteTextCommandAsync(Petabridge.Cmd.Command,System.Threading.CancellationToken)">
             <summary>
             Invokes a command on the server and returns an Akka.Streams <see cref="T:Akka.Streams.ISourceRef`1"/>,
             which can be used to construct an Akka.Streams graph locally on the client.
            
             Some requests will return a stream of responses. Others will return a single response
             and the stream will complete immediately.
             </summary>
             <param name="cliText">A pre-tokenized <see cref="T:Petabridge.Cmd.Command"/>.</param>
             <param name="token">CancellationToken support.</param>
             <returns>A <see cref="T:Petabridge.Cmd.Common.Client.CommandSession"/></returns>
        </member>
        <member name="P:Petabridge.Cmd.Common.Client.IPbmClient.WhenClosed">
            <summary>
            A <see cref="T:System.Threading.Tasks.Task"/> that completes when the client has been terminated.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.IPbmClient.CloseAsync">
            <summary>
            Asynchronously dispose the client.
            </summary>
            <returns>A <see cref="T:System.Threading.Tasks.Task"/> that completes when the client has been terminated.</returns>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.LocalActorClient">
            <summary>
            Used to implement an in-process client for the PetabridgeCmd plugin on the host.
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Client.LocalActorClient._activeSession">
            <summary>
            all of our active command sessions with the server
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.LocalPbmClient">
            <summary>
            In-process <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> implementation.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PbmClientClosedException">
            <summary>
            Exception thrown when attempting to invoke a command on a <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/>
            that is currently closed.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PbmClientProtocol">
            <summary>
            INTERNAL API
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PbmClientProtocol.LaunchClient">
            <summary>
            Used to create a new client instance on the server
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PbmClientProtocol.ClientOpen">
            <summary>
            Response to a <see cref="T:Petabridge.Cmd.Common.Client.PbmClientProtocol.LaunchClient"/> request.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Client.PbmClientProtocol.ClientOpen.ServerHandlerActor">
            <summary>
            The actor that will be handling all of our requests on the server.
            </summary>
            <remarks>
            Might be an actor running in-process on the server, might be an Akka.IO TCP client
            running on the client.
            </remarks>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PbmClientProtocol.RequestPalettes">
            <summary>
            Used to request a set of available palettes
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PbmClientProtocol.InvokeRawCommand">
            <summary>
            Used to invoke a non-parsed CLI command
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PbmClientProtocol.InvokeParsedCommand">
            <summary>
            Used to invoke a parsed command
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PbmClientProtocol.CloseSession">
             <summary>
             Indicates that a particular SessionId has been closed.
            
             TODO: need a server-side version of this message for when a client terminates a session
             </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PetabridgeCmdClient">
            <summary>
            <see cref="T:Akka.Actor.ActorSystem"/> extension for creating remote <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> instances.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.PetabridgeCmdClient.Get(Akka.Actor.ActorSystem)">
            <summary>
                Retrieves the instance of the <see cref="!:PetabridgeCmd" />
                plugin for a given <see cref="T:Akka.Actor.ActorSystem" />.
            </summary>
            <param name="sys">The actor system that this petabridge.cmd host will run on.</param>
            <returns>A singleton instance of the petabridge.cmd host.</returns>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.PetabridgeCmdClient.StartRemoteClient(System.Net.EndPoint,System.Threading.CancellationToken)">
            <summary>
            Starts a remote <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> that can be used to interact programmatically with a <see cref="!:PetabridgeCmd"/> instance
            running on a remote host.
            
            This client can be used over and over again until <see cref="P:Petabridge.Cmd.Common.Client.IPbmClient.IsAvailable"/> is no longer <c>true</c>, which happens when
            the <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> is disposed or when the actors it depends upon are terminated, typically via <see cref="T:Akka.Actor.ActorSystem"/>
            termination or when the remote TCP connection is closed.
            </summary>
            <param name="pbmHost">A <see cref="T:System.Net.DnsEndPoint"/> or <see cref="T:System.Net.IPEndPoint"/> that contains an open <see cref="!:PetabridgeCmd"/> host.</param>
            <param name="token">A cancellation token</param>
            <returns>A remote <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> instance.</returns>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.PetabridgeCmdClient.StartRemoteClient(System.Net.EndPoint)">
            <summary>
            Starts a remote <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> that can be used to interact programmatically with a <see cref="!:PetabridgeCmd"/> instance
            running on a remote host.
            
            This client can be used over and over again until <see cref="P:Petabridge.Cmd.Common.Client.IPbmClient.IsAvailable"/> is no longer <c>true</c>, which happens when
            the <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> is disposed or when the actors it depends upon are terminated, typically via <see cref="T:Akka.Actor.ActorSystem"/>
            termination or when the remote TCP connection is closed.
            </summary>
            <param name="pbmHost">A <see cref="T:System.Net.DnsEndPoint"/> or <see cref="T:System.Net.IPEndPoint"/> that contains an open <see cref="!:PetabridgeCmd"/> host.</param>
            <returns>A remote <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> instance.</returns>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.PetabridgeCmdClientExtension">
            <summary>
                INTERNAL API.
                Defines the <see cref="T:Petabridge.Cmd.Common.Client.PetabridgeCmdClient" /> plugin used directly be end-users.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.RemoteActorClient">
             <summary>
             INTERNAL API
            
             Uses Akka.IO TCP to communicate with a remote PbmClient.
             </summary>
             <remarks>
             Primarily built 
             </remarks>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.RemoteActorClient.Shutdown">
            <summary>
            INTERNAL API - used to shutdown the client from the client side.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.RemoteActorClient.PbmAck">
            <summary>
            Used to Ack / Nak a specific command
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Client.RemoteActorClient.Encoder">
            <summary>
                Note: stateful. Definitely do not make static.
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Client.RemoteActorClient._connection">
            <summary>
            The TcpConnection actor from Akka.IO
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Client.RemoteActorClient._commandHandler">
            <summary>
            <see cref="T:Petabridge.Cmd.Common.Client.LocalActorClient"/>, which handles all of the underlying commands.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.RemoteClientRoot">
             <summary>
             INTERNAL API
            
             Root actor for managing all remote client Tcp sessions
             </summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Client.RemoteClientRoot.OpenRemoteSession.EndPoint">
            <summary>
            The remote endpoint we're going to connect to
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Client.RemoteClientRoot.OpenRemoteSession.Connected">
            <summary>
            TCS that will get completed once we've successfully connected to the server
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.RemotePbmClient">
            <summary>
            Remote <see cref="T:Petabridge.Cmd.Common.Client.IPbmClient"/> implementation. Connects over Akka.IO.Tcp, just like the `pbm` CLI.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.Stages.ShutdownFlows">
            <summary>
            INTERNAL API
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Common.Client.Stages.ShutdownFlows.TerminateWhen``1(System.Predicate{``0})">
            <summary>
            Creates a new <see cref="T:Petabridge.Cmd.Common.Client.Stages.TerminateWhenStage`1"/> that will signal downstream Akka.Streams termination
            whenever terminateWhenTrue returns <c>true</c>.
            </summary>
            <param name="terminateWhenTrue">The filter predicate - as soon as this returns true, the stage will emit the last queued
            elements and terminate.</param>
            <typeparam name="TIn">The type of element</typeparam>
            <returns>A new <see cref="T:Akka.Streams.Dsl.Flow"/></returns>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.Stages.TerminateWhenStage`1">
             <summary>
             INTERNAL API
            
             <see cref="T:Akka.Streams.Dsl.Flow`3"/> stage for conditional upstream termination.
             Waits for a predicate in the stream to be true, but wants to allow procesing
             of all previously received events beforehand.
             </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Client.Stages.TerminateWhenLogic`1">
            <summary>
            INTERNAL API
            </summary>
            <typeparam name="TIn"></typeparam>
        </member>
        <member name="T:Petabridge.Cmd.Common.CloseSession">
            <summary>
            Used to allow modern (1.0+) PbmClients which support concurrent sessions
            to terminate a session programmatically from the client.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.CommandFormatsReflection">
            <summary>Holder for reflection information generated from CommandFormats.proto</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandFormatsReflection.Descriptor">
            <summary>File descriptor for CommandFormats.proto</summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.Schema">
            <summary>
            Uses a schema to describe the type of data included in a response
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.Schema.Text">
            <summary>
            defaults to what we had in PBM v0.2.2
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.Schema.Tabular">
            <summary>
            tabular data pretty-printed into a grid
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.Schema.Metric">
            <summary>
            metric data used to represent samples of values
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.MetricType">
            <summary>
            The type of metric
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.PbmEnvelope">
            <summary>
            Generalized envelope class
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.PbmEnvelope.CommandDefFieldNumber">
            <summary>Field number for the "command_def" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.PbmEnvelope.CommandFieldNumber">
            <summary>Field number for the "command" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.PbmEnvelope.ResponseFieldNumber">
            <summary>Field number for the "response" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.PbmEnvelope.AllPalettesFieldNumber">
            <summary>Field number for the "all_palettes" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.PbmEnvelope.SinglePaletteFieldNumber">
            <summary>Field number for the "single_palette" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.PbmEnvelope.CloseSessionFieldNumber">
            <summary>Field number for the "close_session" field.</summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition">
            <summary>
            Defines a command that can be transmitted over the wire
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.IdFieldNumber">
            <summary>Field number for the "id" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.NameFieldNumber">
            <summary>Field number for the "name" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.DescriptionFieldNumber">
            <summary>Field number for the "description" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.TypeFieldNumber">
            <summary>Field number for the "type" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.ArgumentsFieldNumber">
            <summary>Field number for the "arguments" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.Arguments">
            <summary>
            the set of arguments
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.TableDefFieldNumber">
            <summary>Field number for the "table_def" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.TableDef">
            <summary>
            If this is tabular data, define the columns here
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.MetricDefFieldNumber">
            <summary>Field number for the "metric_def" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandDefinition.MetricDef">
            <summary>
            If this is metric data, define the type here
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.AllPalettes">
            <summary>
            Represents an IEnumerable&lt;CommandPalette>
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.AllPalettes.PalettesFieldNumber">
            <summary>Field number for the "palettes" field.</summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.CommandPalette">
            <summary>
            Defines a command palette
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandPalette.ModuleNameFieldNumber">
            <summary>Field number for the "module_name" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandPalette.CommandsFieldNumber">
            <summary>Field number for the "commands" field.</summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.TableDefinition">
            <summary>
            Defines the schema of a table
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.TableDefinition.ColumnsFieldNumber">
            <summary>Field number for the "columns" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.MetricDefinition.MetricNameFieldNumber">
            <summary>Field number for the "metric_name" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.MetricDefinition.TypeFieldNumber">
            <summary>Field number for the "type" field.</summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition">
            <summary>
            Defines an argument for a command
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition.NameFieldNumber">
            <summary>Field number for the "name" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition.DescriptionFieldNumber">
            <summary>Field number for the "description" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition.SwitchesFieldNumber">
            <summary>Field number for the "switches" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition.Switches">
            <summary>
            the set of switches, ala "-s", "-S"
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition.IsMandatoryFieldNumber">
            <summary>Field number for the "is_mandatory" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition.IsFlagFieldNumber">
            <summary>Field number for the "is_flag" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition.AllowMultipleFieldNumber">
            <summary>Field number for the "allow_multiple" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition.DefaultValuesFieldNumber">
            <summary>Field number for the "default_values" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandArgumentDefinition.DefaultValues">
            <summary>
            , the set of repeated values
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse">
            <summary>
            Defines a response to a command
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.IdFieldNumber">
            <summary>Field number for the "id" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.IsErrorFieldNumber">
            <summary>Field number for the "is_error" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.EndFieldNumber">
            <summary>Field number for the "end" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.TypeFieldNumber">
            <summary>Field number for the "type" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.StructuredDataFieldNumber">
            <summary>Field number for the "structured_data" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.TextDataFieldNumber">
            <summary>Field number for the "text_data" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.TextData">
            <summary>
            populated only if this message is a TEXT type
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.TblDataFieldNumber">
            <summary>Field number for the "tbl_data" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.TblData">
            <summary>
            populated only if this message is a TABULAR type
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.MetricDataFieldNumber">
            <summary>Field number for the "metric_data" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.MetricData">
            <summary>
            populated only if message is a METRIC type
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.SessionIdFieldNumber">
            <summary>Field number for the "session_id" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.SessionId">
            <summary>
            used to correlate requests back to a specific session id
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.Types">
            <summary>Container for nested types declared in the CommandResponse message type.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.Types.DataItem.KeyFieldNumber">
            <summary>Field number for the "key" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandResponse.Types.DataItem.ValuesFieldNumber">
            <summary>Field number for the "values" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.TextData.MsgFieldNumber">
            <summary>Field number for the "msg" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.TextData.Msg">
            <summary>
            the text-based message
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.TabularData.RowsFieldNumber">
            <summary>Field number for the "rows" field.</summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.TabularData.Types">
            <summary>Container for nested types declared in the TabularData message type.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.TabularData.Types.TabularDataRow.ColumnsFieldNumber">
            <summary>Field number for the "columns" field.</summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.MetricData">
            <summary>
            The metric payload
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.MetricData.TypeFieldNumber">
            <summary>Field number for the "type" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.MetricData.TimestampFieldNumber">
            <summary>Field number for the "timestamp" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.MetricData.Timestamp">
            <summary>
            used for timer types
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.MetricData.CounterValueFieldNumber">
            <summary>Field number for the "counter_value" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.MetricData.CounterValue">
            <summary>
            used for counter types
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.MetricData.GaugeValueFieldNumber">
            <summary>Field number for the "gauge_value" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.MetricData.GaugeValue">
            <summary>
            used for gauge types
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.Command">
            <summary>
            Invokes a command over the network
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.Command.ModuleFieldNumber">
            <summary>Field number for the "module" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.Command.NameFieldNumber">
            <summary>Field number for the "name" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.Command.ArgumentsFieldNumber">
            <summary>Field number for the "arguments" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.Command.SessionIdFieldNumber">
            <summary>Field number for the "session_id" field.</summary>
        </member>
        <member name="P:Petabridge.Cmd.Common.Serialization.Msg.Command.SessionId">
            <summary>
            used to split response streams into multiple concurrent instances
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandArgument.SwitchFieldNumber">
            <summary>Field number for the "switch" field.</summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CommandArgument.ValueFieldNumber">
            <summary>Field number for the "value" field.</summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Serialization.Msg.CloseSession">
            <summary>
            used to close a CommandSession from the client-side
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Common.Serialization.Msg.CloseSession.SessionIdFieldNumber">
            <summary>Field number for the "session_id" field.</summary>
        </member>
        <member name="T:Petabridge.Cmd.Common.Util.NoLogEnvelope`1">
            <summary>
                INTERNAL API.
                Used to prevent recursive logging during tails.
            </summary>
            <typeparam name="T">The type of message we won't log while writing to network.</typeparam>
        </member>
        <member name="T:Petabridge.Cmd.HelpCommand">
            <summary>
                Special case. Used to print help instructions for the specified command
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.InvokeCommand">
            <summary>
            Used to invoke a command with a specific sessionId.
            </summary>
            <remarks>
            Implemented as a <see cref="P:Petabridge.Cmd.InvokeCommand.Command"/> for backwards compatibility with actors.
            </remarks>
        </member>
        <member name="T:Petabridge.Cmd.Command">
            <summary>
                A command to be sent to the server for processing
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Command.Empty">
            <summary>
                Special case for unparseable commands
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Command.#ctor(System.String,System.String,System.Collections.Generic.IEnumerable{System.Tuple{System.String,System.String}})">
            <summary>
                Creates a new instance of a command for processing.
            </summary>
            <param name="module">The module (or palette) that defines this command.</param>
            <param name="name">The command name itself.</param>
            <param name="arguments">The set of provided arguments.</param>
        </member>
        <member name="P:Petabridge.Cmd.Command.Module">
            <summary>
                The name of the command palette for this argument.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Command.Name">
            <summary>
                The name of the command being executed.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Command.Arguments">
            <summary>
                The set of arguments associated with this command.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Command.WithSessionId(System.Int64)">
            <summary>
            INTERNAL API.
            </summary>
            <param name="sessionId">The id of the session correlated with this command.</param>
            <returns></returns>
        </member>
        <member name="T:Petabridge.Cmd.CommandBuilder">
            <summary>
                Fluent DSL for building <see cref="T:Petabridge.Cmd.Command" /> objects.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.CommandDefinition">
            <summary>
                Describes the lexical structure of a command.
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.CommandDefinition.BuiltIn">
            <summary>
                INTERNAL API.
                Used to signal that this is a built-in command,
                which receives special case treatment from the parsing,
                help, and validation systems.
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.CommandDefinition.WhiteSpaceDetector">
            <summary>
                INTERNAL API.
                Used to validate that there's no whitespace in any command names, per
                https://github.com/petabridge/petabridge.cmd-issues/issues/14
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.CommandDefinition.#ctor(System.String,System.String,System.Collections.Generic.IEnumerable{Petabridge.Cmd.CommandArgument})">
            <summary>
                Creates a new command definition.
            </summary>
            <param name="name">The name of the command.</param>
            <param name="description">The human-readable description of the command.</param>
            <param name="arguments">The arguments provided.</param>
        </member>
        <member name="T:Petabridge.Cmd.CommandArgument">
            <summary>
                Defines an argument for a <see cref="T:Petabridge.Cmd.CommandDefinition" />
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.CommandArgument.#ctor(System.String,System.String[],System.String,System.Boolean,System.Boolean,System.Boolean,System.String[])">
            <summary>
                Creates a new <see cref="T:Petabridge.Cmd.CommandArgument" />.
            </summary>
            <param name="name">The human friendly name of the command argument.</param>
            <param name="switches">The set of switches used for command on the commandline itself.</param>
            <param name="description">Human friendly description of the commandline argument.</param>
            <param name="mandatory">Determines if this is a required argument or not.</param>
            <param name="allowMultiple">Determiens if there can be mulitple instances of this argument or not.</param>
            <param name="isFlag">Indicates of this argument requires a value or not. If not, then this is treated as a flag.</param>
            <param name="defaultValues">Optional. The set of default values that can be provided to an argument.</param>
        </member>
        <member name="P:Petabridge.Cmd.CommandArgument.Mandatory">
            <summary>
                If <c>true</c>, then the <see cref="T:Petabridge.Cmd.Command" /> who depends on this will fail if this value is not provided.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandArgument.Name">
            <summary>
                Human-readable property name
            </summary>
            <example>
                address
                host
            </example>
        </member>
        <member name="P:Petabridge.Cmd.CommandArgument.Switch">
            <summary>
                The switches used to identify the command on the commandline itself.
            </summary>
            <example>
                -a | -A
            </example>
            <remarks>This can be <c>null</c> if the command is mandatory.</remarks>
        </member>
        <member name="P:Petabridge.Cmd.CommandArgument.AllowMultiple">
            <summary>
                If <c>true</c>, allows this argument to be used multiple times.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandArgument.Description">
            <summary>
                The description for this command. Will be printed out during HELP commands.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandArgument.DefaultValues">
            <summary>
                Optional. Represents a range of possible default values. Mostly used by tab autocompletion.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandArgument.IsFlag">
            <summary>
                If <c>true</c>, then this argument requires a value. If not, then this argument acts just like a flag.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.ArgumentDefinitionBuilder">
            <summary>
                Fluent DSL used for creating arguments for Akka commands we're defining.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.CommandDefinitionBuilder">
            <summary>
                Fluent DSL for creating new <see cref="T:Petabridge.Cmd.CommandDefinition" />s.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.CommandHelp">
            <summary>
                Prints out help information for a <see cref="T:Petabridge.Cmd.CommandPalette" />
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandHelp.Palette">
            <summary>
                The palette for this <see cref="T:Petabridge.Cmd.CommandHelp" />
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.CommandPalette">
            <summary>
                The range of commands supported by a given module.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.CommandParser">
            <summary>
                Parses a space-delimited string into a structured <see cref="T:Petabridge.Cmd.Command" /> object
                for a specific <see cref="T:Petabridge.Cmd.CommandPalette" />.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandParser.Palette">
            <summary>
                The set of commands supported by this parser.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandParser.Validator">
            <summary>
                The validator for this parser.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.CommandParser.Parse(System.String)">
            <summary>
            Parses a full command-line argument into its resultant parts.
            </summary>
            <param name="commandLine">The commandline to tokenize.</param>
            <returns>
                A <see cref="T:Petabridge.Cmd.ParseResult" /> structure indicating if the object was
                correctly formed into a valid, recognizable <see cref="T:Petabridge.Cmd.Command" />
                belonging to this <see cref="T:Petabridge.Cmd.CommandPalette" />.
            </returns>
        </member>
        <member name="M:Petabridge.Cmd.CommandParser.Parse(System.String[])">
            <summary>
                Parses an incoming string into a <see cref="T:Petabridge.Cmd.Command" /> belonging to <see cref="P:Petabridge.Cmd.CommandParser.Palette" />.
            </summary>
            <param name="args">Tokenized commandline arguments</param>
            <returns>
                A <see cref="T:Petabridge.Cmd.ParseResult" /> structure indicating if the object was
                correctly formed into a valid, recognizable <see cref="T:Petabridge.Cmd.Command" />
                belonging to this <see cref="T:Petabridge.Cmd.CommandPalette" />.
            </returns>
        </member>
        <member name="T:Petabridge.Cmd.ErroredCommandResponse">
            <summary>
                Special case for error messages.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.CommandResponse">
            <summary>
                Message sent in response to a <see cref="T:Petabridge.Cmd.Command" /> by an petabridge.cmd host.
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.CommandResponse.Empty">
            <summary>
                Special case. Used to terminate a response stream.
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.CommandResponse.EmptyStructuredData">
            <summary>
                A default, empty value for structured data.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.CommandResponse.#ctor(System.String,System.Boolean,System.Collections.Generic.IReadOnlyDictionary{System.String,System.String[]})">
            <summary>
                Creates a new command response object.
            </summary>
            <param name="msg">The message from the server.</param>
            <param name="final">If <c>true</c>, indicates that the server is done sending responses for this particular request.</param>
            <param name="structuredData">Semantic data that can be used by the client for other types of rich response formatting.</param>
        </member>
        <member name="M:Petabridge.Cmd.CommandResponse.#ctor(System.String,System.Int64,System.Boolean,System.Collections.Generic.IReadOnlyDictionary{System.String,System.String[]})">
            <summary>
                Creates a new command response object.
            </summary>
            <param name="msg">The message from the server.</param>
            <param name="sessionId">The id of the client session this request is correlated to.</param>
            <param name="final">If <c>true</c>, indicates that the server is done sending responses for this particular request.</param>
            <param name="structuredData">Semantic data that can be used by the client for other types of rich response formatting.</param>
        </member>
        <member name="P:Petabridge.Cmd.CommandResponse.CommandType">
            <summary>
                Defines the schema used for the formatting of this command
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandResponse.Msg">
            <summary>
                The raw message that will be printed back onto the console
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandResponse.StructuredData">
            <summary>
                Optional. A string dictionary containing structured data that can be formatted and used by clients
                in more semantically-friendly ways.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandResponse.Final">
            <summary>
                For streaming responses, indicates that this is the final message in the stream
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandResponse.SessionId">
            <summary>
            The id of the client session correlated with this response.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandResponse.IsSpecial">
            <summary>
                Indicates that this is a special message which has built-in handlers on the client.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.CommandResponse.IsError">
            <summary>
                Indicates that this is an error message
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.CommandResponse.WithSessionId(System.Int64)">
            <summary>
            Creates a new copy of this <see cref="T:Petabridge.Cmd.CommandResponse"/> with a new SessionId.
            </summary>
            <param name="sessionId"></param>
            <returns></returns>
        </member>
        <member name="T:Petabridge.Cmd.CommandSwitch">
            <summary>
                Used to indicate the different ways a command can be called on the commandline.
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.CommandSwitch.Empty">
            <summary>
                An empty <see cref="T:Petabridge.Cmd.CommandSwitch" /> instance.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.CommandSwitch.#ctor(System.Collections.Generic.IEnumerable{System.String})">
            <summary>
                Creates a new <see cref="T:Petabridge.Cmd.CommandSwitch" /> based on a list of provided switches.
            </summary>
            <param name="switches">The set of provided switches.</param>
        </member>
        <member name="M:Petabridge.Cmd.CommandSwitch.#ctor(System.Collections.Generic.HashSet{System.String})">
            <summary>
                Creates a new <see cref="T:Petabridge.Cmd.CommandSwitch" /> based on a list of provided switches.
            </summary>
            <param name="switches">The set of provided switches.</param>
        </member>
        <member name="P:Petabridge.Cmd.CommandSwitch.Switches">
            <summary>
                The set of switches supported by this command.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.CommandSwitch.Contains(System.String)">
            <summary>
                Check to see if this <see cref="T:Petabridge.Cmd.CommandSwitch" /> contains an individual switch value.
            </summary>
            <param name="s">The switch value to check.</param>
            <returns><c>true</c> if this switch is contained.</returns>
        </member>
        <member name="M:Petabridge.Cmd.CommandSwitch.Overlap(Petabridge.Cmd.CommandSwitch)">
            <summary>
                Check to see if two switches overlap with each other.
            </summary>
            <param name="other">The other <see cref="T:Petabridge.Cmd.CommandSwitch" /> to check.</param>
            <returns>The set of overlapping values.</returns>
        </member>
        <member name="T:Petabridge.Cmd.CommandType">
            <summary>
                Defines the output response type produced when invoking a particular <see cref="T:Petabridge.Cmd.Command" />
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.ParsePart">
            <summary>
                INTERNAL API.
                Used by the parser to determine which stage it's at in the course
                of parsing a command string.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.ParseResult">
            <summary>
                The result of a parsing operation.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.ParseResult.Parts">
            <summary>
                Internal API. Lists the semantic parts of the string as they were parsed.
            </summary>
            <remarks>
                Used by autocomplete.
            </remarks>
        </member>
        <member name="T:Petabridge.Cmd.Serialization.MessageEncoder">
            <summary>
                INTERNAL API. Used for framing outgoing messages.
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Serialization.MessageEncoder.MessageLengthHeaderSize">
            <summary>
                We use a 4 byte header
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Serialization.MessageEncoder.Encode(System.Byte[])">
            <summary>
                Frame a single message
            </summary>
            <param name="bytes">The raw message bytes.</param>
            <returns>A bytestring with length frame headers.</returns>
        </member>
        <member name="M:Petabridge.Cmd.Serialization.MessageEncoder.Decode(Akka.IO.ByteString)">
            <summary>
                Decode an incoming message and produce 0 or more messages depending on header values.
            </summary>
            <param name="byteString">The incoming data.</param>
            <returns>0 or more individually framed messages.</returns>
        </member>
        <member name="T:Petabridge.Cmd.Util.CircularBuffer`1">
            <summary>
                Base class for working with circular buffers
            </summary>
            <typeparam name="T">The type being stored in the circular buffer</typeparam>
        </member>
        <member name="F:Petabridge.Cmd.Util.CircularBuffer`1._head">
            <summary>
                Front of the buffer
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Util.CircularBuffer`1._tail">
            <summary>
                Back of the buffer
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Util.CircularBuffer`1.Buffer">
            <summary>
                The buffer itself
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Util.CircularBuffer`1.Head">
            <summary>
                FOR TESTING PURPOSES ONLY
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Util.CircularBuffer`1.Tail">
            <summary>
                FOR TESTING PURPOSES ONLY
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Util.CircularBuffer`1.CopyTo(`0[])">
            <summary>
                Copies the contents of the Circular Buffer into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.CircularBuffer`1.CopyTo(`0[],System.Int32)">
            <summary>
                Copies the contents of the Circular Buffer into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
            <param name="index">The starting index for copying in the destination array</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.CircularBuffer`1.CopyTo(`0[],System.Int32,System.Int32)">
            <summary>
                Copies the contents of the Circular Buffer into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
            <param name="index">The starting index for copying in the destination array</param>
            <param name="count">The number of items to copy from the current buffer (max value = current Size of buffer)</param>
        </member>
        <member name="T:Petabridge.Cmd.Util.CircularIterator`1">
            <summary>
                INTERNAL API
                Used to iterate in a circular fashion around an <see cref="T:System.Collections.Generic.IEnumerable`1" />
            </summary>
            <remarks>
                Used for circular tab autocomplete.
            </remarks>
        </member>
        <member name="M:Petabridge.Cmd.Util.CircularIterator`1.MoveBack">
            <summary>
                Allows the iterator to move backwards all the way back to its starting position
            </summary>
            <returns><c>true</c> if we're able to move backwards, <c>false</c> otherwise</returns>
        </member>
        <member name="T:Petabridge.Cmd.Util.ConsoleExtensions">
            <summary>
                INTERNAL API
            </summary>
            <remarks>
                Used to help create text-wrappable columns for printing on the console.
            </remarks>
        </member>
        <member name="T:Petabridge.Cmd.Util.EndpointParser">
            <summary>
                INTERNAL API.
                Designed to help extract IP address and port from startup arguments
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Util.EndpointParser.TryParse(System.String,System.Net.EndPoint@)">
            <summary>
               Attempt to parse the string into an <see cref="T:System.Net.IPEndPoint" /> or <see cref="T:System.Net.DnsEndPoint" />
            </summary>
            <param name="endPoint">The endpoint we'll be using.</param>
            <param name="ep">
                An <see cref="T:System.Net.IPEndPoint" /> or <see cref="T:System.Net.DnsEndPoint" /> if endpoint is a valid address.
                Otherwise <c>null</c>.</param>
            <returns>
               <c>true</c> if the parse was successful, <c>false</c> otherwise.
            </returns>
        </member>
        <member name="M:Petabridge.Cmd.Util.EndpointParser.Parse(System.String)">
            <summary>
                Parses the string into an <see cref="T:System.Net.IPEndPoint" /> or <see cref="T:System.Net.DnsEndPoint" />
            </summary>
            <param name="endPoint">The endpoint we'll be using.</param>
            <returns>
                An <see cref="T:System.Net.IPEndPoint" /> or <see cref="T:System.Net.DnsEndPoint" /> if endpoint is a valid address.
                Otherwise <c>null</c>.
            </returns>
        </member>
        <member name="T:Petabridge.Cmd.Util.FixedSizeStack`1">
            <summary>
                Stack with a fixed size number of members - old items get pushed
                off the stack
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Util.FixedSizeStack`1.DEFAULT_CAPACITY">
            <summary>
                Default capacity for fixed size stacks
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Util.FixedSizeStack`1._buffer">
            <summary>
                The buffer itself
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Util.FixedSizeStack`1.CopyTo(`0[],System.Int32,System.Int32)">
            <summary>
                Copies the contents of the FixedSizeStack into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
            <param name="index">The starting index for copying in the destination array</param>
            <param name="count">The number of items to copy from the current buffer (max value = current Size of buffer)</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.FixedSizeStack`1.CopyTo(`0[])">
            <summary>
                Copies the contents of the FixedSizeStack into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.FixedSizeStack`1.CopyTo(`0[],System.Int32)">
            <summary>
                Copies the contents of the FixedSizeStack into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
            <param name="index">The starting index for copying in the destination array</param>
        </member>
        <member name="P:Petabridge.Cmd.Util.ICircularBuffer`1.Capacity">
            <summary>
                The gets the max capacity of the buffer
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Util.ICircularBuffer`1.Size">
            <summary>
                The current size of the buffer.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Util.ICircularBuffer`1.Peek">
            <summary>
                Peeks at the next message in the buffer
            </summary>
            <returns>The object at the start position of the buffer</returns>
        </member>
        <member name="M:Petabridge.Cmd.Util.ICircularBuffer`1.Enqueue(`0)">
            <summary>
                Adds an object to the end of the circular buffer
            </summary>
            <param name="obj">An object of type T</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.ICircularBuffer`1.Enqueue(`0[])">
            <summary>
                Adds an array of objects to the end of the circular buffer
            </summary>
            <param name="objs">An array of objects of type T</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.ICircularBuffer`1.Dequeue">
            <summary>
                Dequeues an object from the start of the circular buffer
            </summary>
            <returns>An object of type T</returns>
        </member>
        <member name="M:Petabridge.Cmd.Util.ICircularBuffer`1.Dequeue(System.Int32)">
            <summary>
                Dequeues multiple items at once, if available
            </summary>
            <param name="count">The maximum number of items to dequeue</param>
            <returns>An enumerable list of items</returns>
        </member>
        <member name="M:Petabridge.Cmd.Util.ICircularBuffer`1.DequeueAll">
            <summary>
                Dequeues the entire buffer in one dump
            </summary>
            <returns>All of the active contents of a circular buffer</returns>
        </member>
        <member name="M:Petabridge.Cmd.Util.ICircularBuffer`1.Clear">
            <summary>
                Clears the contents from the buffer
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Util.ICircularBuffer`1.CopyTo(`0[])">
            <summary>
                Copies the contents of the Circular Buffer into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.ICircularBuffer`1.CopyTo(`0[],System.Int32,System.Int32)">
            <summary>
                Copies the contents of the Circular Buffer into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
            <param name="index">The starting index for copying in the destination array</param>
            <param name="count">The number of items to copy from the current buffer (max value = current Size of buffer)</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.IFixedSizeStack`1.CopyTo(`0[],System.Int32,System.Int32)">
            <summary>
                Copies the contents of the FixedSizeStack into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
            <param name="index">The starting index for copying in the destination array</param>
            <param name="count">The number of items to copy from the current buffer (max value = current Size of buffer)</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.IFixedSizeStack`1.CopyTo(`0[])">
            <summary>
                Copies the contents of the FixedSizeStack into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
        </member>
        <member name="M:Petabridge.Cmd.Util.IFixedSizeStack`1.CopyTo(`0[],System.Int32)">
            <summary>
                Copies the contents of the FixedSizeStack into a new array
            </summary>
            <param name="array">The destination array for the copy</param>
            <param name="index">The starting index for copying in the destination array</param>
        </member>
        <member name="T:Petabridge.Cmd.Util.Tokenizer">
            <summary>
                INTERNAL API
                Used for parsing command line arguments while preserving quoted strings as single arguments
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Util.Tokenizer.Regex">
            <summary>
            Matches singly quoted, doubly quoted, and unquoted strings separated by spaces.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Util.Tokenizer.Tokenize(System.String)">
            <summary>
                Tokenizes a string and splits it via spaces while stripping trailing and leading quotes.
            </summary>
            <param name="raw">The raw input string.</param>
            <returns>The tokenized output.</returns>
        </member>
        <member name="M:Petabridge.Cmd.Util.Tokenizer.TokenizePreserveQuotes(System.String)">
            <summary>
                Tokenizes a string and splits it via spaces while preserving quotes
            </summary>
            <param name="raw">The raw input string.</param>
            <returns>The tokenized output.</returns>
            <remarks>Used primarily by the autocomplete engine.</remarks>
        </member>
        <member name="T:Petabridge.Cmd.Validation.CommandValidator">
            <summary>
                Validates a given <see cref="T:Petabridge.Cmd.Command" /> against a <see cref="T:Petabridge.Cmd.CommandDefinition" />
                to see if there's any errors with the structure before passing it up to the server for processing.
            </summary>
        </member>
        <member name="M:Petabridge.Cmd.Validation.CommandValidator.#ctor(Petabridge.Cmd.CommandPalette)">
            <summary>
                Creates a new <see cref="T:Petabridge.Cmd.Validation.CommandValidator" /> instance.
            </summary>
            <param name="palette">The palette of the command we're going to validate.</param>
        </member>
        <member name="P:Petabridge.Cmd.Validation.CommandValidator.Palette">
            <summary>
                The palette of the command for which we're going to validate.
            </summary>
        </member>
        <member name="T:Petabridge.Cmd.Validation.ValidationError">
            <summary>
                Reports that there was a validation issue with a <see cref="P:Petabridge.Cmd.Validation.ValidationError.Command" />.
            </summary>
        </member>
        <member name="F:Petabridge.Cmd.Validation.ValidationError.NullCmd">
            <summary>
                Singleton used for when a null command is given.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Validation.ValidationError.Module">
            <summary>
                The module of the command / argument that failed
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Validation.ValidationError.Command">
            <summary>
                The name of the command that failed.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Validation.ValidationError.Argument">
            <summary>
                Optional. The name of the argument that failed.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Validation.ValidationError.Value">
            <summary>
                Optional. The value of the argument that failed.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Validation.ValidationError.ErrorMessage">
            <summary>
                The validation error message.
            </summary>
        </member>
        <member name="P:Petabridge.Cmd.Validation.ValidationError.HelpInfo">
            <summary>
                Optional. A help message with information on how to resolve the issue.
            </summary>
        </member>
    </members>
</doc>

tools\Reactive.Streams.dll

md5: D507938EB8ACAD306FDE66A922BC1A54 | sha1: AE0A54903F44F853AFCEC2F863A11C073CBC13B8 | sha256: DFB748806727FE261F48E15ED6C1E3AB952F7021208FEC4DF0184615BA5EC6F0 | sha512: 367D9C53CC01AE338CDFE04B0D78DF7614C923D5C8E6C27875D4611B1B32E7B5511A3748F8E7F702604C384A31B1EA95FCBF19E6F0D81AC9DF4931C2C213CEA0

tools\System.Buffers.dll

md5: ECDFE8EDE869D2CCC6BF99981EA96400 | sha1: 2F410A0396BC148ED533AD49B6415FB58DD4D641 | sha256: ACCCCFBE45D9F08FFEED9916E37B33E98C65BE012CFFF6E7FA7B67210CE1FEFB | sha512: 5FC7FEE5C25CB2EEE19737068968E00A00961C257271B420F594E5A0DA0559502D04EE6BA2D8D2AAD77F3769622F6743A5EE8DAE23F8F993F33FB09ED8DB2741

tools\System.Collections.Immutable.dll

md5: 614262AD913C42F11C6A2C0E900A2CDB | sha1: F1543A7A66FE541B6DBAEE5B45CCBC4DF48BE9AB | sha256: AED42E17B41407BE33E6B42A172A6D0FCE5C224B88DEC070284D35AAEA90B9DB | sha512: 191FA108254FFE9CB319BC2B534C80CC22A4845161D4FEB7A404DE0309D1415CABFB514316F8598D18C91D6B503EDD743B3FB55A97C995CE82BA40FA50CD2166

tools\System.Configuration.ConfigurationManager.dll

md5: 660AC998CAD361DA8BBCAE680BB2E029 | sha1: 840D997CF9705C43CD02539F338C66D035544B1C | sha256: C67DDF0AE4899E70A9CF50438F39044E18EA4B2F1D4CFD7A79B4BD32F86A1E7C | sha512: B103F192FD80875B2793FA4383731E5E2D1FD58A9760397C22566EF4EE3C19AF9C7BE4686701FC02CBA6559832EB092C41B283C5EC043FD92DEF6B51FE543AA6

tools\System.Data.Common.dll

md5: 4EC7C87D3C8820C20E8C2EF80D80D363 | sha1: 1FEABEBF78539D5E7316BC4352B4383D239FD438 | sha256: 4FE23DD147813C0B724B62FCFC0CE419E9A4AD36F3DA4CC43E5DA97D796E289E | sha512: 2504DFED8DCF4F5C1CC56CB9EBCB03833CFB6837D0592F82DBDBC28899B6F1AAE2E007E0175AD7544FF13B017F3063145E1826267A5DFAEA91BE182ACCA3C5BB

tools\System.Diagnostics.StackTrace.dll

md5: C20C268EABDCC95DA38AD646A0AA0310 | sha1: 3760E870DFCFA41071E5B39CCA59265657B3715B | sha256: E932B25F50E3B09DD7759FF5B9E9ABFA8FC115EA171B768164AE21387FEAC7E8 | sha512: 422F8F7A50F457EB979652B14A6C06A51A6A94C7EB9F56045A4B944ACBE3026580465AEFFFD9F30A4334A556FA1EED8488DB0766C16D637023E72B579A26DFCF

tools\System.Diagnostics.Tracing.dll

md5: 482573CB18B537A7415DCC00C906611D | sha1: 4377161FBD9644953471A94021DF437F21FE83E6 | sha256: D4A59FB62D8A7A138A49911110F8B2AB416196DF95F4CFC599ABB6EC61629E5E | sha512: AA96E1544FD0286FB1D6A77B8ACE8745F69EC4835CF0957C457AA3026B4AD5EC02E953C7BC106D80205109A85512D1DF99AB3DE7D41300E96858298AE5767FE5

tools\System.Globalization.Extensions.dll

md5: 8DE05921A38C0FF54E6D4B4ED0C32235 | sha1: 5BA1692964F8732D2CAAFA6A8D1009DFB8B4A764 | sha256: F690794A0296D8DAD4F30D626A8A89121DF51B5909E440DA08707B09518D040E | sha512: B7DAE61979760224EDDC28C717B78AABDCDE2C9ACD3659958041D08B44CDA12E9D62F15B436691213771A4B32714BD78D54D2BA4C90471FC7BFF4BF274C66C07

tools\System.IO.Compression.dll

md5: B2CE49C37351D7A7471CD20C9E02B6E9 | sha1: 44EB7732131B4B1B25EA8D023C3D2F544E017F24 | sha256: 76FCACCF84313BF78F523B3BC8198C2D040DABDC04A5DC863B46C8AF7AC10A88 | sha512: 40980B050861F7C4F1ED5B71F7F7FD91052FCFC1C49B7B3490D9A4FD68FEC8FD3C95AF38D113ABA8E7F1CE2B4CEADD1B6D66C5D1EA68064EC6265C266BE1AFC5

tools\System.Memory.dll

md5: 6FB95A357A3F7E88ADE5C1629E2801F8 | sha1: 19BF79600B716523B5317B9A7B68760AE5D55741 | sha256: 8E76318E8B06692ABF7DAB1169D27D15557F7F0A34D36AF6463EFF0FE21213C7 | sha512: 293D8C709BC68D2C980A0DF423741CE06D05FF757077E63986D34CB6459F9623A024D12EF35A280F50D3D516D98ABE193213B9CA71BFDE2A9FE8753B1A6DE2F0

tools\System.Net.Http.dll

md5: 5A5E18C377228FDB1D3DB74F1140C1BF | sha1: E36366D2CCB64AEBCC9DF8FD7FADC7A9BB562AF7 | sha256: 8646A26A64928866BBE8746F3323A1F446C5A28C10B6B81DF9BF4A08336B8C02 | sha512: 0C308B29FEBFB5D4CB52BD3B7B0C61A5844EBF1BDF305BE2B89FB0F5040F52ABD8557E9C4245A4F35C527A23674F1AE97BB12CC3A02A7DD7C8387208FCC73152

tools\System.Net.Sockets.dll

md5: B59AF5CBDDAFDC5DC5FF3E34533D6857 | sha1: DEDE511B5270D55E306E1A744E4BC0384A35C8BE | sha256: A4B4BB8B9BE478600F48E43AE8571E6C123F8130923067F10FC92546D0900FB6 | sha512: 4E0104C8A650943D8680F0BD449D4B953B25FF909BF50BE19772E88295F9CE7542F29211528E20B4AD798D26251A50211EEEA8685E3D81FAB72DF1380CA6B984

tools\System.Numerics.Vectors.dll

md5: AAA2CBF14E06E9D3586D8A4ED455DB33 | sha1: 3D216458740AD5CB05BC5F7C3491CDE44A1E5DF0 | sha256: 1D3EF8698281E7CF7371D1554AFEF5872B39F96C26DA772210A33DA041BA1183 | sha512: 0B14A039CA67982794A2BB69974EF04A7FBEE3686D7364F8F4DB70EA6259D29640CBB83D5B544D92FA1D3676C7619CD580FF45671A2BB4753ED8B383597C6DA8

tools\System.Reflection.TypeExtensions.dll

md5: 10303C3595AA9AC1D61C813A95342345 | sha1: 9937CA553C666328C98F7C11E77C2E2666D4653C | sha256: 4682C5211D69E0C40C39F044929ACEAF1CE6B4CBAC8F938A05F493E35DE83DBF | sha512: 2BAE4C0BEAA879360752B85637B1D850904E1CCC5B7CAAD52CA50920A9A933CA37405ECD44DDA1522F319D64378E3C939676EE75A94E844577F5B276053FE81C

tools\System.Runtime.CompilerServices.Unsafe.dll

md5: C610E828B54001574D86DD2ED730E392 | sha1: 180A7BAAFBC820A838BBACA434032D9D33CCEEBE | sha256: 37768488E8EF45729BC7D9A2677633C6450042975BB96516E186DA6CB9CD0DCF | sha512: 441610D2B9F841D25494D7C82222D07E1D443B0DA07F0CF735C25EC82F6CCE99A3F3236872AEC38CC4DF779E615D22469666066CCEFED7FE75982EEFADA46396

tools\System.Runtime.Serialization.Primitives.dll

md5: A84B438DBD4DF29560EEB5765E03723A | sha1: 37DE951F703687CF061556B1A52C6F548CBF779E | sha256: A576D1609CC08C46A46CE708B7FDAE33452A3BEFB701128A5BC9D6FF1F1B6DFD | sha512: EE6855BCA6EE6FF8AC7CE5C0565CCC77C35E5F1B3096F1EDE2C018D3364683BC289C6C520472BA46E174FDBD821EA673BFFA7DABC9358CE4C86D26F0C08FCC7C

tools\System.Security.AccessControl.dll

md5: 527595C86AD17045A101D567D7D3279F | sha1: 83014E2A98F7597B9A26E424A0759E5A3D2ECFF1 | sha256: FF14C5F628B9A6798D173AEFBBA0A43D61E66F715108E2576AC0D3DFAB9071D0 | sha512: 9EBAACA1623BC8E2FC8DF158F338B5E415670FA53E212BB38771E7E25AF9688301CC4AEE055C5B64E33F8AA24729ED896E0BE8E2DBCE54386583C660476C5DDA

tools\System.Security.Cryptography.Algorithms.dll

md5: 79C6FA92DBA0C34DB2C412BFA62E48A3 | sha1: 583A3E0F870ECE6419350A8656D7D4AC21746F1B | sha256: A83CA72A33172E977D7FFF1E96FA6CBAC6BEFE86DCA21D651C04578210325225 | sha512: 386AB22AA5299C5D4FB3D8B551F97C916129F05FA87D4D3D90B58BE1CC304FFD3431B0B5402A0A77F2DB64B713F31BA60B3D006D0F01EB5A5195A4307ED7F590

tools\System.Security.Permissions.dll

md5: 066B5E9A1FF681CEA20D3DEE597907E4 | sha1: B382B80CA629393DA72379C2EC0149E7639D498D | sha256: 23B91C7E6E84AB983CC6E18DE4D60A06169A26EDA82FC01AE297DD014214A023 | sha512: F755B25564017E7A7828253A1F9970972201C38082C2B1794465F45136F65D12288C5B88D69CF83B1FA631D202D2A1FAA807D21AE147172D150616B53422AF0C

tools\System.Security.Principal.Windows.dll

md5: BE2962225B441CC23575456F32A9CF6A | sha1: 9A5BE1FCF410FE5934D720329D36A2377E83747E | sha256: B4D8E15ADC235D0E858E39B5133E5D00A4BAA8C94F4F39E3B5E791B0F9C0C806 | sha512: 3F7692E94419BFFE3465D54C0E25C207330CD1368FCDFAD71DBEED1EE842474B5ABCB03DBA5BC124BD10033263F22DC9F462F12C20F866AEBC5C91EB151AF2E6

tools\System.Security.SecureString.dll

md5: A6DE3093FFB397AF3E4D2A91FA46B738 | sha1: FB9FF696F96BB574EBD40C2AC9C980FE45AB0F84 | sha256: 9239DE3543EA4DCF71AD86F16AA23EEB760566BC69078925900D0E41EEC859AC | sha512: 3EC05A1DE21EC4C96D6137788A868342AADE033B2D6E9ED7972C8FBEF3503CD03DD4728BA34E37C577AC301C056BB8C142516332C31D2F131599021A307DA86B

tools\System.Threading.Channels.dll

md5: 1BC0F4FFA520FBB86A087D280F8621DF | sha1: F414C683BAB2DF055CC918FF42BADEF3C79F20BD | sha256: 401398F461799E242BB3CC3D24D901666A76C8F2A6617329A9C21D7A0564F0C3 | sha512: 22741A11AD5BD21711CB174C2032F7D714E562C35F86D176388EE4C11582EA4D1550C910CA9E934289704109BF59B40AC159BA9FC4488235ECE4733107E03DAC

tools\System.Threading.Overlapped.dll

md5: C8CE5A96458742641AB9752B5B564039 | sha1: B3315E3657442F82B9A84E9ADE610846D183CAD1 | sha256: A74A34E69B5226F0EE4882F7AC1FC0A88602139ED439202C5FC5C8ED489BFA11 | sha512: 16D4C5180ED313C10886C1E411BF38B5B664D5D3E1B9CB1CDE2D6DDF9EFE39367A792E818636B5E12F90A027C68347A546BF43B386195F50904BD9B5882A005E

tools\System.Threading.Tasks.Extensions.dll

md5: E1E9D7D46E5CD9525C5927DC98D9ECC7 | sha1: 2242627282F9E07E37B274EA36FAC2D3CD9C9110 | sha256: 4F81FFD0DC7204DB75AFC35EA4291769B07C440592F28894260EEA76626A23C6 | sha512: DA7AB8C0100E7D074F0E680B28D241940733860DFBDC5B8C78428B76E807F27E44D1C5EC95EE80C0B5098E8C5D5DA4D48BCE86800164F9734A05035220C3FF11

tools\System.Xml.XPath.XDocument.dll

md5: 54A0AE378C4D20F237E8B01B29E907F2 | sha1: 08FD364458B935C82ECCCA43AC53EA182DA4EA45 | sha256: 05DF614F3252B522D2AA078585DCDDD502A25BDB06CA3A44B1C0D24C1ADB85A2 | sha512: 12EA4FFBCD243F3DB5FEC4D4901F5550F044E49478A909416E7B588EB15E9C6DD005D8255ED8235E803C76B57FBEEBA6FC9B0B85A8155787C1D885537EB87611

tools\VERIFICATION.md

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
 
This package is published by Petabridge, LLC.

Virus Scan Results

System.Data.Common.dll (4fe23dd14781) - ## / 75
System.Diagnostics.StackTrace.dll (e932b25f50e3) - ## / 74
System.Diagnostics.Tracing.dll (d4a59fb62d8a) - ## / 72
System.Globalization.Extensions.dll (f690794a0296) - ## / 74
System.IO.Compression.dll (76fcaccf8431) - ## / 74
System.Net.Http.dll (8646a26a6492) - ## / 75
System.Net.Sockets.dll (a4b4bb8b9be4) - ## / 71
System.Runtime.Serialization.Primitives.dll (a576d1609cc0) - ## / 72
System.Security.Cryptography.Algorithms.dll (a83ca72a3317) - ## / 71
System.Security.SecureString.dll (9239de3543ea) - ## / 75
System.Threading.Overlapped.dll (a74a34e69b52) - ## / 71
System.Xml.XPath.XDocument.dll (05df614f3252) - ## / 72
System.Numerics.Vectors.dll (1d3ef8698281) - ## / 72
System.Buffers.dll (accccfbe45d9) - ## / 71
System.Memory.dll (8e76318e8b06) - ## / 72
System.Threading.Tasks.Extensions.dll (4f81ffd0dc72) - ## / 70
System.Security.Principal.Windows.dll (b4d8e15adc23) - ## / 69
Newtonsoft.Json.dll (b624949df8b0) - ## / 72
System.Runtime.CompilerServices.Unsafe.dll (37768488e8ef) - ## / 71
System.Reflection.TypeExtensions.dll (4682c5211d69) - ## / 71
System.Configuration.ConfigurationManager.dll (c67ddf0ae489) - ## / 73
System.Security.AccessControl.dll (ff14c5f628b9) - ## / 73
System.Security.Permissions.dll (23b91c7e6e84) - ## / 74
System.Threading.Channels.dll (401398f46179) - ## / 73
Microsoft.Bcl.AsyncInterfaces.dll (80678203bd02) - ## / 69
Google.Protobuf.dll (34999912d5f0) - ## / 70
Reactive.Streams.dll (dfb748806727) - ## / 72
petabridge-cmd.1.4.4.nupkg (084c458cf805) - ## / 67
Akka.dll (5b125ae3d027) - ## / 70
Akka.Streams.dll (9ddbbce38218) - ## / 72
Microsoft.Extensions.ObjectPool.dll (cc0997c52eff) - ## / 64
pbm.exe (46de2e6ac819) - ## / 72
Petabridge.Cmd.Common.dll (429e967fb0eb) - ## / 72
System.Collections.Immutable.dll (aed42e17b414) - ## / 72

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

Chocolatey Pro provides runtime protection from possible malware.

Version History

Version	Downloads	Last Updated	Status
Petabridge.Cmd 1.4.4	34	Tuesday, December 31, 2024	Approved
Petabridge.Cmd 1.4.3	60	Monday, June 17, 2024	Approved
Petabridge.Cmd 1.4.2	42	Tuesday, June 11, 2024	Approved
Petabridge.Cmd 1.4.1	45	Monday, March 18, 2024	Approved
Petabridge.Cmd 1.4.0	54	Friday, January 12, 2024	Approved
Petabridge.Cmd 1.3.3	36	Wednesday, January 10, 2024	Approved
Petabridge.Cmd 1.3.2	107	Tuesday, July 18, 2023	Approved
Petabridge.Cmd 1.3.1	119	Thursday, May 4, 2023	Approved
Petabridge.Cmd 1.2.2	115	Thursday, January 19, 2023	Approved
Petabridge.Cmd 1.2.1	64	Monday, December 19, 2022	Approved
Petabridge.Cmd 1.2	60	Friday, November 18, 2022	Approved
Petabridge.Cmd 0.8.5	382	Monday, May 3, 2021	Approved
Petabridge.Cmd 0.8.4	105	Friday, April 30, 2021	Approved
Petabridge.Cmd 0.8.3	146	Thursday, March 18, 2021	Approved
Petabridge.Cmd 0.8.2	204	Tuesday, November 24, 2020	Approved
Petabridge.Cmd 0.8.1	151	Monday, November 16, 2020	Approved
Petabridge.Cmd 0.8.0	363	Wednesday, March 11, 2020	Approved
Petabridge.Cmd 0.8.0-rc2	140	Tuesday, March 10, 2020	Approved
Petabridge.Cmd 0.8.0-rc1	147	Tuesday, March 3, 2020	Approved
Petabridge.Cmd 0.7.1	202	Tuesday, March 3, 2020	Approved
Petabridge.Cmd 0.7.0	301	Thursday, October 3, 2019	Approved
Petabridge.Cmd 0.6.3	274	Tuesday, July 30, 2019	Approved
Petabridge.Cmd 0.6.2	241	Wednesday, June 19, 2019	Approved
Petabridge.Cmd 0.6.1	279	Sunday, May 19, 2019	Approved
Petabridge.Cmd 0.6.0	227	Thursday, May 9, 2019	Approved
Petabridge.Cmd 0.5.0	327	Wednesday, March 6, 2019	Approved
Petabridge.Cmd 0.4.1	301	Friday, December 7, 2018	Approved
Petabridge.Cmd 0.4.0	231	Tuesday, November 27, 2018	Approved
Petabridge.Cmd 0.3.3	575	Tuesday, February 27, 2018	Approved
Petabridge.Cmd 0.3.2	435	Tuesday, December 19, 2017	Approved
Petabridge.Cmd 0.3.1	486	Tuesday, September 19, 2017	Approved
Petabridge.Cmd 0.3.0	388	Thursday, September 14, 2017	Approved
Petabridge.Cmd 0.2.2	455	Sunday, June 25, 2017	Approved
Petabridge.Cmd 0.2.1	403	Tuesday, June 6, 2017	Approved
Petabridge.Cmd 0.2.0	444	Sunday, May 21, 2017	Approved
Petabridge.Cmd 0.1.2	417	Tuesday, April 25, 2017	Approved
Petabridge.Cmd 0.1.1	369	Friday, April 21, 2017	Approved
Petabridge.Cmd 0.1.0	421	Wednesday, April 19, 2017	Approved

Petabridge, LLC

Dependencies

This package has no dependencies.

Discussion for the Petabridge.Cmd Package

Ground Rules:

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

9,150

34

31 Dec 2024

Petabridge.Cmd

Petabridge.Cmd 1.4.4

All Checks are Passing

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Ground Rules: