This project is mirrored from https://:*****@github.com/hashicorp/terraform.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
- 21 Mar, 2017 16 commits
-
-
Dana Hoffman authored
-
Dana Hoffman authored
-
Dana Hoffman authored
provider/google: add support for a few more fields in NodeConfig
-
Dana Hoffman authored
-
Mitchell Hashimoto authored
terraform: convert empty path to root path in V1 state
-
Mitchell Hashimoto authored
-
Paul Stack authored
-
Paul Stack authored
machines Fixes: #12898 The way aws_instance works is that we call the Create func then the Update func then the Read func. The way the work to implement the change to iam_instance_profile was added meant that when a machine was created with an iam_instance_profile, it would then try and update that iam_instance_profile because the state hadn't been updated at that point We have changed the Update func to only check for the change to iam_instance_profile when it *is an existing machine* - this will solve the problem of those bringing up new machines and getting hit with the permissions error As requested, added a test that adds an IAM Instance Profile from creation ``` % make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSInstance_withIamInstanceProfile' ==> Checking that code complies with gofmt requirements... go generate $(go list ./... | grep -v /terraform/vendor/) 2017/03/21 17:51:32 Generated command/internal_plugin_list.go TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSInstance_withIamInstanceProfile -timeout 120m === RUN TestAccAWSInstance_withIamInstanceProfile --- PASS: TestAccAWSInstance_withIamInstanceProfile (154.29s) PASS ok github.com/hashicorp/terraform/builtin/providers/aws 154.325s ```
-
Mitchell Hashimoto authored
terraform: V1 to V2 upgrade should treat nil path as root path
-
Mitchell Hashimoto authored
It appears there are no tests for this as far as I can find. We change V1 states (very old) to assume a nil path is a root path. Staet.Validate() later will catch any duplicate paths.
-
Paul Stack authored
-
Paul Stack authored
Fixes: #12914 this is just a simple guard clause to prevent the hash from including an optional value by default
-
James Bardin authored
ignore_changes causes keys in other flatmapped objects to be lost from diff
-
James Bardin authored
When transforming a diff from DestroyCreate to a simple Update, ignore_changes can cause keys from flatmapped objects to be filtered form the diff. We need to filter each flatmapped container as a whole to ensure that unchanged keys aren't lost in the update.
-
Sander van Harmelen authored
-
Yukihiko SAWANOBORI authored
* add option zone_id - Ref: http://docs.idcf.jp/cloud/api/address/#listpublicipaddresses * Exclusion of `network_id`, `vpc_id` and `zone_id` * Revert "Exclusion of `network_id`, `vpc_id` and `zone_id`" This reverts commit 9684c8b0b65b3353aea4e0bfbeaf21986282812b. * remove zone_id from one of required option.
-
- 20 Mar, 2017 24 commits
-
-
Dana Hoffman authored
-
James Bardin authored
-
James Bardin authored
ignore_changes is causing changes in other flatmapped sets to be filtered out incorrectly. This required fixing the testDiffFn to create diffs which include the old value, breaking one other test.
-
Paul Stack authored
-
James Nugent authored
Many cloud services prevent duplicate key pairs with different names. Among them are Digital Ocean, Joyent Triton and Packet. Consequently, if tests leave dangling resources it is not enough to simply randomise the name, the entire key material must be regenerated. This commit adds a helper method that returns a new randomly generated key pair, where the public key material is formatted in OpenSSH "authorized keys" format, and the private key material is PEM encoded.
-
clint shryock authored
-
Mitchell Hashimoto authored
-
Mitchell Hashimoto authored
command: remove legacy remote state on migration
-
clint shryock authored
-
Paul Stack authored
-
Dylan Conrad Johnson authored
* add nil check when assingment from a doc parameter to the param map * remove println
-
ryno75 authored
-
Benjamin Boudreau authored
-
Mitchell Hashimoto authored
Fixes #12871 We were forgetting to remove the legacy remote state from the actual state value when migrating. This only causes an issue when saving a plan since the plan contains the state itself and causes an error where both a backend + legacy state exist. If saved plans aren't used this causes no noticable issue. Due to buggy upgrades already existing in the wild, I also added code to clear the remote section if it exists in a standard unchanged backend
-
Paul Stack authored
-
Gauthier Wallet authored
-
Mitchell Hashimoto authored
[DOCUMENTATION] Change version of Debian image
-
Paul Stack authored
-
Gauthier Wallet authored
-
Paul Stack authored
-
Gauthier Wallet authored
* provider/aws: Added Usage Plan Key resource * provider/aws: Added usage plan import documentation
-
Brett Slaski authored
The -u flag didn't work for me and based on documentation should be -update, which did work. Makes getting started docs more accurate.
-
Paul Stack authored
-
Joshua Spence authored
Adds support for `name_prefix` to the `aws_autoscaling_group` and `aws_elb` resources. Unfortunately when using `name_prefix` with `aws_elb`, this means that the specified prefix can only be a maximum of 6 characters in length. This is because the maximum length for an ELB name is 32 characters, and `resource.PrefixedUniqueId` generates a 26-character unique identifier. I was considering truncating the unique identifier to allow for a longer `name_prefix`, but I worried that doing so would increase the risk of collisions.
-