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.
- 16 Sep, 2020 7 commits
-
-
hashicorp-ci authored
-
James Bardin authored
-
James Bardin authored
0.13 backport of #26264
-
James Bardin authored
0.13 backport of #26263
-
James Bardin authored
While this was easier to spot during plan, it is also possible to evaluate resources with 0 instances during apply as well. This doesn't effect the failure when scaling CBD instances, it only changes the fact that the inconsistent value is no longer unknown.
-
James Bardin authored
Correct the initial test state, and expand the test to cause a cycle without the previous fix.
-
James Bardin authored
When there is only a destroy node, there is no descendent to check for "forced CBD", so we can only rely on the state to verify.
-
- 15 Sep, 2020 2 commits
-
-
Kristin Laemmert authored
-
Kristin Laemmert authored
* go mod tidy * vendor: upgrade go-userdirs library
-
- 14 Sep, 2020 5 commits
-
-
James Bardin authored
-
James Bardin authored
Backport 26192
-
James Bardin authored
When applying a plan, a forced CreateBeforeDestroy may not be set during the apply walk when downstream resources are no longer present in the graph. We still need to stick to that plan, and both the NodeApplyableResourceInstance EvalTree and the individual Eval nodes need to operate on that planned value. Ensure that we always check for an existing plan when determining CreateBeforeDestroy status. This must happen in 2 different code paths due to the eval node pattern currently in-use. Future refactoring may be able to unify these code-paths to make this less fragile.
-
James Bardin authored
If a resource is forced CreateBeforeDestroy from a dependent resource, and that dependent has no changes, the plan is changed from CreateThenDelete to DeleteThenCreate causing an apply error.
-
James Bardin authored
A provider cannot influence CreateThenDelete vs DeleteThenCreate, so we shouldn't attribute this to the provider in the error.
-
- 11 Sep, 2020 9 commits
-
-
Petros Kolyvas authored
-
Petros Kolyvas authored
-
Alisdair McDiarmid authored
-
Kirill Zaborsky authored
-
Nick Fagerlund authored
-
Nick Fagerlund authored
The subtle difference in keywords when creating vs. accessing locals trips people up, even more than the "variable" vs. "var" distinction. It deserves its own subheader on the page, plus a nice noisy callout.
-
Lance Kind authored
I've just wasted an hour to two hours trying to find the problem to finally realize that although I declare a "locals" block, it's referred to as "local". This is pretty weird! So let's be be clear about this.
-
Petros Kolyvas authored
-
Petros Kolyvas authored
-
- 10 Sep, 2020 3 commits
-
-
Pam Selle authored
-
Pam Selle authored
Fix bug for force push for backends besides the remote backend
-
Pam Selle authored
In refactoring the force push code when implementing force push for the Terraform remote backend, a bug was introduced that meant that backends that don't implement the EnableForcePush method would still have their state validated. This commit fixes that, and adds test coverage such that there is a separate mockRemoteClient that has this method implemented.
-
- 09 Sep, 2020 3 commits
-
-
James Bardin authored
-
James Bardin authored
Backport 26186
-
James Bardin authored
One of the tenants of the graph transformations is that resource destroy nodes can only be ordered relative to other resources, and can't be referenced directly. This was broken by the module close node which naively connected to all module nodes, creating cycles in some cases when edges are reversed from CreateBeforeDestroy.
-
- 08 Sep, 2020 3 commits
-
-
shaowenchen authored
Signed-off-by:
shaowenchen <mail@chenshaowen.com>
-
Alex Novak authored
`false` section was missing a finishing "`"
-
Matthias Bartelmeß authored
-
- 02 Sep, 2020 4 commits
-
-
hashicorp-ci authored
-
hashicorp-ci authored
-
Kristin Laemmert authored
-
Matt Kasa authored
-
- 01 Sep, 2020 4 commits
-
-
Justin Campbell authored
The GitHub Action passes this in already.
-
Alisdair McDiarmid authored
-
Alisdair McDiarmid authored
command: Better in-house provider install errors
-
Alisdair McDiarmid authored
The error diagnostic shown when legacy state contains resources from in-house providers has changed, so update references to it in the 0.13 upgrade guide.
-