Chocolatey Community Coffee Break

Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Announcing Chocolatey Central Management 0.10.0

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Watch On-Demand
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand
Chocolatey Product Spotlight: Chocolatey 1.2.0 and Chocolatey Licensed Extension 5.0.0

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Watch On-Demand
Chocolatey Coding Livestream

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Watch On-Demand
Introduction into Chocolatey with Veeam

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

Watch On-Demand



Downloads of v 1.15.0:


Last Update:

25 Feb 2023

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • Armon Dadgar
  • HashiCorp


consul service


This is not the latest version of Consul available.

  • 1
  • 2
  • 3

1.15.0 | Updated: 25 Feb 2023



Downloads of v 1.15.0:



Software Author(s):

  • Mitchell Hashimoto
  • Armon Dadgar
  • HashiCorp

Consul 1.15.0

This is not the latest version of Consul available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


To uninstall Consul, run the following command from the command line or from PowerShell:


Deployment Method:


This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

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

  • 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 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

3. Copy Your Script

choco upgrade consul -y --source="'INTERNAL REPO URL'" --version="'1.15.0'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

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

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

choco upgrade consul -y --source="'INTERNAL REPO URL'" --version="'1.15.0'" 

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

Exit $exitCode

- name: Install consul
    name: consul
    version: '1.15.0'
    state: present

See docs at

chocolatey_package 'consul' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.15.0'

See docs at

cChocoPackageInstaller consul
    Name     = "consul"
    Version  = "1.15.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'consul':
  ensure   => '1.15.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

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 25 Feb 2023.


Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.
Uses NSSM as the service wrapper. More info at:

Package Parameters

The package parameters can be set -
These parameters can be passed to the installer with the use of -params.
For example: -params '-config-file="%PROGRAMDATA%\consul\dsc-config\default.json"'.

Get-Process consul -ErrorAction SilentlyContinue | Stop-Process -Force -ErrorAction SilentlyContinue
if (Test-Path Function:\au_GetLatest) {

# Defaults
$serviceName = "consul"
$binariesPath = Split-Path -parent $MyInvocation.MyCommand.Definition
$toolsPath = Split-Path -Parent $MyInvocation.MyCommand.Definition
$wrapperExe = "$env:ChocolateyInstall\bin\nssm.exe"
$serviceInstallationDirectory = "$env:PROGRAMDATA\consul"
$serviceLogDirectory = "$serviceInstallationDirectory\logs"
$serviceConfigDirectory = "$serviceInstallationDirectory\config"
$serviceDataDirectory = "$serviceInstallationDirectory\data"

$packageParameters = $env:chocolateyPackageParameters
if (-not ($packageParameters)) {
  $packageParameters = ""
  Write-Debug "No Package Parameters Passed in"

# Create Service Directories
Write-Host "Creating $serviceLogDirectory"
New-Item -ItemType directory -Path "$serviceLogDirectory" -ErrorAction SilentlyContinue | Out-Null
Write-Host "Creating $serviceConfigDirectory"
New-Item -ItemType directory -Path "$serviceConfigDirectory" -ErrorAction SilentlyContinue | Out-Null

# Unzip and move Consul
Get-ChocolateyUnzip -fileFullPath $(Join-Path $binariesPath "consul_$($env:ChocolateyPackageVersion)") -fileFullPath64 $(Join-Path $binariesPath "consul_$($env:ChocolateyPackageVersion)") -destination "$toolsPath"

# Create event log source
# User -Force to avoid "A key at this path already exists" exception. Overwrite not an issue since key is not further modified
$registryPath = 'HKLM:\SYSTEM\CurrentControlSet\services\eventlog\Application'
New-Item -Path $registryPath -Name consul -Force | Out-Null
# Set EventMessageFile value
Set-ItemProperty $registryPath\consul EventMessageFile "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\EventLogMessages.dll" | Out-Null

# Set up task scheduler for log rotation
$logrotate = ('%SYSTEMROOT%\System32\forfiles.exe /p \"{0}\" /s /m *.* /c \"cmd /c Del @path\" /d -7' -f "$serviceLogDirectory")
SchTasks.exe /Create /SC DAILY /TN ""ConsulLogrotate"" /TR ""$($logrotate)"" /ST 09:00 /F | Out-Null

# Set up task scheduler for log rotation. Only works for Powershell 4 or Server 2012R2 so this block can replace
# using SchTasks.exe for registering services once machines have retired the older version of PS or upgraded to 2012R2
#$command = ('$now = Get-Date; dir "{0}" | where {{$_.LastWriteTime -le $now.AddDays(-7)}} | del -whatif' -f $serviceLogDirectory)
#$action = New-ScheduledTaskAction -Execute 'Powershell.exe' -Argument "-NoProfile -WindowStyle Hidden -command $($command)"
#$trigger = New-ScheduledTaskTrigger -Daily -At 9am
#Register-ScheduledTask -Action $action -Trigger $trigger -TaskName "ConsulLogrotate" -Description "Log rotation for consul"

#Uninstall service if it already exists. Stops the service first if it's running
$service = Get-Service $serviceName -ErrorAction SilentlyContinue
if ($service) {
  Write-Host "Uninstalling existing service"
  if($service.Status -ne "Stopped" -and $service.Status -ne "Stopping") {
    Write-Host "Stopping consul process ..."

  $service.WaitForStatus("Stopped", (New-TimeSpan -Minutes 1));
  if($service.Status -ne "Stopped") {
    throw "$serviceName could not be stopped within the allotted timespan.  Stop the service and try again."

  $service = Get-WmiObject -Class Win32_Service -Filter "Name='$serviceName'"
  $service.delete() | Out-Null

Write-Host "Installing service: $serviceName"
# Install the service
& $wrapperExe install $serviceName $(Join-Path $toolsPath "consul.exe") "agent -ui -config-dir=$serviceConfigDirectory -data-dir=$serviceDataDirectory $packageParameters" | Out-Null
& $wrapperExe set $serviceName AppEnvironmentExtra GOMAXPROCS=$env:NUMBER_OF_PROCESSORS | Out-Null
& $wrapperExe set $serviceName ObjectName NetworkService | Out-Null
& $wrapperExe set $serviceName AppStdout "$serviceLogDirectory\consul-output.log" | Out-Null
& $wrapperExe set $serviceName AppStderr "$serviceLogDirectory\consul-error.log" | Out-Null
& $wrapperExe set $serviceName AppRotateBytes 10485760 | Out-Null
& $wrapperExe set $serviceName AppRotateFiles 1 | Out-Null
& $wrapperExe set $serviceName AppRotateOnline 1 | Out-Null

Write-Verbose "Service installed"

# When nssm fully supports Rotate/Post Event hooks
# $command = ('$now = Get-Date; dir "{0}" | where {{$_.LastWriteTime -le $now.AddDays(-7)}} | del -whatif' -f $serviceLogDirectory)
# $action = ("Powershell.exe -NoProfile -WindowStyle Hidden -command '$({{0}})'" -f $command)
# & $wrapperExe set consul AppEvents "Rotate/Post" $action | Out-Null

# Restart service on failure natively via Windows sc. There is a memory leak if service restart is performed via NSSM
# The NSSM configuration will set the default behavior of NSSM to stop the service if
# consul fails (for example, unable to resolve cluster) and end the nssm.exe and consul.exe process.
# The sc configuration will set Recovery under the Consul service properties such that a new instance will be started on failure,
# spawning new nssm.exe and consul.exe processes. In short, nothing changed from a functionality perspective (the service will
# still attempt to restart on failure) but this method kills the nssm.exe process thus avoiding memory hog.
& $wrapperExe set $serviceName AppExit Default Exit | Out-Null
Write-Verbose "sc failure"
cmd.exe /c "sc failure $serviceName reset= 0 actions= restart/60000" | Out-Null

Write-Verbose "Stop service"
# Let this call to Get-Service throw if the service does not exist
$service = Get-Service $serviceName
if($service.Status -ne "Stopped" -and $service.Status -ne "Stopping") {

Write-Verbose "Wait for service to stop"
$service.WaitForStatus("Stopped", (New-TimeSpan -Minutes 1));

Write-Verbose "Start service"
Start-Service $serviceName

Write-Host "Installed service: $serviceName"
$service = Get-Service "consul" -ErrorAction SilentlyContinue

if ($service) {
	if ($service.Status -eq "Running") {
		Write-Host "Stopping consul process ..."
		net stop consul | Out-Null

	$service = Get-WmiObject -Class Win32_Service -Filter "Name='consul'"
	$service.delete() | Out-Null

SchTasks.exe /Delete /F /TN "ConsulLogrotate" 2>&1 | Out-Null

Write-Host "Removing C:\ProgramData\consul\ ..."
takeown /f "C:\ProgramData\consul\" /a /r /d Y | Out-Null
icacls "C:\ProgramData\consul" /grant administrators:F /t | Out-Null
Remove-Item -Path "C:\ProgramData\consul\" -Force -Recurse -ErrorAction SilentlyContinue | Out-Null
md5: FE8586EF1261430FADEFD29C3566EDA1 | sha1: E46D54AD14E0EE452C75D412D3735D754A590504 | sha256: FC8FF0949BB2D132D204A87317997B55471AEC467889D777A0F44AA9DA81FD7C | sha512: 233ED79D3ACE1EECC19CD416B464DACE744C7504B3A91676B2644027E5C45266B583EA164F233511AF04A32F1522EA10752E2F65349F55A475A7923111933926
md5: A8CB71596BE0113581BBD9A995AF9F28 | sha1: 7ADDD7BB01AD122E63CE41468AB17BD92C7DADBD | sha256: CDE8EE091EA1E46E4D4D97ADD06344563AEBFDF1F22BD4E19656C773C272D9C2 | sha512: CF1B7209BBA990091A07DE2AF34AE95FF2BFE2CBE9B95EE94B6EB67271179D72A39FEB5AA5181A6178CA5A82AD40260ADB242FF95D8C248C98BF3F16DBABE468

Log in or click on link to see number of positives.

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

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Consul 1.15.2 910 Sunday, April 2, 2023 Approved
Consul 1.15.1 589 Wednesday, March 8, 2023 Approved
Consul 1.15.0 285 Saturday, February 25, 2023 Approved
Consul 1.14.4 4554 Thursday, February 23, 2023 Approved
Consul 1.9.0 16468 Tuesday, January 5, 2021 Approved
Consul 1.8.7 2038 Monday, December 28, 2020 Approved
Consul 1.8.6 115 Monday, December 28, 2020 Approved
Consul 1.8.5 1078 Thursday, November 5, 2020 Approved
Consul 1.8.4 542 Wednesday, November 4, 2020 Approved
Consul 1.8.3 147 Wednesday, November 4, 2020 Approved
Consul 1.8.2 169 Tuesday, November 3, 2020 Approved
Consul 1.8.1 197 Thursday, October 29, 2020 Approved
Consul 1.8.0 2516 Tuesday, August 11, 2020 Approved
Consul 1.7.5 163 Tuesday, August 11, 2020 Approved
Consul 1.7.4 321 Saturday, August 8, 2020 Approved
Consul 1.7.3 158 Saturday, August 8, 2020 Approved
Consul 1.7.2 3363 Wednesday, June 17, 2020 Approved
Consul 1.7.1 184 Wednesday, June 17, 2020 Approved
Consul 1.7.0 194 Tuesday, June 16, 2020 Approved
Consul 1.6.10 288 Sunday, December 27, 2020 Approved
Consul 1.6.9 143 Sunday, December 27, 2020 Approved
Consul 1.6.8 99 Sunday, December 27, 2020 Approved
Consul 1.6.7 93 Saturday, December 26, 2020 Approved
Consul 1.6.6 187 Tuesday, June 16, 2020 Approved
Consul 1.6.5 1753 Friday, April 17, 2020 Approved
Consul 1.6.4 427 Friday, April 17, 2020 Approved
Consul 1.6.3 235 Wednesday, April 15, 2020 Approved
Consul 1.6.2 335 Thursday, April 9, 2020 Approved
Consul 1.6.1 12654 Friday, October 4, 2019 Approved
Consul 1.6.0 371 Friday, October 4, 2019 Approved
Consul 1.5.3 254 Friday, October 4, 2019 Approved
Consul 1.5.2 3662 Monday, July 8, 2019 Approved
Consul 1.5.1 1953 Monday, June 24, 2019 Approved
Consul 1.5.0 293 Monday, June 24, 2019 Approved
Consul 1.4.5 358 Monday, June 24, 2019 Approved
Consul 1.4.4 334 Monday, June 24, 2019 Approved
Consul 1.4.3 2292 Wednesday, March 6, 2019 Approved
Consul 1.4.2 534 Wednesday, March 6, 2019 Approved
Consul 1.4.1 252 Tuesday, March 5, 2019 Approved
Consul 1.4.0 1718 Tuesday, December 11, 2018 Approved
Consul 1.3.1 355 Monday, December 10, 2018 Approved
Consul 1.3.0 818 Saturday, November 10, 2018 Approved
Consul 1.2.3 2268 Friday, October 12, 2018 Approved
Consul 1.2.2 4104 Thursday, August 2, 2018 Approved
Consul 1.2.1 764 Monday, July 16, 2018 Approved
Consul 1.2.0 682 Wednesday, June 27, 2018 Approved
Consul 1.1.0 1029 Monday, June 4, 2018 Approved
Consul 1.0.7 1439 Monday, April 23, 2018 Approved
Consul 1.0.6 409 Friday, April 20, 2018 Approved
Consul 1.0.5 303 Friday, April 20, 2018 Approved
Consul 1.0.3 6414 Friday, January 26, 2018 Approved
Consul 1.0.2 497 Wednesday, January 24, 2018 Approved
Consul 1.0.1 368 Wednesday, January 24, 2018 Approved
Consul 1.0.0 5393 Monday, October 23, 2017 Approved
Consul 0.9.3 9859 Saturday, September 16, 2017 Approved
Consul 0.9.2 440 Saturday, September 16, 2017 Approved
Consul 0.9.1 337 Saturday, September 16, 2017 Approved
Consul 0.9.0 1369 Wednesday, July 26, 2017 Approved
Consul 0.8.5 3972 Friday, June 30, 2017 Approved
Consul 0.8.4 482 Friday, June 30, 2017 Approved
Consul 0.8.3 472 Friday, June 30, 2017 Approved
Consul 0.8.2 414 Friday, June 30, 2017 Approved
Consul 0.8.1 498 Friday, June 30, 2017 Approved
Consul 0.8.0 4098 Monday, April 10, 2017 Approved
Consul 0.7.5 11638 Tuesday, February 21, 2017 Approved
Consul 439 Thursday, February 16, 2017 Approved
Consul 0.7.4 409 Wednesday, February 15, 2017 Approved
Consul 0.7.3 517 Wednesday, February 15, 2017 Approved
Consul 0.7.2 1455 Monday, January 2, 2017 Approved
Consul 0.7.1 524 Friday, December 30, 2016 Approved
Consul 0.7.0 3840 Monday, September 19, 2016 Approved
Consul 0.6.4 5255 Wednesday, April 20, 2016 Approved
Consul 618 Monday, March 7, 2016 Approved
Consul 488 Thursday, February 25, 2016 Approved
Consul 0.6.3 816 Friday, January 22, 2016 Approved
Consul 0.5.2 9174 Wednesday, October 14, 2015 Approved
Consul 0.5.0 20931 Monday, June 1, 2015 Approved
consul 0.4.1 666 Friday, October 31, 2014 Approved
consul 0.3.1 505 Wednesday, August 13, 2014 Approved

1.15.0 (February 23, 2023)


  • acl errors: Delete and get requests now return descriptive errors when the specified resource cannot be found. Other ACL request errors provide more information about when a resource is missing. Add error for when the ACL system has not been bootstrapped.
    • Delete Token/Policy/AuthMethod/Role/BindingRule endpoints now return 404 when the resource cannot be found.
      • New error formats: "Requested * does not exist: ACL not found", "* not found in namespace $NAMESPACE: ACL not found"
    • Read Token/Policy/Role endpoints now return 404 when the resource cannot be found.
      • New error format: "Cannot find * to delete"
    • Logout now returns a 401 error when the supplied token cannot be found
      • New error format: "Supplied token does not exist"
    • Token Self endpoint now returns 404 when the token cannot be found.
      • New error format: "Supplied token does not exist" [GH-16105]
  • acl: remove all acl migration functionality and references to the legacy acl system. [GH-15947]
  • acl: remove all functionality and references for legacy acl policies. [GH-15922]
  • config: Deprecate -join, -join-wan, start_join, and start_join_wan.
    These options are now aliases of -retry-join, -retry-join-wan, retry_join, and retry_join_wan, respectively. [GH-15598]
  • connect: Add peer field to service-defaults upstream overrides. The addition of this field makes it possible to apply upstream overrides only to peer services. Prior to this change, overrides would be applied based on matching the namespace and name fields only, which means users could not have different configuration for local versus peer services. With this change, peer upstreams are only affected if the peer field matches the destination peer name. [GH-15956]
  • connect: Consul will now error and exit when using the consul connect envoy command if the Envoy version is incompatible. To ignore this check use flag --ignore-envoy-compatibility [GH-15818]
  • extensions: Refactor Lambda integration to get configured with the Envoy extensions field on service-defaults configuration entries. [GH-15817]
  • ingress-gateway: upstream cluster will have empty outlier_detection if passive health check is unspecified [GH-15614]
  • xds: Remove the connect.enable_serverless_plugin agent configuration option. Now
    Lambda integration is enabled by default. [GH-15710]



  • API Gateway (Beta) This version adds support for API gateway on VMs. API gateway provides a highly-configurable ingress for requests coming into a Consul network. For more information, refer to the API gateway documentation. [GH-16369]
  • acl: Add new acl.tokens.config_file_registration config field which specifies the token used
    to register services and checks that are defined in config files. [GH-15828]
  • acl: anonymous token is logged as 'anonymous token' instead of its accessor ID [GH-15884]
  • cli: adds new CLI commands consul troubleshoot upstreams and consul troubleshoot proxy to troubleshoot Consul's service mesh configuration and network issues. [GH-16284]
  • command: Adds the operator usage instances subcommand for displaying total services, connect service instances and billable service instances in the local datacenter or globally. [GH-16205]
  • config-entry(ingress-gateway): support outlier detection (passive health check) for upstream cluster [GH-15614]
  • connect: adds support for Envoy access logging. Access logging can be enabled using the proxy-defaults config entry. [GH-15864]
  • xds: Add a built-in Envoy extension that inserts Lua HTTP filters. [GH-15906]
  • xds: Insert originator service identity into Envoy's dynamic metadata under the consul namespace. [GH-15906]


  • connect: for early awareness of Envoy incompatibilities, when using the consul connect envoy command the Envoy version will now be checked for compatibility. If incompatible Consul will error and exit. [GH-15818]
  • grpc: client agents will switch server on error, and automatically retry on RESOURCE_EXHAUSTED responses [GH-15892]
  • raft: add an operator api endpoint and a command to initiate raft leadership transfer. [GH-14132]
  • acl: Added option to allow for an operator-generated bootstrap token to be passed to the acl bootstrap command. [GH-14437]
  • agent: Give better error when client specifies wrong datacenter when auto-encrypt is enabled. [GH-14832]
  • api: updated the go module directive to 1.18. [GH-15297]
  • ca: support Vault agent auto-auth config for Vault CA provider using AWS/GCP authentication. [GH-15970]
  • cli: always use name "global" for proxy-defaults config entries [GH-14833]
  • cli: connect envoy command errors if grpc ports are not open [GH-15794]
  • client: add support for RemoveEmptyTags in Prepared Queries templates. [GH-14244]
  • connect: Warn if ACLs are enabled but a token is not provided to envoy [GH-15967]
  • container: Upgrade container image to use to Alpine 3.17. [GH-16358]
  • dns: support RFC 2782 SRV lookups for prepared queries using format _<query id or name>._tcp.query[.<datacenter>].<domain>. [GH-14465]
  • ingress-gateways: Don't log error when gateway is registered without a config entry [GH-15001]
  • licensing: (Enterprise Only) Consul Enterprise non-terminating production licenses do not degrade or terminate Consul upon expiration. They will only fail when trying to upgrade to a newer version of Consul. Evaluation licenses still terminate.
  • raft: Added experimental wal backend for log storage. [GH-16176]
  • sdk: updated the go module directive to 1.18. [GH-15297]
  • telemetry: Added a consul.xds.server.streamsUnauthenticated metric to track
    the number of active xDS streams handled by the server that are unauthenticated
    because ACLs are not enabled or ACL tokens were missing. [GH-15967]
  • ui: Update sidebar width to 280px [GH-16204]
  • ui: update Ember version to 3.27; [GH-16227]


  • acl: Deprecate the token query parameter and warn when it is used for authentication. [GH-16009]
  • cli: The -id flag on acl token operations has been changed to -accessor-id for clarity in documentation. The -id flag will continue to work, but operators should use -accessor-id in the future. [GH-16044]


  • agent configuration: Fix issue of using unix socket when https is used. [GH-16301]
  • cache: refactor agent cache fetching to prevent unnecessary fetches on error [GH-14956]
  • cli: fatal error if config file does not have HCL or JSON extension, instead of warn and skip [GH-15107]
  • cli: fix ACL token processing unexpected precedence [GH-15274]
  • peering: Fix bug where services were incorrectly imported as connect-enabled. [GH-16339]
  • peering: Fix issue where mesh gateways would use the wrong address when contacting a remote peer with the same datacenter name. [GH-16257]
  • peering: Fix issue where secondary wan-federated datacenters could not be used as peering acceptors. [GH-16230]

Discussion for the Consul Package

Ground Rules:

  • This discussion is only about Consul and the Consul 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 Consul, 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.
comments powered by Disqus