34957 Commits (c7bc22ed7948ff41548b08612b37b6bafb1317e8)

 

All Branches   

Search

Author	SHA1	Message	Date
Daniel Schmidt	c7bc22ed79	only unmark deep once for ValidateDeep	3 months ago
Daniel Schmidt	76747e174c	use format.CtyPath for formatting go-cty paths	3 months ago
Daniel Schmidt	7b28c88e66	improve wording of deprecation marks	3 months ago
Daniel Schmidt	3bafac0d56	we can't savely detect deprecations within provisioners during plan	3 months ago
Daniel Schmidt	7eaf6daf60	add deprecation marks to resources based on schema	3 months ago
Sarah French	02a4ddce1b	fix: Fail an `apply` command if the plan file was generated for a workspace that isn't the selected workspace (#37955) ... * fix: Fail apply command if the plan file was generated for a workspace that isn't the selected workspace. * Add change file * test: Update test helper to include Workspace name in plan representation * fix: Make error message more generic, so is applicable to backend and cloud blocks. * fix: Make error message specific to backend or cloud block * test: Add separate tests for backend/cloud usage * test: Update remaining tests to include a value for Workspace in mocked plans * Apply suggestions from code review Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com> * fix: Panic when a plan file has missing workspace data * test: Update test to match changes in error text --------- Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com>	3 months ago
Daniel Schmidt	379fa79c3e	ElaborateFromConfigBody handles deeply nested paths more precisely	3 months ago
Daniel Schmidt	5723a7a26b	refactor into switch statement	3 months ago
Daniel Schmidt	b09ef138fc	use validate for primitive types	3 months ago
Daniel Schmidt	e6d969a2eb	we only want to send diagnostics for deeply nested deprecations in certain locations ... Mainly terminal locations for the value where they are used, such as the config of a resource, for_each, outputs. We don't want to evaluate the deprecation deeply when it comes to values where the value is not yet used, e.g. locals This is because if e.g. a deeply nested value is deprecated it should still be ok for the entire object to be in a local whereas the same object should give a warning in e.g. an output	3 months ago
Daniel Schmidt	2f392d904e	deprecation.Validate should only check top-level marks	3 months ago
Daniel Schmidt	75445e1ef8	use a string as deprecation origin to help with indirect references ... We want to be able to give better information if e.g. the entire module is stored in a local and the deprecated value is only later used. Where the diag is emitted we might only see the local and not the true origin of the deprecation A string identifying the source of the deprecation should help	3 months ago
Daniel Schmidt	c9cc64a260	move stray check for deprecation to central location	3 months ago
Daniel Schmidt	844bcd8e2c	contextualFromConfigBody should also apply for overridden diagnostics	3 months ago
Daniel Schmidt	a96df66a9a	display origin of deprecated value in diagnostic	3 months ago
Daniel Schmidt	3a36e7732b	refactor: extract write snippet in diagnostic rendering	3 months ago
Daniel Schmidt	ea7f1e3043	add extra origin information for deprecation diagnostics	3 months ago
Daniel Schmidt	c02223e94c	use value without deprecations after validating	3 months ago
Daniel Schmidt	5ee1bece21	detect deprecation marks in more places	3 months ago
Daniel Schmidt	0a9bfcc8d0	move test case to more appropriate PR ... https://github.com/hashicorp/terraform/pull/38006 is dealing with resource deprecation	3 months ago
Daniel Schmidt	5b40f274b2	use EvalContext.Path to get module path for deprecation surpression ... I decided against it before since a lot of tests were panicing, but after consulting with peers I found out the tests were just minimally set up and before it was just fine without the current scope being set. Now we require it to be set as it would in a normal execution therefore I had to add a bit of setup to the tests	3 months ago
Daniel Schmidt	958a1ae1e7	variable and output deprecation ... Variables can be deprecated through the `deprecated` attribute. If set the variable will emit a diagnostic if a values is passed to it. This entails both root level and module variables. Outputs can be deprecated through the `deprecated` attribute as well. If set wherever the value is used a diagnostic will be emitted. Root level outputs can not be deprecated. The only acceptable usage of a deprecated output is another deprecated output (forwarding the deprecation to the module user). If modules not under your control have deprecation warnings you can add a `suppress_deprecations_warnigns` attribute to the module call in question to silence any deeply nested warnings.	3 months ago
Daniel Schmidt	13247d19e2	add deprecation singleton ... This struct tracks and validates deprecations in the context of a graph walk. We need a struct to keep track of the module calls that opt-out of deprecation warnings.	3 months ago
Kristin Laemmert	7e37e518c4	actions test refactor	3 months ago
Radek Simko	41102accc6	command: Fix copy-paste error in error message (#38116)	3 months ago
Radek Simko	1fde2537c2	command/init: Avoid ignoring errors when setting PSS configs (#38115)	3 months ago
Sarah French	2465e326a2	refactor: Use existing methods to detect if a provider is built in (#38118)	3 months ago
Daniel Schmidt	93a38f893b	remove deprecation origin for now ... we will add sth like this again when we will be able display a nicer diagnostic with the origin	3 months ago
Daniel Schmidt	d813ad14f7	add deprecation marks	3 months ago
dependabot[bot]	8a615f93e9	build(deps): bump the github-actions-backward-compatible group with 3 updates (#38113)	3 months ago
Daniel Schmidt	c3cc222a1f	separate tests between different modes	3 months ago
Daniel Schmidt	7307d92619	ignore sorting of diagnostics ... The events are non-deterministic	3 months ago
Daniel Schmidt	fa14a97346	stacks: ensure an empty plan sends an applied status for the component	3 months ago
Daniel Schmidt	ed79a4745b	stacks: add apply time progress message test case	3 months ago
Daniel Schmidt	c24699eab7	stacks: ensure an empty plan produces a planned status	3 months ago
Daniel Schmidt	dce80d4465	stacks: add tests to validate progress events for destroy plans	3 months ago
Daniel Schmidt	70bed8017b	add error-case pre and post diff hook	3 months ago
Daniel Schmidt	4b34066cf2	add error to Pre and PostDiff hook ... We need this information for stacks to forward the error to the progress stream as stacks expects everything that reports itself starting to e.g. plan to also finish either in an error or with success.	3 months ago
Daniel Schmidt	f4c22be3c5	stacks: send progress events on failed provider configurations	3 months ago
Sarah French	8e59c3296a	PSS: Address edge case in `workspace list` when no state files/workspace artefacts exist (#38094) ... * test: Add test demonstrating how the `workspace list` command behaves when no workspaces are reported from a pluggable state store. This scenario isn't possible when using backends. See the code comment for the test for more information. * feat: Make Terraform warn when no workspaces exist, including guidance to users for how to create the workspace. This change is not a breaking change because all backends report that the "default" workspace always exists. This new warning can only be viewed in specific circumstances by users of pluggable state storage.	3 months ago
Radek Simko	64d8933bb8	github/equivalence-test: Ensure inputs are escaped (#38096) ... * github/equivalence-test: Ensure inputs are escaped Co-authored-by: jeevaratnamputla <132266626+jeevaratnamputla@users.noreply.github.com> * Make GH_TOKEN passing more explicit and limited --------- Co-authored-by: jeevaratnamputla <132266626+jeevaratnamputla@users.noreply.github.com>	3 months ago
Sarah French	ac3e32b62b	test: Add test asserting deprecation warnings are present when legacy `env` subcommands are used (#38091)	3 months ago
Daniel Schmidt	492d342aab	ensure actions dont break the graph in modules with no instances	3 months ago
Daniel Schmidt	ece56bda45	add missing assertion	3 months ago
Samsondeen	0b35407d2c	Allow functions in test mock blocks (#37883)	3 months ago
Jared Baker	35e81db902	Merge pull request #38047 from hashicorp/s3/aws-sdk-go-base-upgrade ... backend/s3: bump `github.com/hashicorp/aws-sdk-go-base/v2`	3 months ago
Sarah French	fa620ad0e9	test: Add and update some `init` command tests, linting and code comment changes (#38056)	3 months ago
Sarah French	44e5f86375	PSS: Allow use of pluggable state stores with `-backend=false` during `init` commands (#38066)	3 months ago
Daniel Schmidt	b926263c03	stacks: follow component progress cycle for empty destroys ... We expect a component instances to report its plan/apply starting and ending as well as reporting the progress / result. This should also be the case for no-ops like an empty component instance.	3 months ago
Sarah French	1a36d365c7	Delete automation to detect backported dependency changes (#38065)	3 months ago