27136 Commits (c60dd7c783aea2f9c17d2959dda2f6af12e64872)

 

All Branches   

Search

Author	SHA1	Message	Date
nisunisu	911d09d877	Fixed a typo	6 years ago
Rémi Lapeyre	42be5854a2	Properly quote schema_name in the pg backend configuration	6 years ago
Pam Selle	69b03ebf42	Merge pull request #26379 from hashicorp/pselle/sensitive-nested-block-support ... Support sensitivity within nested blocks	6 years ago
Martin Atkins	593cf7b4d5	didyoumean: move from "helper" to "internal" ... This new-ish package ended up under "helper" during the 0.12 cycle for want of some other place to put it, but in retrospect that was an odd choice because the "helper/" tree is otherwise a bunch of legacy code from when the SDK lived in this repository. Here we move it over into the "internal" directory just to distance it from the guidance of not using "helper/" packages in new projects; didyoumean is a package we actively use as part of error message hints.	6 years ago
Pam Selle	111aadd0f0	Extend tests further	6 years ago
Pam Selle	55c96da27e	Move nested block printing to own method for readability	6 years ago
Nick Fagerlund	26f786959b	website: Update all Learn crosslinks (#26442) ... * website: Update all Learn crosslinks The URL structure on Learn recently changed, so it's time to update some URLs. Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	6 years ago
James Bardin	32681190ca	Merge pull request #26458 from hashicorp/jbardin/data-ref-index ... data sources with indexed references to managed resources	6 years ago
Pam Selle	2ec95f1abc	Make an after val unknown to exercise the known check	6 years ago
Pam Selle	f35b530837	Update compatibility checks for blocks to not use marks ... Remove marks for object compatibility tests to allow apply to continue. Adds a block to the test provider to use in testing, and extends the sensitivity apply test to include a block	6 years ago
Pam Selle	73b1d8b0d1	Add special diff for nested blocks ... When a value in a nested block is marked as sensitive, it will result in the behavior of every member of that block being sensitive. As such, show a specialized diff that reduces noise of (sensitive) for many attributes that we won't show. Also update the warning to differentiate between showing a warning for an attribute or warning for blocks.	6 years ago
Pam Selle	6617c2729c	Test additions for nested blocks ... Add some coverage for in-place on nested block Add nested block to deletion test	6 years ago
Pam Selle	3e7be13dff	Update ordering for marking/unmarking and asserting plan valid ... Update when we unmark objects so we can assert the plan is valid, and process UnknownAsNull on the unmarked value	6 years ago
Pam Selle	26f77564d7	Merge pull request #26459 from hashicorp/pselle/sensitive-vals-map ... Add format/diff coverage for maps with sensitivity	6 years ago
James Bardin	95197f0324	use EvalSelfBlock for destroy provisioners ... Evaluate destroy provisioner configurations using only the last resource state value, and the static instance key data.	6 years ago
James Bardin	804449eda1	Merge pull request #26461 from hashicorp/jbardin/refresh-false ... always load instance state when -refresh=false	6 years ago
Martin Atkins	6b5ca49578	helper: remove a bunch of unused packages, types and functions ... With the SDK moving out into its own repository, a lot of the packages under "helper/" are no longer needed. We still need to keep around just enough legacy SDK to support the "test" provider and some little bits and bobs in the backends and provisioners, but a lot of this is now just dead code. One of the test provider tests was depending on some validation functions only because the schema in there was originally copied from a "real" provider. The validation rules are not actually important for the test, so I removed them. Otherwise, this removes only dead code.	6 years ago
James Bardin	64c3a8f550	lang.Scope.EvalSelfBlock ... In order to properly evaluate a destroy provisioner, we cannot rely on the usual evaluation context, because the resource has already been removed from the state. EvalSelfBlock evaluates an hcl.Body in the limited scope of a single object as "self", with the added values of "count.index" and "each.key".	6 years ago
Pam Selle	1817c8ac3c	Merge pull request #26412 from OwenTuz/issue-26411-fix-failing-e2e-test-provider-not-found ... Fix bad string match that was causing TestInitProviderNotFound to fail	6 years ago
Pam Selle	5286a1bfb7	Merge pull request #26466 from jerrychong25/patch-2 ... Modified terraform force-unlock command	6 years ago
James Bardin	43c0525277	fix the test that was supposed to break ... The test for this behavior did not work, because the old mock diff function does not work correctly. Write a PlanResourceChange function to return a correct plan.	6 years ago
Jerry Chong	90cbc5a123	Modified terraform force-unlock command ... -Added code block for terraform force-unlock LOCK_ID	6 years ago
kt	b66364f7aa	AzureRM backend: correctly lookup environment from metadata host	6 years ago
James Bardin	07af1c6225	destroy time eval of resources pending deletion ... Allow the evaluation of resource pending deleting only during a full destroy. With this change we can ensure deposed instances are not evaluated under normal circumstances, but can be references when needed. This also allows us to remove the fixup transformer that added connections so temporary values would evaluate in the correct order when referencing destroy nodes. In the majority of cases, we do not want to evaluate resources that are pending deletion since configuration references only can refer to resources that is intended to be managed by the configuration. An exception to that rule is when Terraform is performing a full `destroy` operation, and providers need to evaluate existing resources for their configuration.	6 years ago
James Bardin	fa8f8df7b6	add ChangesSync.FullDestroy ... In order to handle various edge cases during a full destroy, add FullDestroy to the synchronized changes so we can attempt to deduce if the plan was created from `terraform destroy`. It's possible that the plan was created by removing all resourced from the configuration, but in that case the end result is the same. Any of the edge cases with provider or destroy provisioner configurations would not apply, since there would not be any configuration references to resolve.	6 years ago
James Bardin	ac526d8d5d	always load instance state when -refresh=false ... The loading of the initial instance state was inadvertently skipped when -refresh=false, causing all resources to appear to be missing from the state during plan.	6 years ago
Pam Selle	52b6f7f53e	Move common IsMarked checks above switch statement	6 years ago
Pam Selle	1780351636	If the whole map is marked, have the same sensitivity behavior as a single value	6 years ago
Pam Selle	0520f143a2	Add diff coverage for maps ... Considers wholly marked maps as well as map keys	6 years ago
James Bardin	78322d5843	data depends_on with indexed references ... If a data source refers to a indexed managed resource, we need to re-target that reference to the containing resource for planning. Since data sources use the same mechanism as depends_on for managed resource references, they can only refer to resources as a whole.	6 years ago
Pam Selle	a7e43dfd46	Merge pull request #26431 from hashicorp/pselle/sensitive-vals-docs ... docs: Docs for sensitive variables	6 years ago
Pam Selle	3ddbb4b009	Update provider caveat grammar	6 years ago
Pam Selle	93d38ff2d2	Update intro to code blocks	6 years ago
Pam Selle	be50089c7f	Rephrase sensitive index description	6 years ago
Pam Selle	09551de078	Rewrite intro to section, rename section, move state info ... Move the information about state from the "caveats" to the main info section, using similar information to sensitive outputs. Updates the header of the section from similar inspiration.	6 years ago
Pam Selle	5cf61448e7	Update website/docs/configuration/variables.html.md ... Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	6 years ago
Pam Selle	9c2556b5ad	Add sensitive variables to changelog	6 years ago
Pam Selle	e0e6f4fd13	Merge pull request #26443 from hashicorp/pselle/sensitive-var-module-merge ... Implement module merge for sensitive variable config	6 years ago
Pam Selle	d57cb50fa9	Merge pull request #26437 from hashicorp/pselle/sensitive-var-type-check ... Add test file for bad sensitive value	6 years ago
James Bardin	2376b3c5ee	Merge pull request #26444 from hashicorp/jbardin/value-checks ... Add some log warnings and remove dead code	6 years ago
James Bardin	82793f8158	update ignore_changes doc ... We can remove the caveat about changing map elements. Add a little more text about the intended use case for ignore_changes, as the common case of fixing erroneous provider behavior should not be the primary motivation for the maintenance of this feature.	6 years ago
James Bardin	ad0b81de81	allow ignore_changes to reference any map key ... There are situations when a user may want to keep or exclude a map key using `ignore_changes` which may not be listed directly in the configuration. This didn't work previously because the transformation always started off with the configuration, and would never encounter a key if it was only present in the prior value.	6 years ago
Kristin Laemmert	90588c036b	terraform: minor cleanup from EvalTree() refactor (#26429) ... * Split node_resource_abstract.go into two files, putting NodeAbstractResourceInstance methods in their own file - it was getting large enough to be tricky for (my) human eyeballs. * un-exported the functions that were created as part of the EvalTree() refactor; they did not need to be public.	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
James Bardin	98b568ad01	remove unused refresh node ... There is no longer a refresh walk, so we no longer use this type.	6 years ago
Pam Selle	2a35240a17	Merge pull request #26314 from hashicorp/remove-template-provider-link ... docs: remove link to deprecated provider	6 years ago
Pam Selle	ef95cf482b	Update CHANGELOG.md ... Add pg backend PR	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
James Bardin	c52672cbbe	log inconsistencies during refresh ... We can't make these errors because there's no way to exempt legacy providers from the check, but we can at least log them for troubleshooting.	6 years ago
Pam Selle	f2fe0ceb0a	Implement module merge for sensitive config ... Implements merging behavior for when sensitive is set on a variable and adds testing accordingly	6 years ago