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.
- 19 Nov, 2018 4 commits
-
-
Martin Atkins authored
This test was initially failing because its fixture had a state which our new state models consider to be "empty", and thus it was not migrated. After fixing that (by adding an output to the fixture), this revealed a bug that the lineage was not being persisted through the migration. This is fixed by using the statemgr.Migrate method instead of writing via the normal Writer interface, which allows two cooperating state managers to properly transfer the lineage and serial along with the state snapshot.
-
Martin Atkins authored
-
Martin Atkins authored
In our recent refactoring of the state manager interfaces we made serial and lineage management the responsibility of the state managers themselves, not exposing them at all to most callers, and allowing for simple state managers that don't implement them at all. However, we do have some specific cases where we need to preserve these properly when available, such as migration between backends, and the "terraform state push" and "terraform state pull" commands. These new functions and their associated optional interface allow the logic here to be captured in one place and access via some simple calls. Separating this from the main interface leaves things simple for the normal uses of state managers. Since these functions are mostly just thin wrappers around other functionality, they are not yet well-tested directly, but will be indirectly tested through the tests of their callers. A subsequent commit will add more unit tests here.
-
Martin Atkins authored
This test was incorrectly updated in a previous iteration, with it creating a modified state to write but then not actually writing it, writing an empty test state instead. This made the test fail because a backup state file is created only if the new state snapshot is different to the old when written.
-
- 17 Nov, 2018 1 commit
-
-
Radek Simko authored
tfdiags: Detect more complex cfgs in ElaborateFromConfigBody
-
- 16 Nov, 2018 15 commits
-
-
James Bardin authored
-
James Bardin authored
When applying a legacy diff, recount the flatmapped containers. We can't trust helper/schema to return the correct value, if it even exists.
-
James Bardin authored
-
James Bardin authored
in some cases helper/schema misses the list counts.
-
James Bardin authored
New Attribute and Diff handling in shims
-
James Bardin authored
-
James Bardin authored
Terraform used to provide empty diffs to the provider when calculating `ignore_changes`, which would cause some DiffSuppressFunc to fail, as can be seen in #18209. Verify that this is no longer the case in 0.12
-
James Bardin authored
In order to prevent mismatched states between read/plan/apply, we need to ensure that the attributes are generated consistently each time. Because of the various ways in which helper/schema and the hcl2 shims interpret empty values, the only way to ensure consistency is to always remove them altogether.
-
James Bardin authored
-
James Bardin authored
This makes sure the diff is generated with the matching set ids from helper/schema. Update the tests to add ID fields to the state, which will exists in practice, since any state traversing through the shims will have the ID inserted.
-
James Bardin authored
-
James Bardin authored
This attempts to apply the diff in order to get consistent output from the shimmed values.
-
James Bardin authored
-
James Bardin authored
This was the resource can rebuild the flatmapped state using the schema and ResourceData, providing us the the correct set key values.
-
James Bardin authored
-
- 15 Nov, 2018 8 commits
-
-
Sander van Harmelen authored
Make the Atlas backend work after updating depencies
-
Sander van Harmelen authored
Newer versions of the retryablehttp package use a context, so we need to add that in our custom `CheckRetry` function. In addition I removed the `return true, nil` to continue retrying in case of an error, and instead directly call the `DefaultRetryPolicy`. This is because the `DefaultRetryPolicy` will now also take the context into consideration.
-
Sander van Harmelen authored
Fix wildcard dependencies when upgrading states
-
Radek Simko authored
-
Radek Simko authored
-
Radek Simko authored
-
Radek Simko authored
-
Sander van Harmelen authored
Fixes #19347
-
- 13 Nov, 2018 9 commits
-
-
James Bardin authored
-
James Bardin authored
-
James Bardin authored
The flatmap shim was lazily adding duplicate items and letting cty.Set clear them out, but if those duplicates contains unknown values they can't be checked for equality and will end up remaining in the set.
-
James Bardin authored
-
James Bardin authored
Resources with certain combinations of attributes in a nested single set fail to perperly coerce their shimmed values.
-
Paddy authored
return state in tests even if cfg is invalid
-
Sander van Harmelen authored
depencies: update `go-tfe`
-
Sander van Harmelen authored
-
Dana Hoffman authored
-
- 12 Nov, 2018 3 commits
-
-
Martin Atkins authored
Some other test is leaving behind a terraform.tfstate after it concludes, which can cause this test to fail in a strange way due to picking up extra provider requirements from that state. This check doesn't fix that problem, but it at least makes the test fail in a more helpful way to avoid time wasted trying to debug this test when it's some other test that actually has the bug.
-
Martin Atkins authored
This test is currently failing due to the command completing successfully, which would previously cause a panic because we didn't properly initialize the MockUi and so its error buffer is nil unless written to. (The failure this was masking will be fixed in a subsequent commit.)
-
Martin Atkins authored
In prior refactoring we lost the required core version check from "terraform init", which we restore here. Additionally, this test used to have an incorrect name that suggested it was testing something in the "getProvider" codepath, but version checking happens regardless of what other options are selected.
-