Downloads:

585,357

Downloads of v 0.15.0:

5,351

Last Update:

14 Apr 2021

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

terraform hashicorp

Terraform

This is not the latest version of Terraform available.

  • 1
  • 2
  • 3

0.15.0 | Updated: 14 Apr 2021

Downloads:

585,357

Downloads of v 0.15.0:

5,351

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

  • 1
  • 2
  • 3
Terraform 0.15.0

This is not the latest version of Terraform available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

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

  • 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

3. Copy Your Script

choco upgrade terraform -y --source="'INTERNAL REPO URL'" --version="'0.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 terraform -y --source="'INTERNAL REPO URL'" --version="'0.15.0'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install terraform
  win_chocolatey:
    name: terraform
    version: '0.15.0'
    source: INTERNAL REPO URL
    state: present

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


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

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


cChocoPackageInstaller terraform
{
    Name     = "terraform"
    Version  = "0.15.0"
    Source   = "INTERNAL REPO URL"
}

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


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

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

This package was approved as a trusted package on 14 Apr 2021.

Description

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.


tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

# DO NOT CHANGE THESE MANUALLY. USE update.ps1
$url = 'https://releases.hashicorp.com/terraform/0.15.0/terraform_0.15.0_windows_386.zip'
$url64 = 'https://releases.hashicorp.com/terraform/0.15.0/terraform_0.15.0_windows_amd64.zip'
$checksum = 'fa3ffcfe85cca5e83faa2c95a9e1518a214a2b68b34a7627fe448ef95c50f09a'
$checksum64 = 'fa55cc82adc4b91fa4f718941da79c3b695aa597e244dae40b574d966bb40692'

$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
tools\chocolateyUninstall.ps1
UnInstall-ChocolateyZipPackage "terraform" "terraformInstall.zip"

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.10 3092 Tuesday, November 9, 2021 Approved
Terraform 1.0.9 11945 Tuesday, October 19, 2021 Approved
Terraform 1.0.8 10412 Wednesday, September 29, 2021 Approved
Terraform 1.0.7 7153 Thursday, September 16, 2021 Approved
Terraform 1.0.6 5186 Wednesday, September 8, 2021 Approved
Terraform 1.0.5 489 Monday, August 23, 2021 Approved
Terraform 1.0.4 13104 Sunday, August 8, 2021 Approved
Terraform 1.0.3 5386 Thursday, July 29, 2021 Approved
Terraform 1.0.2 8543 Saturday, July 10, 2021 Approved

0.15.0 (April 14, 2021)

UPGRADE NOTES AND BREAKING CHANGES:

The following is a summary of each of the changes in this release that might require special consideration when upgrading. Refer to the Terraform v0.15 upgrade guide for more details and recommended upgrade steps.

  • "Proxy configuration blocks" (provider blocks with only alias set) in shared modules are now replaced with a more explicit configuration_aliases argument within the required_providers block. Some support for the old syntax is retained for backward compatibility, but we've added explicit error messages for situations where Terraform would previously silently misinterpret the purpose of an empty provider block. (#27739)

  • The list and map functions, both of which were deprecated since Terraform v0.12, are now removed. You can replace uses of these functions with tolist([...]) and tomap({...}) respectively. (#26818)

  • Terraform now requires UTF-8 character encoding and virtual terminal support when running on Windows. This unifies Terraform's terminal handling on Windows with that of other platforms, as per Microsoft recommendations. Terraform previously required these terminal features on all other platforms, and now requires them on Windows too.

    UTF-8 and virtual terminal support were introduced across various Windows 10 updates, and so Terraform is no longer officially supported on the original release of Windows 10 or on Windows 8 and earlier. However, there are currently no technical measures to artificially prevent Terraform from running on these obsolete Windows releases, and so you may still be able to use Terraform v0.15 on older Windows versions if you either disable formatting (using the -no-color) option, or if you use a third-party terminal emulator package such as ConEmu, Cmder, or mintty.

    We strongly encourage planning to migrate to a newer version of Windows rather than relying on these workarounds for the long term, because the Terraform team will test future releases only on up-to-date Windows 10 and can therefore not guarantee ongoing support for older versions.

  • Built-in vendor provisioners (chef, habitat, puppet, and salt-masterless) have been removed. (#26938)

  • Interrupting execution will now cause terraform to exit with a non-zero exit status. (#26738)

  • The trailing [DIR] argument to specify the working directory for various commands is no longer supported. Use the global -chdir option instead. (#27664)

    For example, instead of terraform init infra, write terraform -chdir=infra init.

  • The -lock and -lock-timeout options are no longer available on terraform init (#27464)

  • The -verify-plugins=false option is no longer available on terraform init. (Terraform now always verifies plugins.) (#27461)

  • The -get-plugins=false option is no longer available on terraform init. (Terraform now always installs plugins.) (#27463)

  • The -force option is no longer available on terraform destroy. Use -auto-approve instead (#27681)

  • The -var and -var-file options are no longer available on terraform validate. These were deprecated and have had no effect since Terraform v0.12. (#27906)

  • terraform version -json output no longer includes the (previously-unpopulated) "revision" property (#27484)

  • In the gcs backend the path config argument, which was deprecated since Terraform v0.11, is now removed. Use the prefix argument instead. (#26841)

  • The deprecated ignore_changes = ["*"] wildcard syntax is no longer supported. Use ignore_changes = all instead. (#27834)

  • Previously deprecated quoted variable type constraints are no longer supported. Follow the instructions in the error message to update your type signatures to be more explicit. For example, use map(string) instead of "map". (#27852)

  • Terraform will no longer make use of the HTTP_PROXY environment variable to determine proxy settings for connecting to HTTPS servers. You must always set HTTPS_PROXY if you intend to use a proxy to connect to an HTTPS server. (Note: This affects only connections made directly from Terraform CLI. Terraform providers are separate programs that make their own requests and may thus have different proxy configuration behaviors.)

  • Provider-defined sensitive attributes will now be redacted throughout the plan output. You may now see values redacted as (sensitive) that were previously visible, because sensitivity did not follow provider-defined sensitive attributes.

    If you are transforming a value and wish to force it not to be sensitive, such as if you are transforming a value in such a way that removes the sensitive data, we recommend using the new nonsensitive function to hint Terraform that the result is not sensitive.

  • The atlas backend, which was deprecated since Terraform v0.12, is now removed. (#26651)

  • We've upgraded the underlying TLS and certificate-related libraries that Terraform uses when making HTTPS requests to remote systems. This includes the usual tweaks to preferences for different cryptographic algorithms during handshakes and also some slightly-stricter checking of certificate syntax. These changes should not cause problems for correctly-implemented HTTPS servers, but can sometimes cause unexpected behavior changes with servers or middleboxes that don't comply fully with the relevant specifications.

ENHANCEMENTS:

  • config: A required_providers entry can now contain configuration_aliases to declare additional configuration aliases names without requirring a configuration block (#27739)
  • config: Improved type inference for conditional expressions. (#28116)
  • config: Provider-defined sensitive attributes will now be redacted throughout the plan output. (#28036)
  • config: New function one for concisely converting a zero-or-one element list/set into a single value that might be null. (#27454)
  • config: New functions sensitive and nonsensitive allow module authors to explicitly override Terraform's default infererence of value sensitivity for situations where it's too conservative or not conservative enough. (#27341)
  • config: Terraform will now emit a warning if you declare a backend block in a non-root module. Terraform has always ignored such declarations, but previously did so silently. This is a warning rather than an error only because it is sometimes convenient to temporarily use a root module as if it were a child module in order to test or debug its behavior separately from its main backend. (#26954)
  • config: Removed warning about interpolation-only expressions being deprecated, because terraform fmt now automatically fixes most cases that the warning would previously highlight. We still recommend using simpler expressions where possible, but the deprecation warning had caused a common confusion in the community that the interpolation syntax is always deprecated, rather than only in the interpolation-only case. (#27835)
  • config: The family of error messages with the summary "Invalid for_each argument" will now include some additional context about which external values contributed to the result, making it easier to find the root cause of the error. (#26747)
  • config: Terraform now does text processing using the rules and tables defined for Unicode 13. Previous versions were using Unicode 12 rules.
  • terraform init: Will now make suggestions for possible providers on some registry failures, and generally remind of required_providers on all registry failures. (#28014)
  • terraform init: Provider installation will now only attempt to rewrite .terraform.lock.hcl if it would contain new information. (#28230)
  • terraform init: New -lockfile=readonly option, which suppresses writing changes to the dependency lock file. Any installed provider packages must already be recorded in the lock file, or initialization will fail. Use this if you are managing the lock file via a separate process and want to avoid adding new checksums for existing dependencies. (#27630)
  • terraform show: Improved performance when rendering large plans as JSON. (#27998)
  • terraform validate: The JSON output now includes a code snippet object for each diagnostic. If present, this object contains an excerpt of the source code which triggered the diagnostic, similar to what Terraform would include in human-oriented diagnostic messages. (#28057)
  • cli: Terraform now uses UTF-8 and full VT mode even when running on Windows. Previously Terraform was using the "classic" Windows console API, which was far more limited in what formatting sequences it supported and which characters it could render. (#27487)
  • cli: Improved support for Windows console UI on Windows 10, including bold colors and underline for HCL diagnostics. (#26588)
  • cli: Diagnostic messages now have a vertical line along their left margin, which we hope will achieve a better visual hierarchy for sighted users and thus make it easier to see where the errors and warnings start and end in relation to other content that might be printed alongside. (#27343)
  • cli: Typing an invalid top-level command, like terraform destory instead of destroy, will now print out a specific error message about the command being invalid, rather than just printing out the usual help directory. (#26967)
  • cli: Plugin crashes will now be reported with more detail, pointing out the plugin name and the method call along with the stack trace (#26694)
  • cli: Core and Provider logs can now be enabled separately for debugging, using TF_LOG_CORE and TF_LOG_PROVIDER (#26685)
  • backend/azurerm: Support for authenticating as AzureAD users/roles. (#28181)
  • backend/pg: Now allows locking of each workspace separately, whereas before the locks were global across all workspaces. (#26924)

BUG FIXES:

  • config: Fix multiple upstream crashes with optional attributes and sensitive values. (#28116)
  • config: Fix various panics in the experimental defaults function. (#27979, #28067)
  • config: Fix crash with resources which have sensitive iterable attributes. (#28245)
  • config: Fix crash when referencing resources with sensitive fields that may be unknown. (#28180)
  • terraform validate: Validation now ignores providers that lack configuration, which is useful for validating modules intended to be called from other modules which therefore don't include their own provider configurations. (#24896)
  • terraform fmt: Fix fmt output when unwrapping redundant multi-line string interpolations (#28202)
  • terraform console: expressions using path (path.root, path.module) now return the same result as they would in a configuration (#27263)
  • terraform show: Fix crash when rendering JSON plans containing iterable unknown values. (#28253)
  • terraform show: fix issue with child_modules not properly displaying in certain circumstances. (#27352)
  • terraform state list: fix bug where nested modules' resources were missing (#27268)
  • terraform state mv: fix display names in errors and improve error when failing to target a whole resource (#27482)
  • terraform taint: show resource name in -allow-missing warning (#27501)
  • terraform untaint: show resource name in -allow-missing warning (#27502)
  • cli: All commands will now exit with an error if unable to read input at an interactive prompt. For example, this may happen when running in a non-interactive environment but without -input=false. Previously Terraform would behave as if the user entered an empty string, which often led to confusing results. (#26509)
  • cli: TF_LOG levels other than trace will now work reliably. (#26632)
  • core: Fix crash when trying to create a destroy plan with -refresh=false. (#28272)
  • core: Extend the Terraform plan file format to include information about sensitivity and required-replace. This ensures that the output of terraform show saved.tfplan matches terraform plan, and sensitive values are elided. (#28201)
  • core: Ensure that stored dependencies are retained when a resource is removed entirely from the configuration, and create_before_destroy ordering is preserved. (#28228)
  • core: Resources removed from the configuration will now be destroyed before their dependencies are updated. (#28165)
  • core: Refresh data sources while creating a destroy plan, in case their results are important for destroy operations. (#27408)
  • core: Fix missing deposed object IDs in apply logs (#27796)
  • backend/azurerm: Fix nil pointer crashes with some state operations. (#28181, #26721)
  • backend/azure: Fix interactions between state reading, state creating, and locking. (#26561)

EXPERIMENTS:

  • provider_sensitive_attrs: This experiment has now concluded, and its functionality is now on by default. If you were previously participating in this experiment then you can remove the experiment opt-in with no other necessary configuration changes.
  • There is now a terraform test command, which is currently an experimental feature serving as part of the Module Testing Experiment.

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