3258aa98e6
Update CHANGELOG.md
2016-11-08 19:42:30 -07:00
cfa4d9b63b
Merge pull request #9966 from fatmcgav/openstack_update_gophercloud_vendor
...
vendor: Update github.com/gophercloud/gophercloud
2016-11-08 19:40:02 -07:00
8eb116a183
update CHANGELOG
2016-11-08 16:20:28 -08:00
779d599b07
Merge pull request #9980 from hashicorp/update-hcl
...
vendor: update HCL for GH-8709
2016-11-08 16:17:30 -08:00
839e91756e
vendor: update HCL for GH-8709
2016-11-08 16:07:24 -08:00
2f0a7a99e6
update CHANGELOG
2016-11-08 15:59:43 -08:00
2b7177cfe7
Merge pull request #9607 from hashicorp/f-provider-stop-redo
...
terraform: ResourceProvider.Stop (redo)
2016-11-08 15:58:48 -08:00
b22f7d4b6b
update CHANGELOG
2016-11-08 15:57:43 -08:00
95871adca9
Merge pull request #9613 from hashicorp/b-accurate-forcenew
...
helper/schema: only mark "ForceNew" on resources that cause the ForceNew
2016-11-08 15:56:31 -08:00
e45debe0e5
helper/schema: only mark "ForceNew" on resources that cause the ForceNew
...
Fixes #2748
This changes the diff to only mark "forces new resource" on the fields
that actually caused the new resource, not every field that changed.
This makes diffs much more accurate.
I'd like to request a review but I'm going to defer merging until
Terraform 0.8. Changes like this are very possible to cause "diffs
didn't match" errors and I want some real world testing in a beta before
we hit prod with this.
2016-11-08 15:49:28 -08:00
645d3271f6
update CHANGELOG
2016-11-08 15:31:50 -08:00
261f0ee592
Merge pull request #9698 from hashicorp/b-simple-var
...
terraform: disallow simple variables ("foo")
2016-11-08 15:30:31 -08:00
45b2bc1a27
update CHANGELOG
2016-11-08 15:29:56 -08:00
646b3c1b68
Merge pull request #9158 from hashicorp/f-vault-provider
...
Vault Provider
2016-11-08 15:27:33 -08:00
11b05de147
Merge pull request #9975 from hashicorp/paddy_fix_google_sidebar
...
Fix typo in the Google sidebar.
2016-11-08 14:50:11 -08:00
9d4bedee0c
Fix typo in the Google sidebar.
...
We have Google Compute Platform when we really mean Google Cloud
Platform. Whoops. I totally let this sneak in in #9969 .
2016-11-08 14:09:17 -08:00
838fe2af9b
terraform: address go vet
2016-11-08 14:04:57 -08:00
bcc67fd135
terraform: uncomment a test that we were waiting on
...
terraform: remove final TODO
2016-11-08 13:59:31 -08:00
19350d617d
terraform: references can have backups
...
terraform: more specific resource references
terraform: outputs need to know about the new reference format
terraform: resources w/o a config still have a referencable name
2016-11-08 13:59:30 -08:00
c0d2493156
terraform: remove a complete TODO
2016-11-08 13:59:30 -08:00
337abe3f62
terraform: enable plan shadow graph
2016-11-08 13:59:30 -08:00
1efdba9b30
terraform: target at the right moment to get the right values
2016-11-08 13:59:30 -08:00
bb9820cc0b
terraform: enable targeting on expanded nodes
2016-11-08 13:59:29 -08:00
d29844969a
terraform: test fixture needs to use variable so its not pruned
2016-11-08 13:59:29 -08:00
f6df1edeb4
terraform: proper "what to orphan" on zero/one boundary logic
2016-11-08 13:59:29 -08:00
f95f904ba8
terraform: add TargetsTransformer to plan
2016-11-08 13:59:29 -08:00
a2d71388c2
terraform: output the exact instance for prevent destroy on count
2016-11-08 13:59:28 -08:00
e6be4fefe8
terraform: reference an output so it isn't pruned during plan
2016-11-08 13:59:28 -08:00
6914d605c8
terraform: connect references
2016-11-08 13:59:28 -08:00
091264e4ba
terraform: OrphanResourceCountTransformer for orphaning extranneous
...
instances
2016-11-08 13:59:27 -08:00
97b7915b8f
terraform: fix zero/one boundary for resource counts
2016-11-08 13:59:27 -08:00
bd8802e08d
terraform: plan orphan destruction
2016-11-08 13:59:27 -08:00
2608c5f282
terraform: transform for adding orphan resources + tests
2016-11-08 13:59:27 -08:00
6337829786
terraform: expand count in plan
2016-11-08 13:59:26 -08:00
4cdaf6f687
terraform: ResourceTransformer to ResourceTransformerOld
2016-11-08 13:59:26 -08:00
d7aa59be3c
terraform: begin NodePlannableResource
2016-11-08 13:59:26 -08:00
dbac0785bc
terraform: tests for the plan graph builder
2016-11-08 13:59:26 -08:00
7557e6e70a
terraform: ConfigTransformer
2016-11-08 13:59:25 -08:00
4f0d68dda4
terraform: PlanGraphBuilder
2016-11-08 13:59:17 -08:00
b0772b9131
provider/scaleway: retry volume attachment create/ destroy ( #9972 )
...
this PR fixes a flakyness in the `scaleway_volume_attachment` resource, as
described below:
when attaching/ detaching a volume from a `scaleway_server`, the server needs to
be stopped. even though the code already waits for the server to be stopped, the
`PatchServer` calls gets a `400 server is being stopped or rebooted` error
response.
If the API returns the `400` we bail, leaving terraform in a broken state.
Assuming this is the only error that the API might return to us, as the payload
itself is correct, this retry behaviour should fix the issue.
\cc @stack72 PTAL
2016-11-08 21:57:33 +00:00
d7ab7c029b
Update CHANGELOG.md
2016-11-08 21:57:18 +00:00
a466aaf639
Merge pull request #9969 from cblecker/f-google-docs-sidebar-update
...
provider/google: Add google_iam_policy and google_project to sidebar
2016-11-08 13:53:53 -08:00
ce4ff06d25
terraform: prepare Plan for shadowing
2016-11-08 13:28:50 -08:00
f9fee4106f
terraform: Diff.Prune
2016-11-08 13:28:50 -08:00
9890a2ee91
terraform: prune orphan outputs in old graph
...
This makes the old graph also prune orphan outputs in modules.
This will fix shadow graph errors such as #9905 since the old graph will
also behave correctly in these scenarios.
Luckily, because orphan outputs don't rely on anything, we were able to
simply use the same transformer!
2016-11-08 13:24:09 -08:00
dfab66e550
Update CHANGELOG.md
2016-11-08 13:02:33 -08:00
3bc26db4e0
Merge pull request #9968 from hashicorp/b-destroy-self-ref
...
terraform: destroy edges should never point to self
2016-11-08 13:01:56 -08:00
2eeb9fbf86
Add google_iam_policy and google_project to sidebar
2016-11-08 12:55:53 -08:00
dd76c99301
Update CHANGELOG.md
2016-11-08 14:32:54 -06:00
fb29b6a2dc
terraform: destroy edges should never point to self
...
Fixes #9920
This was an issue caught with the shadow graph. Self references in
provisioners were causing a self-edge on destroy apply graphs.
We need to explicitly check that we're not creating an edge to ourself.
This is also how the reference transformer works.
2016-11-08 12:27:33 -08:00
Joe Topjian