terraform

Commit Graph

Author	SHA1	Message	Date
Daniel Banck	65c7a3b9f3	Add changelog	1 month ago
Radek Simko	07b3e3b800	command/init: Merge duplicated PSS logic back into existing codepath (#38227 )	1 month ago
James Bardin	7960f60d21	Merge pull request #38160 from hashicorp/jbardin/inline-type-conversion inline type conversions	1 month ago
Sebastian Rivera	2f457cb416	chore: add changelog entry	1 month ago
Daniel Schmidt	dbfe0cb20a	add changelog entry	2 months ago
Sarah French	a1d962b9aa	docs: Update issue reference in change file for v1.15 (#38195 )	2 months ago
Sarah French	eab282f617	test: Add `http` backend locking test (#38192 ) * test: Update TestHTTPBackend so it can be created with pre-existing lock info inside it. This will be used for tests that want to assert the lock info returned with lock errors. * test: Add a test asserting data returned in lock errors from the http backend. * chore: Replace use of `io/ioutil` in http backend * chore: Update changelog entry to link to the original PR https://github.com/hashicorp/terraform/pull/38144 * test: Improve test code comments	2 months ago
Nicholas Ngai	5e4cfd42fa	backend/http: Return existing lock info from backend on conflict (#38144 ) * Return existing lock info from http state backend on conflict * Remove info from LockError if failed to read or unmarshal * Add change to .changes	2 months ago
Varun Chawla	a5aa6cc5b7	states: fix RootOutputValuesEqual comparing s2 to itself (#38181 ) * states: fix RootOutputValuesEqual comparing s2 to itself RootOutputValuesEqual had a copy-paste bug where it iterated over s2.RootOutputValues instead of s.RootOutputValues, effectively comparing s2 against itself rather than comparing the receiver (s) against the argument (s2). This meant the function would always return true as long as both states had the same number of output values, regardless of whether the actual values differed. This bug was introduced in #37886 and affects refresh-only plan mode, where RootOutputValuesEqual is used to determine if root output values changed during refresh, which controls whether the plan is considered applyable. * add changelog entry for RootOutputValuesEqual fix * Update changelog wording per reviewer suggestion Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>	2 months ago
James Bardin	c507cfe455	CHANGELOG	2 months ago
Brandon Croft	ca320f398f	Revert "Create BUG FIXES-20260114-135324.yaml" This reverts commit `cb615c38d8`.	2 months ago
Sarah French	694f746748	validate: Add checking the backend block to the `validate` command (#38021 ) * feat: Make validate command detect when an unknown backend type is in use. * feat: Make validate command detect when the backend configuration doesn't match the schema. * fix: Stop suppressing the Required:true parts of the backend schema when validating backend blocks * test: Add test showing validation fails when a required attribute is missing from a backend's config	2 months ago
Daniel Banck	d103825d84	Move changelog file to avoid duplicate entry This PR moves the changelog file for the fix in #38025 into the 1.14 directory. Since it was backported we would otherwise end up with two changelog entries. One in 1.14.x and one in 1.15.x	2 months ago
Abdurahman Abdelgany	587fc8e66b	Merge branch 'main' into stacks_validate_relative_path_fix	2 months ago
Daniel Schmidt	f44decc5f1	fix PR link	2 months ago
Brandon Croft	cb615c38d8	Create BUG FIXES-20260114-135324.yaml	2 months ago
Daniel Schmidt	7eaf6daf60	add deprecation marks to resources based on schema	2 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>	2 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.	2 months ago
Daniel Schmidt	f4c22be3c5	stacks: send progress events on failed provider configurations	2 months ago
Daniel Schmidt	492d342aab	ensure actions dont break the graph in modules with no instances	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
Abdurahman Abdelgany	1ed50c2aca	Changelog entry Co-authored-by: Arun Ramakrishnan arun@ibm.com Co-authored-by: Sahar Azizighannad Sahar.Azizighannad@hashicorp.com	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
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	3 months ago
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>	3 months ago
Michael Yocca	810f497ecd	fix(cloud): cloud backend rendering query warning diags (#38040 )	3 months ago
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.	3 months ago
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.	3 months ago
Jared Baker	4f53303c12	Merge branch 'main' into fix/s3-backend-fips-env-var-parsing	3 months ago
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	4 months ago
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?	4 months ago
Daniel Schmidt	2eb22c8435	backport fix to 1.14	4 months ago
Daniel Schmidt	c71e0d736c	add changelog entry	4 months ago
Daniel Schmidt	889d605664	backport this change to 1.14	4 months ago
Daniel Schmidt	37e0194a23	changelog entry	4 months ago
James Pogran	2c075b9f8e	Add component registry source resolution support to Terraform Stacks (#37888 ) * Add component registry source resolution support to Terraform Stacks This change implements the missing component source resolution case in the stack configuration loader, enabling Terraform Stacks to properly handle component registry sources from HCP Terraform and other component registries. The implementation mirrors the existing module registry resolution workflow, where component sources are first resolved to their versioned form using the source bundle's component metadata, then converted to final source addresses that can be used to locate the actual component code. This completes the integration between the terraform-registry-address component parsing capabilities and the go-slug sourcebundle component resolution APIs. * chore: bump go-slug to v0.18.1 * fix: add case for component final source type * chore: rm space * chore: sync module deps * chore: update testdata with separate bundle * fix: manifest file json obj with trailing comma * Add changelog entry to 1.14 --------- Co-authored-by: Michael Yocca <michael.yocca@hashicorp.com>	4 months ago
Kevin Vu	b62d97ac88	fix: parse boolean env vars in S3 backend correctly Fixes #37601	5 months ago
Kevin Vu	87b3390189	fix: Make init backend messages JSON-compatible (#37920 ) * fix: Make all init backend messages JSON-compatible Fixes #37911 by converting all backend configuration messages to use the View abstraction, which properly formats output as JSON when the -json flag is used. Previously, certain messages were output directly using the legacy Ui abstraction, bypassing JSON formatting. Changes: - Added 11 new message codes to init.go MessageRegistry with both human and JSON formatted values - Replaced 11 direct m.Ui.Output() calls in meta_backend.go with View abstraction calls - Fixed output in backend_C_r_s(), backend_C_r_S_changed(), backend_c_r_S(), and stateStore_c_S() functions All init tests pass successfully. * docs: Add changelog entry for init JSON backend messages fix * cleanup: Remove unused backend output constants The following constants were moved to init.go as message registry entries and are no longer used in meta_backend.go: - outputBackendMigrateChange - outputBackendMigrateLocal - outputStateStoreMigrateLocal - outputBackendReconfigure - successBackendUnset - successBackendSet	5 months ago
Daniel Schmidt	7647923c53	actions: connect resource instance nodes to after actions	5 months ago
Sarah French	4381860dc6	fix: Make `state show` command exit with code 1 if the stored state cannot be marshalled for rendering (#37933 ) Prior to this change, when running a `state show` command with an address for a resource that existed in state but didn't match the current schema of the resource, users would see the "Failed to marshal" error but would also see output saying "The state file is empty. No resources are represented". This is misleading, as the state file isn't empty. Also, the command would exit with code 0 despite the error.	5 months ago
Steven Masley	3df28c3101	fix: Make `terraform init` JSON log timestamps include millisecond precision (#37818 ) * fix: terraform init log timestamps include millisecond precision * docs: add changelog entry	5 months ago
Daniel Schmidt	808713f56f	Fix changie entry I was linking to the issue we fixed, not the PR	5 months ago
Kevin Vu	dc0eba33af	fix: support ephemeral resources in jsonchecks (#37893 ) Fixes #37834	5 months ago
Liam Cervante	cfbfdc5797	providers lock: include test files when loading configuration (#37851 )	5 months ago
Daniel Schmidt	1b662d78e5	init: skip dependencies declared in development override	5 months ago
James Bardin	64f2b5d9c6	Merge pull request #37886 from hashicorp/jbardin/state-deep-equal Implement equality for state objects	5 months ago
James Bardin	f78c64e528	CHANGELOG	5 months ago
Radek Simko	40482337a7	ssh-based provisioner: Re-enable support for PowerShell (#37794 ) * ssh-based provisioner: Re-enable support for PowerShell * add changelog entry	5 months ago

1 2 3 4

184 Commits (add-missing-variable-loading)