Downloads:

592,448

Downloads of v 0.6.0:

354

Last Update:

09 Jul 2015

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

terraform

Terraform

This is not the latest version of Terraform available.

  • 1
  • 2
  • 3

0.6.0 | Updated: 09 Jul 2015

Downloads:

592,448

Downloads of v 0.6.0:

354

Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Tags:

terraform

  • 1
  • 2
  • 3
Terraform 0.6.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.6.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.6.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.6.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.6.0'
end

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


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

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


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

This package was approved by moderator ferventcoder on 28 Dec 2015.

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://dl.bintray.com/mitchellh/terraform/terraform_0.6.0_windows_386.zip'
$url64bit = 'https://dl.bintray.com/mitchellh/terraform/terraform_0.6.0_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.

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.6.0 (June 30, 2015)

BACKWARDS INCOMPATIBILITIES:

  • command/push: If a variable is already set within Atlas, it won't be
    updated unless the -overwrite flag is present [GH-2373]
  • connection/ssh: The agent field now defaults to true if
    the SSH_AGENT_SOCK environment variable is present. In other words,
    ssh-agent support is now opt-out instead of opt-in functionality. [GH-2408]
  • provider/aws: If you were setting access and secret key to blank ("")
    to force Terraform to load credentials from another source such as the
    EC2 role, this will now error. Remove the blank lines and Terraform
    will load from other sources.
  • concat() has been repurposed to combine lists instead of strings (old behavior
    of joining strings is maintained in this version but is deprecated, strings
    should be combined using interpolation syntax, like "${var.foo}{var.bar}")
    [GH-1790]

FEATURES:

  • New provider: azure [GH-2052, GH-2053, GH-2372, GH-2380, GH-2394, GH-2515, GH-2530, GH-2562]
  • New resource: aws_autoscaling_notification [GH-2197]
  • New resource: aws_autoscaling_policy [GH-2201]
  • New resource: aws_cloudwatch_metric_alarm [GH-2201]
  • New resource: aws_dynamodb_table [GH-2121]
  • New resource: aws_ecs_cluster [GH-1803]
  • New resource: aws_ecs_service [GH-1803]
  • New resource: aws_ecs_task_definition [GH-1803, GH-2402]
  • New resource: aws_elasticache_parameter_group [GH-2276]
  • New resource: aws_flow_log [GH-2384]
  • New resource: aws_iam_group_association [GH-2273]
  • New resource: aws_iam_policy_attachment [GH-2395]
  • New resource: aws_lambda_function [GH-2170]
  • New resource: aws_route53_delegation_set [GH-1999]
  • New resource: aws_route53_health_check [GH-2226]
  • New resource: aws_spot_instance_request [GH-2263]
  • New resource: cloudstack_ssh_keypair [GH-2004]
  • New remote state backend: swift: You can now store remote state in
    a OpenStack Swift. [GH-2254]
  • command/output: support display of module outputs [GH-2102]
  • core: keys() and values() funcs for map variables [GH-2198]
  • connection/ssh: SSH bastion host support and ssh-agent forwarding [GH-2425]

IMPROVEMENTS:

  • core: HTTP remote state now accepts skip_cert_verification
    option to ignore TLS cert verification. [GH-2214]
  • core: S3 remote state now accepts the 'encrypt' option for SSE [GH-2405]
  • core: plan now reports sum of resources to be changed/created/destroyed [GH-2458]
  • core: Change string list representation so we can distinguish empty, single
    element lists [GH-2504]
  • core: Properly close provider and provisioner plugin connections [GH-2406, GH-2527]
  • provider/aws: AutoScaling groups now support updating Load Balancers without
    recreation [GH-2472]
  • provider/aws: Allow more in-place updates for ElastiCache cluster without recreating
    [GH-2469]
  • provider/aws: ElastiCache Subnet Groups can be updated
    without destroying first [GH-2191]
  • provider/aws: Normalize certificate_chain in aws_iam_server_certificate to
    prevent unnecessary replacement. [GH-2411]
  • provider/aws: aws_instance supports `monitoring' [GH-2489]
  • provider/aws: aws_launch_configuration now supports enable_monitoring [GH-2410]
  • provider/aws: Show outputs after terraform refresh [GH-2347]
  • provider/aws: Add backoff/throttling during DynamoDB creation [GH-2462]
  • provider/aws: Add validation for aws_vpc.cidr_block [GH-2514]
  • provider/aws: Add validation for aws_db_subnet_group.name [GH-2513]
  • provider/aws: Add validation for aws_db_instance.identifier [GH-2516]
  • provider/aws: Add validation for aws_elb.name [GH-2517]
  • provider/aws: Add validation for aws_security_group (name+description) [GH-2518]
  • provider/aws: Add validation for aws_launch_configuration [GH-2519]
  • provider/aws: Add validation for aws_autoscaling_group.name [GH-2520]
  • provider/aws: Add validation for aws_iam_role.name [GH-2521]
  • provider/aws: Add validation for aws_iam_role_policy.name [GH-2552]
  • provider/aws: Add validation for aws_iam_instance_profile.name [GH-2553]
  • provider/aws: aws_auto_scaling_group.default_cooldown no longer requires
    resource replacement [GH-2510]
  • provider/aws: add AH and ESP protocol integers [GH-2321]
  • provider/docker: docker_container has the privileged
    option. [GH-2227]
  • provider/openstack: allow OS_AUTH_TOKEN environment variable
    to set the openstack api_key field [GH-2234]
  • provider/openstack: Can now configure endpoint type (public, admin,
    internal) [GH-2262]
  • provider/cloudstack: cloudstack_instance now supports projects [GH-2115]
  • provisioner/chef: Added a os_type to specifically specify the target OS [GH-2483]
  • provisioner/chef: Added a ohai_hints option to upload hint files [GH-2487]

BUG FIXES:

  • core: lifecycle prevent_destroy can be any value that can be
    coerced into a bool [GH-2268]
  • core: matching provider types in sibling modules won't override
    each other's config. [GH-2464]
  • core: computed provider configurations now properly validate [GH-2457]
  • core: orphan (commented out) resource dependencies are destroyed in
    the correct order [GH-2453]
  • core: validate object types in plugins are actually objects [GH-2450]
  • core: fix -no-color flag in subcommands [GH-2414]
  • core: Fix error of 'attribute not found for variable' when a computed
    resource attribute is used as a parameter to a module [GH-2477]
  • core: moduled orphans will properly inherit provider configs [GH-2476]
  • core: modules with provider aliases work properly if the parent
    doesn't implement those aliases [GH-2475]
  • core: unknown resource attributes passed in as parameters to modules
    now error [GH-2478]
  • core: better error messages for missing variables [GH-2479]
  • core: removed set items now properly appear in diffs and applies [GH-2507]
  • core: '*' will not be added as part of the variable name when you
    attempt multiplication without a space [GH-2505]
  • core: fix target dependency calculation across module boundaries [GH-2555]
  • command/*: fixed bug where variable input was not asked for unset
    vars if terraform.tfvars existed [GH-2502]
  • command/apply: prevent output duplication when reporting errors [GH-2267]
  • command/apply: destroyed orphan resources are properly counted [GH-2506]
  • provider/aws: loading credentials from the environment (vars, EC2 role,
    etc.) is more robust and will not ask for credentials from stdin [GH-1841]
  • provider/aws: fix panic when route has no cidr_block [GH-2215]
  • provider/aws: fix issue preventing destruction of IAM Roles [GH-2177]
  • provider/aws: fix issue where Security Group Rules could collide and fail
    to save to the state file correctly [GH-2376]
  • provider/aws: fix issue preventing destruction self referencing Securtity
    Group Rules [GH-2305]
  • provider/aws: fix issue causing perpetual diff on ELB listeners
    when non-lowercase protocol strings were used [GH-2246]
  • provider/aws: corrected frankfurt S3 website region [GH-2259]
  • provider/aws: aws_elasticache_cluster port is required [GH-2160]
  • provider/aws: Handle AMIs where RootBlockDevice does not appear in the
    BlockDeviceMapping, preventing root_block_device from working [GH-2271]
  • provider/aws: fix terraform show with remote state [GH-2371]
  • provider/aws: detect instance_type drift on aws_instance [GH-2374]
  • provider/aws: fix crash when security_group_rule referenced non-existent
    security group [GH-2434]
  • provider/aws: aws_launch_configuration retries if IAM instance
    profile is not ready yet. [GH-2452]
  • provider/aws: fqdn is populated during creation for aws_route53_record [GH-2528]
  • provider/aws: retry VPC delete on DependencyViolation due to eventual
    consistency [GH-2532]
  • provider/aws: VPC peering connections in "failed" state are deleted [GH-2544]
  • provider/aws: EIP deletion works if it was manually disassociated [GH-2543]
  • provider/aws: elasticache_subnet_group.subnet_ids is now a required argument [GH-2534]
  • provider/aws: handle nil response from VPN connection describes [GH-2533]
  • provider/cloudflare: manual record deletion doesn't cause error [GH-2545]
  • provider/digitalocean: handle case where droplet is deleted outside of
    terraform [GH-2497]
  • provider/dme: No longer an error if record deleted manually [GH-2546]
  • provider/docker: Fix issues when using containers with links [GH-2327]
  • provider/openstack: fix panic case if API returns nil network [GH-2448]
  • provider/template: fix issue causing "unknown variable" rendering errors
    when an existing set of template variables is changed [GH-2386]
  • provisioner/chef: improve the decoding logic to prevent parameter not found errors [GH-2206]

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