Downloads:

377,756

Downloads of v 0.10.0:

931

Last Update:

03 Aug 2017

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

terraform hashicorp

Terraform

This is not the latest version of Terraform available.

0.10.0 | Updated: 03 Aug 2017

Downloads:

377,756

Downloads of v 0.10.0:

931

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

terraform hashicorp

Terraform 0.10.0

This is not the latest version of Terraform available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

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:

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade terraform -y --source="'STEP 3 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 terraform -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Ensure terraform installed
  win_chocolatey:
    name: terraform
    state: present
    version: 0.10.0
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'terraform' do
  action    :install
  version  '0.10.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: terraform,
    Version: 0.10.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller terraform
{
   Name     = 'terraform'
   Ensure   = 'Present'
   Version  = '0.10.0'
   Source   = 'STEP 3 URL'
}

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


package { 'terraform':
  provider => 'chocolatey',
  ensure   => '0.10.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install terraform version="0.10.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 03 Aug 2017.

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 
$checksum = 'a118202c72a8404d406e8250e2163dcf218dd31fe16f846ac3996854fa3c7613'
$checksum64 = 'd9697b0153bed48af4b077c711197f8fca1163e94d5a1c067b077a02201be25f'
$url = 'https://releases.hashicorp.com/terraform/0.10.0/terraform_0.10.0_windows_386.zip'
$url64bit = 'https://releases.hashicorp.com/terraform/0.10.0/terraform_0.10.0_windows_amd64.zip'
$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-*.*"
    }
  }
}

Install-ChocolateyZipPackage -PackageName "terraform" -Url "$url" -UnzipLocation "$unzipLocation" -Url64 "$url64bit" -ChecksumType 'sha256' -Checksum "$checksum" -Checksum64 "$checksum64"
tools\chocolateyInstall.ps1.orig
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.

Version Downloads Last Updated Status
Terraform 0.14.7 4642 Thursday, February 18, 2021 Approved
Terraform 0.14.6 3392 Wednesday, February 10, 2021 Approved
Terraform 0.14.5 4907 Wednesday, January 27, 2021 Approved
Terraform 0.14.4 5340 Sunday, January 10, 2021 Approved
Terraform 0.14.3 4548 Sunday, December 20, 2020 Approved
Terraform 0.14.2 3886 Wednesday, December 9, 2020 Approved
Terraform 0.14.1 55 Wednesday, December 9, 2020 Approved
Terraform 0.14.0 1503 Tuesday, December 8, 2020 Approved
Terraform 0.13.6 432 Sunday, January 10, 2021 Approved
Terraform 0.13.5 13501 Thursday, November 5, 2020 Approved

0.10.0 (August 2, 2017)

This is the complete 0.9.11 to 0.10.0 CHANGELOG

BACKWARDS INCOMPATIBILITIES / NOTES:

  • A new flag -auto-approve has been added to terraform apply. This flag controls whether an interactive approval is applied before making the changes in the plan. For now this flag defaults to true to preserve previous behavior, but this will become the new default in a future version. We suggest that anyone running terraform apply in wrapper scripts or automation refer to the upgrade guide to learn how to prepare such wrapper scripts for the later breaking change.
  • The validate command now checks that all variables are specified by default. The validation will fail by default if that's not the case. (#13872)
  • terraform state rm now requires at least one argument. Previously, calling it with no arguments would remove all resources from state, which is consistent with the other terraform state commands but unlikely enough that we considered it better to be inconsistent here to reduce the risk of accidentally destroying the state.
  • Terraform providers are no longer distributed as part of the main Terraform distribution. Instead, they are installed automatically as part of running terraform init. It is therefore now mandatory to run terraform init before any other operations that use provider plugins, to ensure that the required plugins are installed and properly initialized.
  • The terraform env family of commands have been renamed to terraform workspace, in response to feedback that the previous naming was confusing due to collisions with other concepts of the same name. The commands still work the same as they did before, and the env subcommand is still supported as an alias for backward compatibility. The env subcommand will be removed altogether in a future release, so it's recommended to update any automation or wrapper scripts that use these commands.
  • The terraform init subcommand no longer takes a SOURCE argument to copy to the current directory. The behavior has been changed to match that of plan and apply, so that a configuration can be provided as an argument on the commandline while initializing the current directory. If a module needs to be copied into the current directory before initialization, it will have to be done manually.
  • The -target option available on several Terraform subcommands has changed behavior and now matches potentially more resources. In particular, given an option -target=module.foo, resources in any descendent modules of foo will also be targeted, where before this was not true. After upgrading, be sure to look carefully at the set of changes proposed by terraform plan when using -target to ensure that the target is being interpreted as expected. Note that the -target argument is offered for exceptional circumstances only and is not intended for routine use.
  • The import command requires that imported resources be specified in the configuration file. Previously, users were encouraged to import a resource and then write the configuration block for it. This creates the risk that users could import a resource and subsequently create no configuration for it, which results in Terraform deleting the resource. If the imported resource is not present in the configuration file, the import command will fail.

FEATURES:

  • Separate Provider Releases: Providers are now released independently from Terraform.
  • Automatic Provider Installation: The required providers will be automatically installed during terraform init.
  • Provider Constraints: Provider are now versioned, and version constraints may be declared in the configuration.

PROVIDERS:

  • Providers now maintain their own CHANGELOGs in their respective repositories: terraform-providers

IMPROVEMENTS:

  • cli: Add a -from-module flag to terraform init to re-introduce the legacy terraform init behavior of fetching a module. (#15666)
  • backend/s3: Add workspace_key_prefix to allow a user-configurable prefix for workspaces in the S3 Backend. (#15370)
  • cli: terraform apply now has an option -auto-approve=false that produces an interactive prompt to approve the generated plan. This will become the default workflow in a future Terraform version. (#7251)
  • cli: terraform workspace show command prints the current workspace name in a way that's more convenient for processing in wrapper scripts. (#15157)
  • cli: terraform state rm will now generate an error if no arguments are passed, whereas before it treated it as an open resource address selecting all resources (#15283)
  • cli: Files in the config directory ending in .auto.tfvars are now loaded automatically (in lexicographical order) in addition to the single terraform.tfvars file that auto-loaded previously. (#13306)
  • Providers no longer in the main Terraform distribution; installed automatically by init instead (#15208)
  • cli: terraform env command renamed to terraform workspace (#14952)
  • cli: terraform init command now has -upgrade option to download the latest versions (within specified constraints) of modules and provider plugins.
  • cli: The -target option to various Terraform operation can now target resources in descendent modules. (#15314)
  • cli: Minor updates to terraform plan output: use standard resource address syntax, more visually-distinct -/+ actions, and more (#15362)
  • config: New interpolation function contains, to find if a given string exists in a list of strings. (#15322)

BUG FIXES:

  • provisioner/chef: fix panic (#15617)
  • Don't show a message about the path to the state file if the state is remote (#15435)
  • Fix crash when terraform graph is run with no configuration (#15588)
  • Handle correctly the .exe suffix on locally-compiled provider plugins on Windows systems. (#15587)
  • config: Fixed a parsing issue in the interpolation language HIL that was causing misinterpretation of literal strings ending with escaped backslashes (#15415)
  • core: the S3 Backend was failing to remove the state file checksums from DynamoDB when deleting a workspace (#15383)
  • core: Improved reslience against crashes for a certain kind of inconsistency in the representation of list values in state. (#15390)
  • core: Display correct to and from backends in copy message when migrating to new remote state (#15318)
  • core: Fix a regression from 0.9.6 that was causing the tally of resources to create to be double-counted sometimes in the plan output (#15344)
  • cli: the state rm and mv commands were always loading a state from a Backend, and ignoring the -state flag (#15388)
  • cli: certain prompts in terraform init were respecting -input=false but not the TF_INPUT environment variable (#15391)
  • state: Further work, building on #15423, to improve the internal design of the state managers to make this code more maintainable and reduce the risk of regressions; this may lead to slight changes to the number of times Terraform writes to remote state and how the serial is implemented with respect to those writes, which does not affect outward functionality but is worth noting if you log or inspect state updates for debugging purposes.
  • config: Interpolation function cidrhost was not correctly calcluating host addresses under IPv6 CIDR prefixes (#15321)
  • provisioner/chef: Prevent a panic while trying to read the connection info (#15271)
  • provisioner/file: Refactor the provisioner validation function to prevent false positives (#15273)

INTERNAL CHANGES:

  • helper/schema: Actively disallow reserved field names in schema (#15522)
  • helper/schema: Force field names to be alphanum lowercase + underscores (#15562)

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