terraform

Commit Graph

Author	SHA1	Message	Date
Daniel Banck	2d53372dd8	Introduce new source for variables from the cloud backend	4 weeks ago
Sarah French	c05eaaf20d	PSS: Refactor how we handle unmanaged providers, add support for using dev_override (#38269 ) * feat: Enable use of developer override providers when using PSS * feat: Store how a provider was supplied to Terraform in the backend state file. This allows triggering a prompt for state migration if there's a change between using a managed provider versus an unmanaged/override provider. * test: Update all PSS-related backend state files in test fixtures to include new, necessary provider_supply_mode data. * fix: Avoid duplicate dev_override warnings * refactor: Change how we determine how a provider is supplied to Terraform. By using supply mode data we prevent multiple parts of the code checking if a given provider is reattached/builtin/etc... * test: Add separate tests showing a built-in or dev override provider being used for the main workflow using PSS * test: Add E2E tests that characterise current behaviour when how a provider is supplied is changed partway through different workflows * fix: Tolerate missing default workspace when using PSS and init handles minor changes in state store configuration. * feat: `init`-related code will prompt a user to migrate state if Terraform detects a swap between managed and unmanaged providers being used for PSS. Internally, what happens is the different version data (null versus a value being present) impacts the hash of the state store. This then triggers logic where TF checks if a migration is needed or if the new hash value should be silently updated in the backend state file. We always prompt for migration. * refactor: Add `NotManagedByTerraform` method to `ProviderSupplyMode` * Apply suggestions from code review Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com> --------- Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com>	1 month ago
Daniel Banck	cd5eb226cc	Bump github.com/go-jose/go-jose/v4 to v4.1.4	1 month ago
Sarah French	2c5e03f229	Bump go-getter to v1.8.6, bump Go version, address breaking changes introduced by dependency bump. (#38374 ) * chore: go get github.com/hashicorp/go-getter@v1.8.6 & make syncdeps. Replace deprecated methods. The interceptor methods used in the rpcapi package needed to be replaced with the new stats-handlers. These were removed around v1.36.0 of the go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc dependency * chore: Update .go-version * tests: Address breaking change in cloud.google.com/go/storage dependency that affects returned errors See `0dd7d3d62e` for more information.	1 month ago
Sarah French	9b970d5454	chore: go get go.opentelemetry.io/otel/sdk@v1.43.0 & make syncdeps (#38366 )	2 months ago
Sarah French	6f6fef17a3	Bump github.com/aws/aws-sdk-go-v2 related packages to address reported vulnerability (#38362 ) * chore: go get github.com/aws/aws-sdk-go-v2/service/s3@v1.97.3 * chore: make syncdeps	2 months ago
Brandon Croft	b4ddd25f6e	Bump terraform-svchost to 0.2.1 (#38236 )	2 months ago
Daniel Banck	6843a8dcd7	Use variables from planfile during a local run from plan During apply all variables required to load configuration should be available from the planfile. We shouldn't run our regular checks for variable values.	2 months ago
Daniel Banck	5bf90e356f	Allow commands to fetch backend variables The new `resolveConstVariables` helper checks if const variables are present in the configuration, but don't have a value yet. In that case we try to fetch them via a backend. This will only work for backends that implement the ConstVariableSupplier interface. (Which the `cloud` backend does) The precedence is the same as for existing commands: a CLI supplied value will override a value from a workspace	2 months ago
Daniel Banck	36b5207d2b	Still require const variables when AllowUnsetVariables is set We never want to stub const variables, so we will always try to get values for them. The cloud backend now always fetches variable values so const vars can be satisfied.	2 months ago
Daniel Banck	1d517c3ae8	Add check for missing const variables	2 months ago
Daniel Banck	97534ebd3b	Improve ParseVariableValues signature with a helper Instead of passing a "magic" boolean as third parameter, we now have two functions `ParseConstVariableValues` and `ParseVariableValues`.	2 months ago
Daniel Banck	a47b89170f	Fix ParseVariableValues for different command flows We want to treat `const` variables as part of the configuration, we always require a value for them when loading configuration. Since most command load configuration via `Meta.loadConfig` or `Meta.loadConfigWithTests`, these flows call `ParseVariableValues` with `constOnly` true. Backend operations like `plan` and `apply` require values for all required variables (as before), so here we set `constOnly` to false, to keep the existing logic.	3 months ago
James Bardin	bcd60bf017	make syncdeps	3 months ago
Daniel Schmidt	a9756b273c	move initwd config loading into terraform otherwise we run into cyclic references	3 months ago
Daniel Banck	4ef9684188	Rework most of the configuration loading We previously used a loader -> BuildConfig flow to load configuration. This commit changes most (but not all yet) flows to use the new graph-based approach. Instead of simply recursively loading the modules, we now need to take a stepped approach: 1. Load the root module 2. Collect the variables and their values 3. Build the configuration with the graph-based approach Because this approach relies on different parts from different packages, it can't easliy be done within the `configload` package. So, now we do most of in the backend or command.	3 months ago
Radek Simko	07b3e3b800	command/init: Merge duplicated PSS logic back into existing codepath (#38227 )	3 months ago
Daniel Schmidt	2424cf6423	make test case more robust to developer environments	3 months ago
Daniel Banck	a39e3bce32	make syncdeps	3 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	3 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	3 months ago
Daniel Schmidt	026c935961	move UnparsedVariableValue from backendrun to arguments This prevents a cyclic dependency and also makes sense semantically. The arguments package will collect the unparsed variable values and the backendrun helpers will work to collect the values and transform them into terraform.InputValue.	3 months ago
Sarah French	817ed318db	chore: Update go version from 1.25 to 1.25.7 (#38185 ) * chore: Update go version from 1.25 to 1.25.7 * chore: make syncdeps	3 months ago
Radek Simko	0fe906fa8c	make copyrightfix	3 months ago
Radek Simko	244443b3e0	make syncdeps	3 months ago
Brandon Croft	1df7030c5a	Revert "make syncdeps" This reverts commit `c42d0006fe`.	3 months ago
Radek Simko	27770ee805	PSS: Migration from a backend to a state store (#38048 ) * backend/inmem: Make it easier to use the backend in tests * cloud: Make the cloud backend testable * command/views: Introduce migration UI messages * command/init: Add 3 tests for migrations from a backend to PSS - TestInit_backend_to_stateStore_singleWorkspace - TestInit_backend_to_stateStore_multipleWorkspaces - TestInit_cloud_to_stateStore * command/init: Implement migration from a backend to PSS * address PR feedback * remove local state after migration	4 months ago
Brandon Croft	c42d0006fe	make syncdeps	4 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>	4 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`	4 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	4 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.	5 months ago
Jared Baker	4f53303c12	Merge branch 'main' into fix/s3-backend-fips-env-var-parsing	5 months ago
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>	5 months ago
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>	6 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>	6 months ago
Sarah French	9fb91c2229	PSS: Refactor Plan struct to reference `Backend` and `StateStore` via pointers, update calling code (#37946 ) * refactor: Update Plan struct's Backend field to be a pointer * fix: Add some refactorings or protections against nil pointers when accessing the Backend field on a Plan struct * refactor: Update Plan struct's StateStore field to be a pointer, update a nil check in calling code.	6 months ago
Sarah French	64015ca6d2	refactor: let panic arise directly if the provider doesn't implement providers.StateStoreChunkSizeSetter (#37942 )	6 months ago
Sarah French	cf047be4e4	PSS: Use interfaces to configure state stores (#37899 ) * refactor: Move chunk size limit constants to new `chunks` package * refactor: Make `NewPluggable` return a `Pluggable` concrete type, instead of an instance of the `backend.Backend` interface. * refactor: Configure state stores through the backend.Backend interface, instead of directly using methods related to RPCs. This requires changing where we call `SetStateStoreChunkSize`. * docs: Add godocs comment to `StateStoreChunkSizeSetter` interface To summarize, we don't really need the `SetStateStoreChunkSize` method, and instead methods like `(GRPCProvider).ConfigureStateStore` in the `plugin6` package can directly inspect the negotiation process that passes through that code and pull out the chunk size. However that means that that code would also need to implement validation. And that's just `(GRPCProvider).ConfigureStateStore`; what about all the test mocks that are used in different types of test? They would all need to be implemented similarly to GRPCProvider to be good, useful mocks, and then a lot of things that fulfil the provider.Interface interface are coupled to each other. Instead, it's easier to have validation in the `grpcClient` struct's methods in the `remote` package, as that code is common to all scenarios. That code needs a method to 'reach into' the provider.Interface value, so we use the `SetStateStoreChunkSize` method. * chore: Make it clearer that the v6 GRPCProvider implements `SetStateStoreChunkSize` * fix: Remove unnecessary assignment of chunk size I'm surprised that removing this doesn't break E2E tests of PSS that use grpcwrap, but I think there's `plugin6` code that runs in that situation, so maybe chunking is handled elsewhere. * chore: Add panic to try detect unexpected cases when setting chunk size. * feat: Add `providers.StateStoreChunkSizeSetter` implementation to provider-simple-v6 * docs: Update code comments for NewPluggable describing its intended use	6 months ago
Kevin Vu	b62d97ac88	fix: parse boolean env vars in S3 backend correctly Fixes #37601	6 months ago
dependabot[bot]	7034a193d9	build(deps): bump golang.org/x/crypto from 0.44.0 to 0.45.0 (#37925 ) * build(deps): bump golang.org/x/crypto from 0.44.0 to 0.45.0 Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.44.0 to 0.45.0. - [Commits](https://github.com/golang/crypto/compare/v0.44.0...v0.45.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.45.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> * run syncdeps --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Daniel Banck <daniel@dbanck.de>	6 months ago
Sarah French	1dd8e60f15	chore: Bump golang.org/x/crypto dependency, ignore SA4003 linting errors globally (#37901 ) * chore: Upgrade golang.org/x/crypto - `go get golang.org/x/crypto@v0.44.0` * chore: Upgrade golang.org/x/crypto in submodules - `make syncdeps` * chore: Run `make generate` * chore: Ignore SA4003 linter error globally, as `golang.org/x/tools/cmd/stringer` generates code that breaks this rule when it's used with custom types that have unsigned integers or bytes as the underlying type.	6 months ago
Sarah French	f2818db795	PSS : Add `fs` and `inmem` state storage implementations to the builtin `simplev6` provider, update `grpcwrap` package, use PSS implementation in E2E test (#37790 ) * feat: Implement `inmem` state store in provider-simple-v6 * feat: Add filesystem state store `fs` in provider-simple-v6, no locking implemented * refactor: Move PSS chunking-related constants into the `pluggable` package, so they can be reused. * feat: Implement PSS-related methods in grpcwrap package * test: Add E2E test checking an init and apply (no plan) workflow is usable with both PSS implementations * fix: Ensure state stores are configured with a suggested chunk size from Core --------- Co-authored-by: Radek Simko <radeksimko@users.noreply.github.com>	7 months ago
Sarah French	f4d0ec5136	PSS: Fix hashing without provider version (#37852 ) * Fix panic hashing backend config when a builtin or reattached provider is used for PSS * Add test showing a nil version.Version is tolerated by the Hash method, refactor existing test Protect against provider version data missing when using an un-reattached, un-builtin provider. Add test coverage. * Make reporting errors from reattach.IsProviderReattached more consistent * Run `make syncdeps` * Update tests to show when nil provider data is tolerated	7 months ago
Radek Simko	cbda324977	backend/oss: Bump github.com/aliyun/aliyun-oss-go-sdk to v2.1.1 (#37442 )	7 months ago
Sarah French	6b73f710f8	PSS: Implement initialisation of new working directory (or use of `-reconfigure` flag) while using `state_store` (#37732 ) * Minor fixes in diagnostics This can only be done once modules have been parsed and the required providers data is available. There are multiple places where config is parsed, into either Config or Module structs, so this needs to be implemented in multiple places. * Rename test to make it specific to use of backend block in config * Update initBackend to accept whole initArgs collection * Only process --backend-config data, when setting up a `backend`, if that data isn't empty * Simplify how mock provider factories are made in tests * Update mock provider's default logic to track and manage existing workspaces * Add `ProviderSchema` method to `Pluggable` structs. This allows calling code to access the provider schema when using provider configuration data. * Add function for converting a providerreqs.Version to a hashicorp/go-version Version. This is needed for using locks when creating the backend state file. * Implement initial version of init new working directories using `stateStore_C_s`. Default to creating the default workspace if no workspaces exist. * Update test fixtures to match the hashicorp/test mock provider used in PSS tests * Allow tests to obtain locks that include `testingOverrides` providers. The `testingOverrides` field will only be set in tests, so this should not impact end users. * Add tests showing TF can initialize a working directory for the first time (and do the same when forced by -reconfigure flag). Remove replaced tests. * Add -create-default-workspace flag, to be used to disable creating the default workspace by default when -input=false (i.e for use in CI). Refactor creation of default workspace logic. Add tests. * Allow reattached providers to be used during init for PSS * Rename variable to `backendHash` so relation to `backend` is clearer * Allow `(m Meta) Backend` to return warning diagnostics Protect against nil testingOverrides in providerFactoriesFromLocks * Add test case seeing what happens if default workspace selected, doesn't exist, but other workspaces do exist. The consequences here are due to using `selectWorkspace` in `stateStore_C_s`, matching what's done in `backend_C_r_s`. * Address code consistency check failure on PR * Refactor use of mock in test that's experiencing EOF error... * Remove test that requires test to supply input for user prompt This test passes when run in isolation but fails when run alongside other tests, even when skipping all other tests using `testStdinPipe`. I don't think the value of this test is great enough to start changing how we test stdin input. * Allow -create-default-workspace to be used regardless of whether input is enabled or disabled * Add TF_SKIP_CREATE_DEFAULT_WORKSPACE environment variable * Responses to feedback, including making testStdinPipe helper log details of errors copying data to stdin. Note: We cannot call t.Fatal from a non-test goroutine. * Use Errorf instead * Allow backend state files to not include version data when a builtin or reattached provider is in use. * Add clarifying comment about re-attached providers when finding the matching entry in required_providers * Report that the default workspace was created to the view * Refactor: use error comparison via `errors.Is` to identify when no workspaces exist. * Move handling of TF_ENABLE_PLUGGABLE_STATE_STORAGE into init's ParseInit func. * Validate that PSS-related flags can only be used when experiments are enabled, enforce coupling of PSS-related flags when in use. * Slight rewording of output message about default workspace * Update test to assert new output about default workspace	7 months ago
Dirk Avery	edb3f6487d	Bump go-getter v1.8.2	8 months ago
Liam Cervante	6b17cfe2e5	actions: connect invoke flag with TFC (#37544 ) * actions: connect invoke flag with TFC * use latest go-tfe	8 months ago
Dirk Avery	c5cdbf00c6	sync deps	8 months ago
Dirk Avery	5e3a9fbdf3	Bump aws-sdk-go-base	8 months ago

1 2 3 4 5 ...

675 Commits (f8fb61de12dea9ac94de3060a0d3e97ce9b5480b)