662 Commits (fc8a76a2a3a2ce0d318cdb2e6f3f76ebbc6b28ac)

Author	SHA1	Message	Date
Paul Thrasher	fc8a76a2a3	Stop printing tfce error message log	6 years ago
Kristin Laemmert	b8e3b8036a	backend: remove deprecated atlas backend	6 years ago
Paul Thrasher	960042ad42	Merge pull request #26618 from hashicorp/pault/tfce-continue-on-error ... Allow runs to continue on tfce error	6 years ago
James Bardin	0b31ffa587	use a single log writer ... Use a single log writer instance for all std library logging. Setup the std log writer in the logging package, and remove boilerplate from test packages.	6 years ago
James Bardin	6ca477f042	move helper/logging to internal ... remove a dead code file too	6 years ago
Paul Thrasher	d380f5873c	Allow runs to continue on tfce error ... A cost estimation error does not actually stop a run, so the run was continuing in the background after the cli exits, causing confusion. This change matches the UI behavior.	6 years ago
James Bardin	5e9425b562	unreachable	6 years ago
James Bardin	b8df47c9ac	add struct field names	6 years ago
James Bardin	657dd33008	Merge pull request #26557 from remilapeyre/skip-ddl-commands ... Add skip_table_creation and skip_index_creation options to the pg backend	6 years ago
James Bardin	5eca0788c6	rely solely on the plan changes for outputs ... Now that outputs changes are tracked in full, we can remove the comparisons with the prior state and use the planned changes directly.	6 years ago
Rémi Lapeyre	12a0a21c0b	Add skip_table_creation and skip_index_creation options to the pg backend ... Closes https://github.com/hashicorp/terraform/issues/25708	6 years ago
James Bardin	57a47d0b82	Merge pull request #26519 from hashicorp/jbardin/FIXME ... Cleanup and remove legacy types from test mocks	6 years ago
James Bardin	103a6cf2db	update mock provider call	6 years ago
Kristin Laemmert	6f4f6fbc72	helper: deprecate pathorcontents ... pathorcontents was solely used by the gcs backend. I moved the function into the backend package so it could still be used by other backends for good measure.	6 years ago
Kristin Laemmert	d2e999ba1f	remove unused code (#26503) ... * remove unused code I've removed the provider-specific code under registry, and unused nil backend, and replaced a call to helper from backend/oss (the other callers of that func are provisioners scheduled to be deprecated). I also removed the Dockerfile, as our build process uses a different file. Finally I removed the examples directory, which had outdated examples and links. There are better, actively maintained examples available. * command: remove various unused bits * test wasn't running * backend: remove unused err	6 years ago
James Bardin	826ccdd123	re-enable test	6 years ago
Pam Selle	f84a7c1d57	Merge pull request #26476 from remilapeyre/postgres-backend-escape-schema_name ... Properly quote schema_name in the pg backend configuration	6 years ago
James Bardin	70652814e3	add missing Context argument	6 years ago
James Bardin	5e13d57f4e	Merge pull request #26463 from hashicorp/kt/azurerm-secret-backend-fix ... AzureRM backend: correctly lookup environment from metadata host	6 years ago
Alisdair McDiarmid	35d4926bf7	Merge pull request #25837 from remilapeyre/consul-force-unlock ... Fix `terraform force-unlock <lock_id>` for Consul backend	6 years ago
Kristin Laemmert	3933cbd491	remove LegacyProvider (#26433)	6 years ago
Rémi Lapeyre	42be5854a2	Properly quote schema_name in the pg backend configuration	6 years ago
kt	b66364f7aa	AzureRM backend: correctly lookup environment from metadata host	6 years ago
Kristin Laemmert	d76cfc8c0c	Merge pull request #26440 from hashicorp/mildwonkey/remove-older-state-vs ... refactor tests to use modern states.State in favor of terraform.State where possible	6 years ago
Pam Selle	3a99405b8b	Merge pull request #26420 from remilapeyre/postgres-default-backend ... Always have the default workspace in the pg backend	6 years ago
Kristin Laemmert	479655ad47	refactor tests to use modern states.State in favor of terraform.State where possible	6 years ago
James Bardin	ab6d6f99ae	fix races in remote backend mock	6 years ago
Rémi Lapeyre	9acfe30ca6	Always have the default workspace in the pg backend ... Closes https://github.com/hashicorp/terraform/issues/23121	6 years ago
Rémi Lapeyre	5c7008bd89	Merge remote-tracking branch 'origin/master' into consul-force-unlock	6 years ago
James Bardin	37569f5cc3	insert PlanRefresh into the context	6 years ago
James Bardin	bc82347a04	fix tests ... Update tests to match the new behavior. Some were incorrect, some no longer make sense, and some just weren't setup to handle th plan api calls.	6 years ago
James Bardin	312317abd0	wrong instance key in test state ... This was never picked up by the tests until now	6 years ago
James Bardin	8658424059	skip plan with no refresh test ... We still need to determine if `-refresh=false` is even useful with the new planning strategy.	6 years ago
James Bardin	f52d836e0a	fix local backend tests to match new behavior ... Leaving plan with -refresh=false tests failing for now.	6 years ago
James Bardin	be757bd416	Refresh instances during plan ... This change refreshes the instance state during plan, so a complete Refresh no longer needs to happen before Plan.	6 years ago
Alisdair McDiarmid	e183163739	Merge pull request #25856 from remilapeyre/consul-split-state ... Split the state in chunks when they outgrow the limit of Consul KV store	6 years ago
Alisdair McDiarmid	92abaadc02	Merge pull request #25842 from remilapeyre/consul-path-slash ... Sanitize lock path for the Consul backend when it ends with a /	6 years ago
Alisdair McDiarmid	09d8355f43	command: Add experimental concise diff renderer ... When rendering a diff between current state and projected state, we only show resources and outputs which have changes. However, we show a full structural diff for these values, which includes all attributes and blocks for a changed resource or output. The result can be a very long diff, which makes it difficult to verify what the changed fields are. This commit adds an experimental concise diff renderer, which suppresses most unchanged fields, only displaying the most relevant changes and some identifying context. This means: - Always show all identifying attributes, initially defined as `id`, `name`, and `tags`, even if unchanged; - Only show changed, added, or removed primitive values: `string`, `number`, or `bool`; - Only show added or removed elements in unordered collections and structural types: `map`, `set`, and `object`; - Show added or removed elements with any surrounding unchanged elements for sequence types: `list` and `tuple`; - Only show added or removed nested blocks, or blocks with changed attributes. If any attributes, collection elements, or blocks are hidden, a count is kept and displayed at the end of the parent scope. This ensures that it is clear that the diff is only displaying a subset of the resource. The experiment is currently enabled by default, but can be disabled by setting the TF_X_CONCISE_DIFF environment variable to 0.	6 years ago
Kirill Zaborsky	fbd3f191bd	Minor typo	6 years ago
Matt Kasa	c2e35ae3b5	backend/http: add support for configuration by environment variable (#25439)	6 years ago
Kristin Laemmert	196c183dda	terraform: remove state from `validate` graph walk (#26063) ... This pull reverts a recent change to backend/local which created two context, one with and one without state. Instead I have removed the state entirely from the validate graph (by explicitly passing a states.NewState() to the validate graph builder). This changed caused a test failure, which (ty so much for the help) @jbardin discovered was inaccurate all along: the test's call to `Validate()` was actually what was removing the output from state. The new expected test output matches terraform's actual behavior on the command line: if you use -target to destroy a resource, an output that references only that resource is *not* removed from state even though that test would lead you to believe it did. This includes two tests to cover the expected behavior: TestPlan_varsUnset has been updated so it will panic if it gets more than one request to input a variable TestPlan_providerArgumentUnset covers #26035 Fixes #26035, #26027	6 years ago
James Bardin	0c5430f88d	Merge pull request #25585 from chushenmeshile/master ... fix ossbackend only returned 100 workspaces	6 years ago
James Bardin	bd5ff98ca7	Merge pull request #25830 from hashicorp/kt/secret-metadata-host ... backend/azurerm: support loading environments from a metadata host	6 years ago
James Bardin	d46e9a4198	Merge pull request #25770 from hashicorp/f/azure-backend-spcert ... backend/azurerm: support for authenticating using a Client Certificate	6 years ago
Angie Pinilla	582fb73a7c	deps: Update aws-sdk-go-based to 0.6.0	6 years ago
Rémi Lapeyre	e680211bc0	Split the state in chunks when they outgrow the limit of Consul KV store ... The Consul KV store limits the size of the values in the KV store to 524288 bytes. Once the state reaches this limit Consul will refuse to save it. It is currently possible to try to bypass this limitation by enable Gzip but the issue will manifest itself later. This is particularly inconvenient as it is possible for the state to reach this limit without changing the Terraform configuration as datasources or computed attributes can suddenly return more data than they used to. Several users already had issues with this. To fix the problem once and for all we now split the payload in chunks of 524288 bytes when they are to large and store them separatly in the KV store. A small JSON payload that references all the chunks so we can retrieve them later and concatenate them to reconstruct the payload. While this has the caveat of requiring multiple calls to Consul that cannot be done as a single transaction as those have the same size limit, we use unique paths for the chunks and CAS when setting the last payload so possible issues during calls to Put() should not result in unreadable states. Closes https://github.com/hashicorp/terraform/issues/19182	6 years ago
Rémi Lapeyre	032d339915	Sanitize lock path for the Consul backend when it ends with a / ... When the path ends with / (e.g. `path = "tfstate/"), the lock path used will contain two consecutive slashes (e.g. `tfstate//.lock`) which Consul does not accept. This change the lock path so it is sanitized to `tfstate/.lock`. If the user has two different Terraform project, one with `path = "tfstate"` and the other with `path = "tfstate/"`, the paths for the locks will be the same which will be confusing as locking one project will lock both. I wish it were possible to forbid ending slashes altogether but doing so would require all users currently having an ending slash in the path to manually move their Terraform state and would be a poor user experience. Closes https://github.com/hashicorp/terraform/issues/15747	6 years ago
Rémi Lapeyre	11eb88753d	Fix `terraform force-unlock <lock_id>` for Consul backend ... When locking was enabled with the Consul backend and the lock not properly released, the `terraform force-unlock <lock_id>` command would do nothing as its implementation would exit early in that case. It now destroys the session that created the lock and clean both the lock and the lock-info keys. A regression test is added to TestConsul_destroyLock() to catch the issue if it happends again. Closes https://github.com/hashicorp/terraform/issues/22174	6 years ago
kt	23b4c2db42	azurerm backend: support loading metadata from a given host	6 years ago
James Bardin	1c09df1a66	Merge pull request #25779 from hashicorp/jbardin/remove-state-attrs ... Remove resource state attributes that are no longer in the schema	6 years ago