terraform

Commit Graph

Author	SHA1	Message	Date
Radek Simko	0fe906fa8c	make copyrightfix	5 days ago
Samsondeen	719aefdb89	tf query: ready list blocks for beta (#37619 )	5 months ago
Kristin Laemmert	df113486a1	actions: remove references to action types, linked resources (#37616 ) * action renaming * actions: remove references to action types * actions: remove references to linked_resources or action types from the plan proto	5 months ago
Daniel Schmidt	871451122f	actions: move schema to single action type and remove linked resources we want to leave the door open to evolve the design in the future based on feedback	5 months ago
Liam Cervante	ffdf9f2a86	actions: preserve unknown metadata in the json plan (#37611 ) * actions: preserve unknown metadata in the json plan * copywrite headers	5 months ago
Daniel Schmidt	85717fba7e	actions: add number of invoked actions to plan summary	6 months ago
Liam Cervante	673717d01a	actions: render invoked actions (#37540 ) * actions: add invoke graph nodes * fix small bugs * add additional tests * remove whitespace * actions: invoke rendered actions * also fix up apply message * make description headers consistent * fix copyright headers * go generate	6 months ago
Liam Cervante	8488fbb35c	Revert "actions: render invoked actions (#37522 )" (#37538 ) This reverts commit `0fae555389`.	6 months ago
Liam Cervante	0fae555389	actions: render invoked actions (#37522 ) * actions: add invoke graph nodes * fix small bugs * add additional tests * remove whitespace * actions: invoke rendered actions * also fix up apply message * make description headers consistent * fix copyright headers * go generate	6 months ago
Daniel Schmidt	8b65426ecf	move action schemas out of experimental flag	6 months ago
Daniel Banck	2463f864dd	Exclude nested config block from list resource schemas (#37495 ) * Exclude nested config block from list resource schemas * Guard action schemas by experimental flag * Fix tests	6 months ago
Daniel Schmidt	219c31f4eb	action: move action trigger into nested struct this prepares the work on CLI / flag-driven invocations	6 months ago
Daniel Schmidt	4fb4c3f056	render action config values	7 months ago
Daniel Banck	ab04e5cfec	Include list resource schemas in provider json schemas (TF-25497) (#37163 ) * Include list schemas in provider json schemas * Only include list schemas in experimental builds	8 months ago
Daniel Schmidt	fec6e4b552	send resource identities to provider calls	12 months ago
Daniel Banck	10c9b64007	Rename schema.Block to Body (#36629 )	12 months ago
Radek Simko	289a3568da	Address `go vet` 1.24 failures (#36485 ) * address go vet failures * avoid unnecessary .Error()	1 year ago
Daniel Schmidt	276662f754	ephemeral: add test case for block rendering	1 year ago
Daniel Schmidt	0e6a3ac994	ephemeral: render write-only attributes in plan UI	1 year ago
Liam Cervante	332757894d	plan renderer: fix crash when updating a null attribute to unknown (#35709 )	1 year ago
Liam Cervante	abd6b9ef1b	plan renderer: render unknown nested blocks properly (#35644 )	1 year ago
James Bardin	16231373a4	update changes in command pkgs	2 years ago
Daniel Schmidt	3b95a5f6b1	fix formatting Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com>	2 years ago
Daniel Schmidt	8e1f02843d	jsonformat: update tests	2 years ago
Daniel Schmidt	a00e015e24	jsonformat: render different no changes message on deferred actions	2 years ago
Daniel Schmidt	4afb3b2b48	jsonformat: render deferred actions	2 years ago
Martin Atkins	30e2fd6525	Handle marks a little more consistently In the very first implementation of "sensitive values" we were unfortunately not disciplined about separating the idea of "marked value" from the idea of "sensitive value" (where the latter is a subset of the former). The first implementation just assumed that any marking whatsoever meant "sensitive". We later improved that by adding the marks package and the marks.Sensitive value to standardize on the representation of "sensitive value" as being a value marked with _that specific mark_. However, we did not perform a thorough review of all of the mark-handling codepaths to make sure they all agreed on that definition. In particular, the state and plan models were both designed as if they supported arbitrary marks but then in practice marks other than marks.Sensitive would be handled in various inconsistent ways: dropped entirely, or interpreted as if marks.Sensitive, and possibly do so inconsistently when a value is used only in memory vs. round-tripped through a wire/file format. The goal of this commit is to resolve those oddities so that there are now two possible situations: - General mark handling: some codepaths genuinely handle marks generically, by transporting them from input value to output value in a way consistent with how cty itself deals with marks. This is the ideal case because it means we can add new marks in future and assume these codepaths will handle them correctly without any further modifications. - Sensitive-only mark preservation: the codepaths that interact with our wire protocols and file formats typically have only specialized support for sensitive values in particular, and lack support for any other marks. Those codepaths are now subject to a new rule where they must return an error if asked to deal with any other mark, so that if we introduce new marks in future we'll be forced either to define how we'll avoid those markings reaching the file/wire formats or extend the file/wire formats to support the new marks. Some new helper functions in package marks are intended to standardize how we deal with the "sensitive values only" situations, in the hope that this will make it easier to keep things consistent as the codebase evolves in future. In practice the modules runtime only ever uses marks.Sensitive as a mark today, so all of these checks are effectively covering "should never happen" cases. The only other mark Terraform uses is an implementation detail of "terraform console" and does not interact with any of the codepaths that only support sensitive values in particular.	2 years ago
James Bardin	bdd5a2cd33	try to render some empty string -> null changes Changes between empty strings and `null` were hidden in the CLI output, because the SDK could not reliably detect the difference and may return either value depending on the situation. This legacy behavior can be confusing for authors of new provider which can correctly handle `null`, and it would be preferable to be able to render those changes in the CLI. While we don't have enough information to detect when the legacy behavior is required, we can detect a number of cases where it's certain that we are not dealing with a legacy schema and should output the full diff.	2 years ago
Daniel Schmidt	adf008d489	adjust tests to new implementation	2 years ago
kmoe	8f3aa0e099	jsonformat: render forget-only attr changes as no-op (#34403 ) * jsonplan: document forget actions * jsonformat: format forget changes as no-op Previous to this commit, forget-only actions (i.e. "forget", not "create then forget") would be rendered using the forget action symbol for the top-level resource, and the delete action symbol for each resource attribute, with a new value of "null". This attribute rendering is identical to that for resource deletion, which might suggest to some users that Terraform plans to delete the resource, not just remove it from state. This commit tweaks the renderer so forget-only changes render as no-ops but with the forget action symbol and resource change comment.	2 years ago
kmoe	a718f70f85	Add removed block (#34251 ) * terraform: remove redundant code NodeDestroyResourceInstance is never instantiated with a DeposedKey of anything other than states.NotDeposed, so the deleted code is never run. Deposed objects get a NodeDestroyDeposedResourceInstanceObject instead. * tfdiags: add helper func * configs: introduce removed block type * terraform: add forget action * renderer: render forget actions * terraform: deposed objects can be forgotten Deposed objects encountered during planning spawn NodePlanDeposedResourceInstanceObject, which previously generated a destroy change. Now it will generate a forget change if the deposed object is a forget target, and a destroy change otherwise. The apply graph gains a new node type, NodeForgetDeposedResourceInstanceObject, whose execution simply removes the object from the state. * configs: add RemoveTarget address type * terraform: modules can be forgotten * terraform: error if removed obj still in config * tests: better error on restore state fail * Update CHANGELOG.md	2 years ago
hashicorp-copywrite[bot]	53c34ff49c	Update copyright file headers to BUSL-1.1	3 years ago
James Bardin	cf5ebaf685	s/Schemas/ProviderSchema/	3 years ago
James Bardin	36d34135ad	replace remaining types in tests	3 years ago
kmoe	b4d1146f58	plannable import: improve gen config human plan output (#33194 ) * renderer: remove hard-coded config gen path * mention config gen file in plan next steps	3 years ago
Liam Cervante	4d837df546	Plannable import: Add generated config to JSON and human-readable plan output (#33154 ) * command: keep our promises * remove some nil config checks Remove some of the safety checks that ensure plan nodes have config attached at the appropriate time. * add GeneratedConfig to plan changes objects Add a new GeneratedConfig field alongside Importing in plan changes. * add config generation package The genconfig package implements HCL config generation from provider state values. Thanks to @mildwonkey whose implementation of terraform add is the basis for this package. * generate config during plan If a resource is being imported and does not already have config, attempt to generate that config during planning. The config is generated from the state as an HCL string, and then parsed back into an hcl.Body to attach to the plan graph node. The generated config string is attached to the change emitted by the plan. * complete config generation prototype, and add tests * Plannable import: Add generated config to json and human-readable plan output --------- Co-authored-by: Katy Moe <katy@katy.moe>	3 years ago
Liam Cervante	77f10c4f68	Imports should come before Adds in change summaries (#33147 )	3 years ago
Liam Cervante	54c1c1162f	[Plannable Import] Implement human-readable plan rendering (#33113 ) * [plannable import] embed the resource id within the changes * add the plannable imports to the json and human plans * latest importing struct	3 years ago
hashicorp-copywrite[bot]	325d18262e	[COMPLIANCE] Add Copyright and License Headers	3 years ago
Liam Cervante	357012a2f3	Refactor of differ to make code reuse easier (#33054 ) * refactor of differ to make code reuse easier * fix imports	3 years ago
Liam Cervante	15ecdb66c8	Fix no-op outputs causing the plan renderer to skip the 'no changes' message (#32820 ) * Fix no-op outputs causing the plan renderer to skip the 'no changes' message * fix imports	3 years ago
Liam Cervante	d818d7850d	Structured Renderer: use the new renderer when rendering the state in addition to the plan (#32629 ) * Use the new renderer when rendering the state * remove confusing and unneeded comment	3 years ago

42 Commits (main)