Downloads of v 0.13.0:


Last Update:

11 Aug 2020

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp


terraform hashicorp


This is not the latest version of Terraform available.

  • 1
  • 2
  • 3

0.13.0 | Updated: 11 Aug 2020



Downloads of v 0.13.0:



Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

  • 1
  • 2
  • 3
Terraform 0.13.0

This is not the latest version of Terraform 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:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


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


Deployment Method:

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

1. Enter Your Internal Repository Url

(this should look similar to

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 terraform -y --source="'INTERNAL REPO URL'" --version="'0.13.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 terraform -y --source="'INTERNAL REPO URL'" --version="'0.13.0'" 

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

Exit $exitCode

- name: Install terraform
    name: terraform
    version: '0.13.0'
    state: present

See docs at

chocolatey_package 'terraform' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.13.0'

See docs at

cChocoPackageInstaller terraform
    Name     = "terraform"
    Version  = "0.13.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'terraform':
  ensure   => '0.13.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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 11 Aug 2020.


Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions.

The key features of Terraform are:

  • Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.
  • Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.
  • Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.
  • Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what Terraform will change and in what order, avoiding many possible human errors.

For more information, see the introduction section of the Terraform website.

$ErrorActionPreference = 'Stop'

$url        = ''
$url64      = ''
$checksum   = '53a8b2162d8a5b77b18472b344af578845983c83eaa910b999ab1cc9186388ac'
$checksum64 = '8af85914d8804c521152167749ca680d7d51447127deb2c7853835b6c62aa9ed'

$unzipLocation = Split-Path -Parent $MyInvocation.MyCommand.Definition

if ([System.IO.Directory]::Exists("$env:ChocolateyInstall\lib\terraform")) {
  if ([System.IO.Directory]::Exists("$env:ChocolateyInstall\lib\terraform\tools")) {
    # clean old plugins and ignore files
    Write-Host "Removing old terraform plugins"
    Remove-Item "$env:ChocolateyInstall\lib\terraform\tools\terraform-*.*"
} else {
  if ([System.IO.Directory]::Exists("$env:ALLUSERSPROFILE\chocolatey\lib\terraform")) {
    if ([System.IO.Directory]::Exists("$env:ALLUSERSPROFILE\chocolatey\lib\terraform\tools")) {
      # clean old plugins and ignore files
      Write-Host "Removing old terraform plugins"
      Remove-Item "$env:ALLUSERSPROFILE\chocolatey\lib\terraform\tools" -Include "terraform-*.*"

$packageParams = @{
  PackageName   = "terraform"
  UnzipLocation = $unzipLocation
  Url           = $url
  Url64         = $url64
  Checksum      = $checksum
  Checksum64    = $checksum64
  ChecksumType  = 'sha256'

Install-ChocolateyZipPackage @packageParams
UnInstall-ChocolateyZipPackage "terraform" ""

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
Terraform 1.0.11 15000 Saturday, November 13, 2021 Approved
Terraform 1.0.10 3099 Tuesday, November 9, 2021 Approved
Terraform 1.0.9 12193 Tuesday, October 19, 2021 Approved
Terraform 1.0.8 10445 Wednesday, September 29, 2021 Approved
Terraform 1.0.7 7202 Thursday, September 16, 2021 Approved
Terraform 1.0.6 5207 Wednesday, September 8, 2021 Approved
Terraform 1.0.5 494 Monday, August 23, 2021 Approved
Terraform 1.0.4 13197 Sunday, August 8, 2021 Approved
Terraform 1.0.3 5409 Thursday, July 29, 2021 Approved

0.13.0 (August 10, 2020)

> This is a list of changes relative to Terraform v0.12.29. To see the
> incremental changelogs for the v0.13.0 prereleases, see
> the v0.13.0-rc1 changelog.

This section contains details about various changes in the v0.13 major release. If you are upgrading from Terraform v0.12, we recommend first referring to the v0.13 upgrade guide for information on some common concerns during upgrade and guidance on ways to address them. (The final upgrade guide and the documentation for the new features will be published only when v0.13.0 final is released; until then, some links in this section will be non-functional.)


  • count and for_each for modules: Similar to the arguments of the same name in resource and data blocks, these create multiple instances of a module from a single module block. (#24461)

  • depends_on for modules: Modules can now use the depends_on argument to ensure that all module resource changes will be applied after any changes to the depends_on targets have been applied. (#25005)

  • Automatic installation of third-party providers: Terraform now supports a decentralized namespace for providers, allowing for automatic installation of community providers from third-party namespaces in the public registry and from private registries. (More details will be added about this prior to release.)

  • Custom validation rules for input variables: A new validation block type inside variable blocks allows module authors to define validation rules at the public interface into a module, so that errors in the calling configuration can be reported in the caller's context rather than inside the implementation details of the module. (#25054)

  • New Kubernetes remote state storage backend: This backend stores state snapshots as Kubernetes secrets. (#19525)


  • As part of introducing a new heirarchical namespace for providers, Terraform now requires an explicit source specification for any provider that is not in the "hashicorp" namespace in the main public registry. (#24477)

    For more information, including information on the automatic upgrade process, refer to the v0.13 upgrade guide.

  • terraform import: the previously-deprecated -provider option is now removed. (#24090)

    To specify a non-default provider configuration for import, add the provider meta-argument to the target resource block.

  • config: Inside provisioner blocks that have when = destroy set, and inside any connection blocks that are used by such provisioner blocks, it is no longer valid to refer to any objects other than self, count, or each. (This was previously deprecated in a v0.12 minor release.) (#24083)

    If you are using null_resource to define provisioners not attached to a real resource, include any values your provisioners need in the triggers map and change the provisioner configuration to refer to those values via self.triggers.

  • configs: At most one terraform required_providers block is permitted per module (#24763)

    If you previously had multiple required_providers blocks in the same module, consolidate their requirements together into a single block.

  • The official MacOS builds of Terraform CLI are no longer compatible with Mac OS 10.10 Yosemite; Terraform now requires at least Mac OS 10.11 El Capitan.

    Terraform 0.13 is the last major release that will support 10.11 El Capitan, so if you are upgrading your OS we recommend upgrading to Mac OS 10.12 Sierra or later.

  • The official FreeBSD builds of Terraform CLI are no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later.

  • backend/oss: The TableStore schema now requires a primary key named LockID of type String. (#24149)

  • backend/s3: The previously-deprecated lock_table, skip_get_ec2_platforms, and skip_requesting_account_id arguments are now removed. (#25134)

  • backend/s3: The credential source preference order now considers EC2 instance profile credentials as lower priority than shared configuration, web identity, and ECS role credentials. (#25134)

  • backend/s3: The AWS_METADATA_TIMEOUT environment variable is no longer used. The timeout is now fixed at one second with two retries. (#25134)


  • The terraform plan and terraform apply commands will now detect and report changes to root module outputs as needing to be applied even if there are no resource changes in the plan.

    This is an improvement in behavior for most users, since it will now be possible to change output blocks and use terraform apply to apply those changes.

    If you have a configuration where a root module output value is changing for every plan (for example, by referring to an unstable data source), you will need to remove or change that output value in order to allow convergence on an empty plan. Otherwise, each new plan will propose more changes.

  • Terraform CLI now supports TLS 1.3 and supports Ed25519 certificates when making outgoing connections to remote TLS servers.

    While both of these changes are backwards compatible in principle, certain legacy TLS server implementations can reportedly encounter problems when attempting to negotiate TLS 1.3. (These changes affects only requests made by Terraform CLI itself, such as to module registries or backends. Provider plugins have separate TLS implementations that will gain these features on a separate release schedule.)

  • On Unix systems where use-vc is set in resolv.conf, Terraform will now use TCP for DNS resolution.

    We don't expect this to cause any problem for most users, but if you find you are seeing DNS resolution failures after upgrading please verify that you can either reach your configured nameservers using TCP or that your resolver configuration does not include the use-vc directive.

  • The terraform 0.12upgrade command is no longer available. (#24403)

    To upgrade from Terraform v0.11, first upgrade to the latest v0.12 release and then upgrade to v0.13 from there.


  • config: templatefile function will now return a helpful error message if a given variable has an invalid name, rather than relying on a syntax error in the template parsing itself. (#24184)

  • config: The configuration language now uses Unicode 12.0 character tables for certain Unicode-version-sensitive operations on strings, such as the upper and lower functions. Those working with strings containing new characters introduced since Unicode 9.0 may see small differences in behavior as a result of these table updates.

  • config: The new sum function takes a list or set of numbers and returns the sum of all elements. (#24666)

  • config: Modules authored by the same vendor as the main provider they use can now pass metadata to the provider to allow for instrumentation and analytics. (#22583)

  • cli: The terraform plan and terraform apply commands now recognize changes to root module outputs as side-effects to be approved and applied. This means you can apply root module output changes using the normal plan and apply workflow. (#25047)

  • cli: When installing providers from the Terraform Registry, Terraform will verify the trust signature for partner providers, and allow for self-signed community providers. (#24617)

  • cli: terraform init will display detailed trust signature information when installing providers from the Terraform Registry and other provider registries. (#24932)

  • cli: It is now possible to optionally specify explicitly which installation methods can be used for different providers in the CLI configuration, such as forcing a particular provider to be loaded from a particular directory on local disk instead of consulting its origin provider registry. (#24728)

  • cli: The new terraform state replace-provider subcommand allows changing the selected provider for existing resource instances in the Terraform state. (#24523)

  • cli: The new terraform providers mirror subcommand can automatically construct or update a local filesystem mirror directory containing the providers required for the current configuration. (#25084)

  • cli: terraform version -json now produces machine-readable version information. (#25252)

  • cli: terraform import can now work with provider configurations containing references to other objects, as long as the data in question is already known in the current state. (#25420)

  • cli: The terraform state rm command will now exit with status code 1 if the given resource address does not match any resource instances. (#22300)

  • cli: The terraform login command now requires the full word "yes" to confirm, rather than just "y", for consistency with Terraform's other interactive prompts. (#25379)

  • core: Several of Terraform's graph operations are now better optimized to support configurations with highly-connected graphs. (#23811, #25544)

  • backend/remote: Now supports terraform state push -force. (#24696)

  • backend/remote: Can now accept -target options when creating a plan using remote operations, if supported by the target server. (Server-side support for this in Terraform Cloud and Terraform Enterprise will follow in forthcoming releases of each.) (#24834)

  • backend/azurerm: Now uses the Giovanni Storage SDK to communicate with Azure. (#24669)

  • backend/s3: The backend will now always consult the shared configuration file, even if the AWS_SDK_LOAD_CONFIG environment variable isn't set. That environment variable is now ignored. (#25134)

  • backend/s3: Region validation now automatically supports the new af-south-1 (Africa (Cape Town)) region. (#24744)

    For AWS operations to work in the new region, you must explicitly enable it as described in AWS General Reference: Enabling a Region. If you haven't enabled the region, the Terraform S3 Backend will return InvalidClientTokenId errors during credential validation.

  • backend/s3: A ~/ prefix in the shared_credentials_file argument is now expanded to the current user's home directory. (#25134)

  • backend/s3: The backend has a number of new options for customizing the "assume role" behavior, including controlling the lifetime and access policy of temporary credentials. (#25134)

  • backend/swift: The authentication options match those of the OpenStack provider. (#23510)


  • config: The jsonencode function can now correctly encode a single null value as the JSON expression null. (#25078)
  • config: The map function no longer crashes when incorrectly given a non-string key. (#24277)
  • config: The substr function now correctly returns a zero-length string when given a length of zero, rather than ignoring that argument entirely. (#24318)
  • config: ceil(1/0) and floor(1/0) (that is, an infinity as an argument) now return another infinity with the same sign, rather than just a large integer. (#21463)
  • config: The rsadecrypt function now supports the OpenSSH RSA key format. (#25112)
  • config: The merge function now returns more precise type information, making it usable for values passed to for_each, and will no longer crash if all of the given maps are empty. (#24032, #25303)
  • vendor: The various set-manipulation functions, like setunion, will no longer panic if given an unknown set value (#25318)
  • config: Fixed a crash with incorrect syntax in .tf.json and .tfvars.json files. (#24650)
  • config: The function argument expansion syntax ... no longer incorrectly fails with "Invalid expanding argument value" in situations where the expanding argument's type will not be known until the apply phase. (#25216)
  • config: Variable validation block error message checks no longer fail when non-ASCII characters are present. (#25144)
  • cli: The terraform plan command (and the implied plan run by terraform apply with no arguments) will now print any warnings that were generated even if there are no changes to be made. (#24095)
  • cli: terraform state mv now correctly records the resource's use of either count or for_each based on the given target address. (#24254)
  • cli: When using the TF_CLI_CONFIG_FILE environment variable to override where Terraform looks for CLI configuration, Terraform will now ignore the default CLI configuration directory as well as the default CLI configuration file. (#24728)
  • cli: The terraform login command in OAuth2 mode now implements the PKCE OAuth 2 extension more correctly. Previously it was not compliant with all of the details of the specification. (#24858)
  • cli: Fixed a potential crash when the HOME environment variable isn't set, causing the native service credentials store to be nil. (#25110)
  • command/fmt: Error messages will now include source code snippets where possible. (#24471)
  • command/apply: terraform apply will no longer silently exit when given an absolute path to a saved plan file on Windows. (#25233)
  • command/init: terraform init will now produce an explicit error message if given a non-directory path for its configuration directory argument, and if a -backend-config file has a syntax error. Previously these were silently ignored. (#25300, #25411)
  • command/console: (#25442)
  • command/import: The import command will now properly attach the configured provider for the target resource based on the configuration, making the -provider command line option unnecessary. (#22862)
  • command/import: The -allow-missing-config option now works correctly. It was inadvertently disabled as part of v0.12 refactoring. (#25352)
  • command/show: Resource addresses are now consistently formatted between the plan and prior state in the -json output. (#24256)
  • core: Fixed a crash related to an unsafe concurrent read and write of a map data structure. (#24599)
  • core: Instances are now destroyed only using their stored state, without re-evaluating configuration. This avoids a number of dependency cycle problems when "delete" actions are included in a plan. (#24083)
  • provider/terraform: The terraform_remote_state data source will no longer attempt to "configure" the selected backend during validation, which means backends will not try to perform remote actions such as verifying credentials during terraform validate. Local validation still applies in all cases, and the configuration step will still occur prior to actually reading the remote state in a normal plan/apply operation. (#24887)
  • backend/remote: Backend will no longer crash if the user cancels backend initialization at an inopportune time, or if there is a connection error. (#25135) (#25341)
  • backend/azurerm: The backend will now create a Azure storage snapshot of the previous Terraform state snapshot before writing a new one. (#24069)
  • backend/s3: Various other minor authentication-related fixes previously made in the AWS provider. (#25134)
  • backend/oss: Now allows locking of multiple different state files. (#24149)
  • provisioner/remote-exec: The provisioner will now return an explicit error if the host connection argument is an empty string. Previously it would repeatedly attempt to resolve an empty hostname until timeout. (#24080)
  • provisioner/chef: The provisioner will now gracefully handle non-failure (RFC062) exit codes returned from Chef. (#19155)
  • provisioner/habitat: The provisioner will no longer generate user.toml with world-readable permissions. (#24321)
  • communicator/winrm: Support a connection timeout for WinRM connection blocks. Previously this argument worked for SSH only. (#25350)


  • This release concludes the variable_validation experiment that was started in Terraform v0.12.20. If you were participating in the experiment, you should remove the experiment opt-in from your configuration as part of upgrading to Terraform 0.13.

    The experiment received only feedback that can be addressed with backward-compatible future enhancements, so we've included it into this release as stable with no changes to its original design so far. We'll consider additional features related to custom validation in future releases after seeing how it's used in real-world modules.

Previous Releases

For more information on previous releases, check out the changelog on GitHub.

This package has no dependencies.

Discussion for the Terraform Package

Ground Rules:

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