Downloads:

373,272

Downloads of v 0.6.10:

302

Last Update:

02 Feb 2016

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

terraform

Terraform

This is not the latest version of Terraform available.

0.6.10 | Updated: 02 Feb 2016

Downloads:

373,272

Downloads of v 0.6.10:

302

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

terraform

Terraform 0.6.10

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.6.10
    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.6.10'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: terraform,
    Version: 0.6.10,
    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.6.10'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install terraform version="0.6.10" 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 Feb 2016.

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
$url = 'https://releases.hashicorp.com/terraform/0.6.10/terraform_0.6.10_windows_386.zip'
$url64bit = 'https://releases.hashicorp.com/terraform/0.6.10/terraform_0.6.10_windows_amd64.zip'
$unzipLocation = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

Install-ChocolateyZipPackage "terraform" "$url" "$unzipLocation" "$url64bit"
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.6 3356 Wednesday, February 10, 2021 Approved
Terraform 0.14.5 4868 Wednesday, January 27, 2021 Approved
Terraform 0.14.4 5332 Sunday, January 10, 2021 Approved
Terraform 0.14.3 4490 Sunday, December 20, 2020 Approved
Terraform 0.14.2 3734 Wednesday, December 9, 2020 Approved
Terraform 0.14.1 52 Wednesday, December 9, 2020 Approved
Terraform 0.14.0 1495 Tuesday, December 8, 2020 Approved
Terraform 0.13.6 379 Sunday, January 10, 2021 Approved
Terraform 0.13.5 13132 Thursday, November 5, 2020 Approved

0.6.10 (January 27, 2016)

BACKWARDS INCOMPATIBILITIES / NOTES:

  • The -module-depth flag available on plan, apply, show, and graph now defaults to -1, causing
    resources within modules to be expanded in command output. This is only a cosmetic change; it does not affect
    any behavior.
  • This release includes a bugfix for ${} interpolation escaping. These strings are now properly converted to ${}
    during interpolation. This may cause diffs on existing configurations in certain cases.
  • Users of consul_keys should note that the value sub-attribute of key will no longer be updated with the remote value of the key. It should be only used to set a key in Consul K/V. To reference key values, use the var attribute.
  • The 0.6.9 release contained a regression in aws_autoscaling_group capacity waiting behavior for configs where min_elb_capacity != desired_capacity or min_size != desired_capacity. This release remedies that regression by un-deprecating min_elb_capacity and restoring the prior behavior.

FEATURES:

  • New resource: aws_lambda_alias [GH-4664]
  • New resource: aws_redshift_cluster [GH-3862]
  • New resource: aws_redshift_parameter_group [GH-3862]
  • New resource: aws_redshift_security_group [GH-3862]
  • New resource: aws_redshift_subnet_group [GH-3862]
  • New resource: azurerm_cdn_endpoint [GH-4759]
  • New resource: azurerm_cdn_profile [GH-4740]
  • New resource: azurerm_network_interface [GH-4598]
  • New resource: azurerm_network_security_rule [GH-4586]
  • New resource: azurerm_route_table [GH-4602]
  • New resource: azurerm_route [GH-4604]
  • New resource: azurerm_storage_account [GH-4698]
  • New resource: azurerm_storage_blob [GH-4862]
  • New resource: azurerm_storage_container [GH-4862]
  • New resource: azurerm_storage_queue [GH-4862]
  • New resource: azurerm_subnet [GH-4595]
  • New resource: docker_network [GH-4483]
  • New resource: docker_volume [GH-4483]
  • New resource: google_sql_user [GH-4669]

IMPROVEMENTS:

  • core: Add sha256() interpolation function [GH-4704]
  • core: Validate lifecycle keys to show helpful error messages whe they are mistypes [GH-4745]
  • core: Default module-depth parameter to -1, which expands resources within modules in command output [GH-4763]
  • core: Variable types may now be specified explicitly using the type argument [GH-4795]
  • provider/aws: Add new parameters az_mode and availability_zone(s) in ElastiCache [GH-4631]
  • provider/aws: Allow ap-northeast-2 (Seoul) as valid region [GH-4637]
  • provider/aws: Limit SNS Topic Subscription protocols [GH-4639]
  • provider/aws: Add support for configuring logging on aws_s3_bucket resources [GH-4482]
  • provider/aws: Add AWS Classiclink for AWS VPC resource [GH-3994]
  • provider/aws: Supporting New AWS Route53 HealthCheck additions [GH-4564]
  • provider/aws: Store instance state [GH-3261]
  • provider/aws: Add support for updating ELB availability zones and subnets [GH-4597]
  • provider/aws: Enable specifying aws s3 redirect protocol [GH-4098]
  • provider/aws: Added support for encrypted on ebs_block_devices in Launch Configurations [GH-4481]
  • provider/aws: Retry Listener Creation for ELBs [GH-4825]
  • provider/aws: Add support for creating Managed Microsoft Active Directory
    and Directory Connectors [GH-4388]
  • provider/aws: Mark some aws_db_instance fields as optional [GH-3138]
  • provider/digitalocean: Add support for reassigning digitalocean_floating_ip resources [GH-4476]
  • provider/dme: Add support for Global Traffic Director locations on dme_record resources [GH-4305]
  • provider/docker: Add support for adding host entries on docker_container resources [GH-3463]
  • provider/docker: Add support for mounting named volumes on docker_container resources [GH-4480]
  • provider/google: Add content field to bucket object [GH-3893]
  • provider/google: Add support for named_port blocks on google_compute_instance_group_manager resources [GH-4605]
  • provider/openstack: Add "personality" support to instance resource [GH-4623]
  • provider/packet: Handle external state changes for Packet resources gracefully [GH-4676]
  • provider/tls: tls_private_key now exports attributes with public key in both PEM and OpenSSH format [GH-4606]
  • provider/vdc: Add allow_unverified_ssl for connections to vCloud API [GH-4811]
  • state/remote: Allow KMS Key Encryption to be used with S3 backend [GH-2903]

BUG FIXES:

  • core: Fix handling of literals with escaped interpolations ${var} [GH-4747]
  • core: Fix diff mismatch when RequiresNew field and list both change [GH-4749]
  • core: Respect module target path argument on terraform init [GH-4753]
  • core: Write planfile even on empty plans [GH-4766]
  • core: Add validation error when output is missing value field [GH-4762]
  • core: Fix improper handling of orphan resources when targeting [GH-4574]
  • core: Properly handle references to computed set attributes [GH-4840]
  • config: Detect a specific JSON edge case and show a helpful workaround [GH-4746]
  • provider/openstack: Ensure valid Security Group Rule attribute combination [GH-4466]
  • provider/openstack: Don't put fixed_ip in port creation request if not defined [GH-4617]
  • provider/google: Clarify SQL Database Instance recent name restriction [GH-4577]
  • provider/google: Split Instance network interface into two fields [GH-4265]
  • provider/aws: Error with empty list item on security group [GH-4140]
  • provider/aws: Fix issue with detecting drift in AWS Security Groups rules [GH-4779]
  • provider/aws: Trap Instance error from mismatched SG IDs and Names [GH-4240]
  • provider/aws: EBS optimised to force new resource in AWS Instance [GH-4627]
  • provider/aws: Wait for NACL rule to be visible [GH-4734]
  • provider/aws: default_result on aws_autoscaling_lifecycle_hook resources is now computed [GH-4695]
  • provider/aws: fix ASG capacity waiting regression by un-deprecating min_elb_capacity [GH-4864]
  • provider/consul: fix several bugs surrounding update behavior [GH-4787]
  • provider/mailgun: Handle the fact that the domain destroy API is eventually consistent [GH-4777]
  • provider/template: Fix race causing sporadic crashes in template_file with count > 1 [GH-4694]
  • provider/template: Add support for updating template_cloudinit_config resources [GH-4757]
  • provisioner/chef: Add ENV['no_proxy'] to chef provisioner if no_proxy is detected [GH-4661]

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