34928 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
Sarah French	fa37804256	feat: Add -safe-init flag to init command, including validation of use with experiments and mutually-exclusive flags	2026-01-30 17:00:01 +00:00
Daniel Schmidt	c3cc222a1f	separate tests between different modes	2026-01-30 16:13:59 +01:00
Daniel Schmidt	7307d92619	ignore sorting of diagnostics ... The events are non-deterministic	2026-01-30 16:13:59 +01:00
Daniel Schmidt	fa14a97346	stacks: ensure an empty plan sends an applied status for the component	2026-01-30 16:13:59 +01:00
Daniel Schmidt	ed79a4745b	stacks: add apply time progress message test case	2026-01-30 16:13:59 +01:00
Daniel Schmidt	c24699eab7	stacks: ensure an empty plan produces a planned status	2026-01-30 16:13:59 +01:00
Daniel Schmidt	dce80d4465	stacks: add tests to validate progress events for destroy plans	2026-01-30 16:13:59 +01:00
Daniel Schmidt	70bed8017b	add error-case pre and post diff hook	2026-01-30 16:13:59 +01:00
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.	2026-01-30 16:13:59 +01:00
Daniel Schmidt	f4c22be3c5	stacks: send progress events on failed provider configurations	2026-01-30 16:13:59 +01:00
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.	2026-01-28 15:15:04 +00:00
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>	2026-01-26 15:44:53 +00:00
Sarah French	ac3e32b62b	test: Add test asserting deprecation warnings are present when legacy env subcommands are used (#38091)	2026-01-23 15:33:46 +00:00
Daniel Schmidt	492d342aab	ensure actions dont break the graph in modules with no instances	2026-01-23 13:29:47 +01:00
Daniel Schmidt	ece56bda45	add missing assertion	2026-01-23 13:29:47 +01:00
Samsondeen	0b35407d2c	Allow functions in test mock blocks (#37883)	2026-01-22 09:42:21 +01:00
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`	2026-01-20 11:00:44 -05:00
Sarah French	fa620ad0e9	test: Add and update some init command tests, linting and code comment changes (#38056)	2026-01-20 09:14:26 +00:00
Sarah French	44e5f86375	PSS: Allow use of pluggable state stores with -backend=false during init commands (#38066)	2026-01-20 09:12:52 +00:00
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.	2026-01-15 14:23:02 +01:00
Sarah French	1a36d365c7	Delete automation to detect backported dependency changes (#38065)	2026-01-15 11:39:39 +00:00
Sarah French	827f693e32	test: Update TestInit_fromModule_dstInSrc to reflect current behaviour when -from-module references the location of the current directory (#38059) ... * test: Update `TestInit_fromModule_dstInSrc` to use modern `t.Chdir` approach, add context through comments * test: Add context about how `TestInit_fromModule_dstInSrc` has been refactored since it was first created Originally the test's args were []string{".", "foo"} (https://github.com/hashicorp/terraform/pull/547), where the second arg is the directory TF should use as the root directory. Then the test was changed to use []string{"-from-module=.", "foo"} when the -from-module flag was added in 8a7a0a7459. Finally, the second arg was removed in https://github.com/hashicorp/terraform/pull/27664, and replaced with the use of os.Chdir in this test. * test: Update `TestInit_fromModule_dstInSrc` to define the new behavior of -from-module in this scenario; the current directory is copied once, but not recursively. If you run this test from commit 84f5b863ef with a debugger we can see that foo is never copied into the current directory foo (./foo/foo is never made). Now, after refactoring ./foo/foo IS made, but it's not copied recursively like in the original issue. * docs: Add comment about emergent behavior when using -chdir with -from-module in this scenario	2026-01-14 15:57:10 +00:00
Radek Simko	1186262c8c	backend/http: Refresh state earlier (align with other backends) (#38033) ... * correct changelog entry for #38027 * backend/http: Refresh state before returning StateMgr This aligns the http backend with the implementation of StateMgr in other remote backends, which in turn enables easier testing of higher level logic that relies on certain backend behaviours. * backend/http: Refactor TestHTTPBackend to allow custom method implementations * add regression test for PR 38027	2026-01-14 15:13:58 +00:00
Mark Hall	7029dfac86	Fix nil pointer dereference in backend state migration (#38028) ... * fix: handle all StateMgr errors during backend migration Fixes a nil pointer dereference panic that occurs during backend migration when StateMgr returns an error other than ErrDefaultWorkspaceNotSupported. The bug occurred because the code only checked for the specific ErrDefaultWorkspaceNotSupported error. When any other error occurred (such as permission errors like storage.objects.get access denied), destinationState remained nil, but the code continued and attempted to call destinationState.RefreshState(), causing a panic. This fix adds an else clause to catch and return all other errors from StateMgr, preventing the nil pointer dereference and providing users with a clear error message instead of a crash. Fixes #24100 * Add changelog entry for backend migration nil pointer fix 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>	2026-01-14 11:41:23 +00:00
Michael Yocca	810f497ecd	fix(cloud): cloud backend rendering query warning diags (#38040)	2026-01-13 08:48:15 -08:00
Jared Baker	6475423325	backend/s3: bump github.com/hashicorp/aws-sdk-go-base/v2 ... Incrementing the `aws-sdk-go-base` dependecy will also pull in the latest version of the AWS SDK for Go V2, which includes support for the newly launched `aws login` authentication method.	2026-01-08 10:59:37 -05:00
Jared Baker	0b9a20c7c4	Merge pull request #37940 from vietcgi/fix/s3-backend-fips-env-var-parsing ... fix: parse boolean env vars in S3 backend correctly	2026-01-08 09:19:59 -05:00
Jared Baker	dc0384e578	chore: switch changelog to UPGRADE NOTES kind ... This is consistent with the `kind` used for previous breaking changes to S3 backend behavior.	2026-01-07 15:54:50 -05:00
Jared Baker	4f53303c12	Merge branch 'main' into fix/s3-backend-fips-env-var-parsing	2026-01-07 15:50:34 -05:00
dependabot[bot]	59b84c820e	build(deps): bump the github-actions-breaking group with 4 updates (#38035) ... Bumps the github-actions-breaking group with 4 updates: [actions/upload-artifact](https://github.com/actions/upload-artifact), [actions/cache](https://github.com/actions/cache), [actions/download-artifact](https://github.com/actions/download-artifact) and [dessant/lock-threads](https://github.com/dessant/lock-threads). Updates `actions/upload-artifact` from 5.0.0 to 6.0.0 - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](330a01c490...b7c566a772) Updates `actions/cache` from 4.3.0 to 5.0.1 - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](0057852bfa...9255dc7a25) Updates `actions/download-artifact` from 6.0.0 to 7.0.0 - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](018cc2cf5b...37930b1c2a) Updates `dessant/lock-threads` from 5.0.1 to 6.0.0 - [Release notes](https://github.com/dessant/lock-threads/releases) - [Changelog](https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md) - [Commits](1bf7ec2505...7266a7ce5c) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions-breaking - dependency-name: actions/cache dependency-version: 5.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions-breaking - dependency-name: actions/download-artifact dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions-breaking - dependency-name: dessant/lock-threads dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions-breaking ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-01-05 11:05:56 +00:00
Andy Hay	e3263bece0	cleanup: remove stale FIXME in terraform provider (#38031) ... * cleanup: remove stale FIXME in terraform provider Signed-off-by: Andrew Hay <andrew.hay@benchmarkanalytics.com> * chore: add changelog entry Signed-off-by: Andrew Hay <andrew.hay@benchmarkanalytics.com> * chore: fix changelog entry format Signed-off-by: Andrew Hay <andrew.hay@benchmarkanalytics.com> * chore: remove changelog entry (not user facing) Signed-off-by: Andrew Hay <andrew.hay@benchmarkanalytics.com> --------- Signed-off-by: Andrew Hay <andrew.hay@benchmarkanalytics.com>	2026-01-05 11:05:34 +00:00
dependabot[bot]	16032e16e6	build(deps): bump actions/checkout (#38036) ... Bumps the github-actions-backward-compatible group with 1 update: [actions/checkout](https://github.com/actions/checkout). Updates `actions/checkout` from 6.0.0 to 6.0.1 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](1af3b93b68...8e8c483db8) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions-backward-compatible ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2026-01-05 10:52:21 +00:00
Sarah French	193867f060	test: Add E2E test coverage for inspecting a plan file using the terraform show command (#38020)	2025-12-19 14:53:07 +00:00
Tommy O'Keefe	13cccebef0	Merge pull request #38019 from hashicorp/tommy/contribution-guide-ai-updates ... docs: add link for new AI Usage section to CONTRIBUTING.md TOC	2025-12-18 12:04:44 -05:00
tommyokeefe	14181ad0c6	docs: add link for new AI Usage section to CONTRIBUTING.md TOC	2025-12-18 11:53:04 -05:00
Tommy O'Keefe	e27f9467c8	ocs: update CONTRIBUTING.md to include guidance for AI usage	2025-12-18 10:40:19 -05:00
tommyokeefe	ee446e8920	docs: update CONTRIBUTING.md to include guidance for AI usage	2025-12-18 09:09:13 -05:00
Sarah French	fd7f25120b	PSS: Allow pluggable state store configuration to be read from a plan file (#37957) ... * feat: Allow reading state store configuration from a planfile and using it to prepare a Local backend that uses the state store * test: Assert that we can get and use state store configuration from a plan file * test: Add integration test showing that an apply command can use a plan file to configure and use a state store * test: Add E2E test showing pluggable state storage being used with the full init-plan-apply workflow * feat: A plan file will report the state storage provider among its required providers, if PSS is in use. See the code comment added in this commit. This addition does not impact an apply command as the missing provider will be detected before this code is executed. However I'm making this change so that the method is still accurate is being able to return a complete list of providers needed by the plan. * fix: Include error messages when there is a problem parsing provider or state store config when getting a backend from a planfile * feat: Add trace logs to BackendForLocalPlan indicating when the provider is launched and the state store is configured * chore: Small grammar change in error diagnostic * refactor: Remove suggestions when the plan's state store doesn't match the implementations in the provider * test: Add test coverage of what happens when the contents of a plan file using PSS doesn't match the resources available in the project	2025-12-18 11:49:31 +00:00
Kevin Vu	c36c81431a	fix: validate replace_triggered_by attribute references (#38010) ... * fix: use schema-based validation for replace_triggered_by Fixes #36740 * fix: use change.ProviderAddr for schema lookup	2025-12-17 19:50:51 +00:00
Sarah French	f88d09544e	PSS: Add tests showing provider commands being used with PSS (#37959) ... * test: Add E2E test for using pluggable state storage with the `providers` command Note: I've excluded the `terraform providers locks` and `terraform providers mirror` commands as they don't interact with backends. * test: Add integration test for using pluggable state storage with the `providers` command * refactor: Change ioutil.ReadDir to os.ReadDir * test: Add integration test for using pluggable state storage with the `providers schema` command * feat: Allow state store schema's to be included when schemas are marshalled into JSON output * test: Assert that state stores are present in provider schemas returned from `providers schema`. * test: Update existing tests to accommodate state stores being in provider schema output * test: Update E2E test for `providers` commands to be better scoped to testing use of a state store to access and use state when generating output. This complements TestProvidersSchema that tests that state stores in a provider are reflected in the JSON representations of the schemas that the command returns. * chore: Replace `io/ioutil` with `io` in `providers schema` tests	2025-12-17 19:44:36 +00:00
Sarah French	578766bdc0	PSS: Add tests showing output and show commands being used with PSS (#37894) ... * test: Add E2E test demonstrating `output` command used with PSS * test: Add E2E test demonstrating `show` command used with PSS * docs: Fix code comment * test: Add integration test for using pluggable state storage with the `output` command * test: Add integration test for using pluggable state storage with the `show` command	2025-12-17 18:11:48 +00:00
Sarah French	940fbfb7ed	test: Add more test coverage of validate command's interaction with backend blocks (#37977) ... * test: Show how the validate command doesn't detect when an unknown backend type is in the config. * test: Minor fixes to error messages when test fails * test: Add some TODOs in code comments These tests are here to define existing behaviour, not define desired behaviour. I wanted to make that clear!	2025-12-17 18:09:54 +00:00
Sarah French	33d54b9a7c	test: Update module used for testing init's -from-module feature, so that the test can be run on darwin_arm64 platforms. (#38015)	2025-12-17 16:12:41 +00:00
hc-github-team-tf-core	e4ffb51022	Cleanup after 1.15.0-alpha20251203 release (#38002)	2025-12-15 18:10:57 +00:00
Radek Simko	213d133d86	command/meta: Enable migration from PSS to a backend (#37949) ... * command/meta: Enable migration from PSS to a backend * Address PR feedback * Update internal/command/meta_backend.go Co-authored-by: Sarah French <15078782+SarahFrench@users.noreply.github.com> * meta_backend: Rename stateStore_c_S to stateStore_to_backend --------- Co-authored-by: Sarah French <15078782+SarahFrench@users.noreply.github.com>	2025-12-15 10:29:34 +00:00
Nick Fagerlund	b2aad914f1	stacks: Make path.module and path.root relative, to match documentation (#37982) ... * stacks: Make path.module and path.root relative, to match documentation Previously, we were just handing off the absolute path produced by the sourcebundle struct. But that's no good, because the value doesn't stay consistent between plan and apply when running under tfc-agent. (It uses working directories named after the unique job ID.) It also doesn't match the documentation, which describes these as relative paths. This was preventing people from uploading module-provided files to create aws lambda functions, for example. This commit addresses that by converting the source-bundle provided module path to a relative path (relative to Terraform's working directory). In tfc-agent for stacks runs, that ends up being the directory directly above the sourcebundle directory, and all the paths below that are consistent between plan and apply. * I think this is how the changelog thing works?	2025-12-12 11:05:32 -08:00
Sarah French	f591872699	PSS: Allow pluggable state store configuration to be stored in a plan file (#37956) ... * refactor: Rename Meta's backendState field to backendConfigState This helps with navigating ambiguity around the word backend. The new name should indicate that the value represents a `backend` block, not a more general interpretation of what a backend is. * fix: Only set backendConfigState to synthetic object if it's nil due to a lack of data. Don't change it if pluggable state storage is in use. * feat: Enable recording a state store's details in an Operation, and using that data when creating a plan file. * fix: Include provider config when writing a plan file using pluggable state storage * fix: Having `backendConfigState` be nil may be valid, but it definitely isn't valid for `stateStoreConfigState` to be nil When backendConfigState is nil it means that an implied local backend is in use, i.e. there is no backend block in the config. * test: Add integration test showing that a plan command creates a plan file with the expected state_store configuration data * refactor: Apply suggestion from @radeksimko Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com> * fix: Allow panics to occur if an unexpected implementation of `backend.Backend` is encountered when managing a state store * docs: Add code comment explaining the current situation with passing backend config state to downstream logic. In future this should be simplified, either via refactoring or changes affecting the implied local backend --------- Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com>	2025-12-11 11:41:36 +00:00
Daniel Schmidt	2eb22c8435	backport fix to 1.14	2025-12-11 10:42:52 +01:00
Daniel Schmidt	c71e0d736c	add changelog entry	2025-12-11 10:42:52 +01:00
Matej Risek	768b7bd0bc	Add local values walk to walk_dynamic ... This helps us catch diagnostics in locals that only happen during evaluation Co-authored-by: Mutahhir Hayat <mutahhir.hayat@hashicorp.com> Co-authored-by: Matej Risek <matej.risek@hashicorp.com>	2025-12-11 10:42:52 +01:00