terraform

Commit Graph

Author	SHA1	Message	Date
Sarah French	9595517730	Update test for autocompletion of top-level commands (#37853 ) * Update test for autocompletion of top-level commands * Add test coverage for autocompletion of workspace names in `workspace select` subcommand * Remove autocompletion tests for workspace select	4 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	4 months ago
Radek Simko	5001deb4a2	PSS: Ensure experimental backend codepath is isolated + gated correctly (#37868 ) * PSS: Ensure experimental backend codepath is isolated + gated correctly * Update init_run.go Co-authored-by: Sarah French <15078782+SarahFrench@users.noreply.github.com> --------- Co-authored-by: Sarah French <15078782+SarahFrench@users.noreply.github.com>	4 months ago
James Bardin	39eb8c7fb4	Merge pull request #37854 from hashicorp/jbardin/provider-eval-scope Allow inconsistent filesystem function results for provider configuration	4 months ago
Daniel Schmidt	3055256140	suggest similarly named action	4 months ago
Daniel Schmidt	b0e7f3ab2e	improve wording and subject of error message	4 months ago
Daniel Banck	6b038754f0	Fix list resource diagnostics check (#37863 ) * Fix list resource diagnostics check * Improve error message on missing identity schema * Add test case for list response diagnostics * Add changelog	4 months ago
Sarah French	f5a28cfa8b	PSS: Update how commands access backends, so both `backend` and `state_store` configuration can be used (#37569 ) * Add a generic method for loading an operations backend in non-init commands * Refactor commands to use new prepareBackend method: group 1 * Refactor commands to use new prepareBackend method: group 2, where config parsing needs to be explicitly added * Refactor commands to use new prepareBackend method: group 3, where we can use already parsed config * Additional, more nested, places where logic for accessing backends needs to be refactored * Remove duplicated comment * Add test coverage of `(m Meta) prepareBackend()` Add TODO related to using plans for backend/state_store config in apply commands * Add `testStateStoreMockWithChunkNegotiation` test helper * Add assertions to tests about the backend (remote-state, local, etc) in use within operations backend * Stop prepareBackend taking locks as argument * Code comment in prepareBackend * Replace c.Meta.prepareBackend with c.prepareBackend * Change `c.Meta.loadSingleModule` to `c.loadSingleModule` * Rename (Meta).prepareBackend to (Meta).backend, update godoc comment to make relationship to (Meta).Backend more obvious. * Revert change from config.Module to config.Root.Module * Update `(m Meta) backend` method to parse config itself, and also to adhere to calling code's viewtype instructions Update all tests and calling code following previous commit * Change how an operations backend is obtained by autocomplete code * Update autocomplete to return nil if no workspace names are returned from the backend * Add test coverage for autocompleting workspace names when using a pluggable state store * Fix output command: pass view type data to new `backend` method * Fix in plan command: pass correct view type to `backend` method * Fix `providers schema` command to use correct viewtype when preparing a backend	4 months ago
James Bardin	4934006982	CHANGELOG	4 months ago
dependabot[bot]	f0a2953bd0	build(deps): bump the github-actions-breaking group with 2 updates (#37856 ) Bumps the github-actions-breaking group with 2 updates: [actions/upload-artifact](https://github.com/actions/upload-artifact) and [actions/download-artifact](https://github.com/actions/download-artifact). Updates `actions/upload-artifact` from 4.6.2 to 5.0.0 - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](`ea165f8d65...330a01c490`) Updates `actions/download-artifact` from 5.0.0 to 6.0.0 - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](`634f93cb29...018cc2cf5b`) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions-breaking - dependency-name: actions/download-artifact 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>	4 months ago
James Bardin	4ce205da74	provider eval scope test	4 months ago
James Bardin	eaf225a871	allow inconsistent function results for providers Due to the inherently ephemeral nature of provider configuration, inconsistent function results were tolerated while evaluating provider config. This loophole was found to be used by a number of configurations, which took advantage of it to create the equivalent of ephemeral values before they formally existed in the language. In order to work around this, we create a special evaluation scope just for providers, allowing us to override the results check for filesystem functions. I've opted to not further clutter the EvalContext interface since this is intended to be a temporary workaround, and does not contribute to the testing of that interface (the interface is solely for internal unit tests anyway).	4 months ago
Liam Cervante	e44b870b8b	don't write ephemeral outputs to state (#37821 )	4 months ago
Liam Cervante	7ac2b7938e	Stacks: temporarily disable ephemeral outputs in Stack components (#37823 )	4 months ago
James Bardin	f8ae45cfc8	Merge pull request #37833 from hashicorp/jbardin/force-replace-instance Don't carry all `-replace` addresses through to every instance	4 months ago
Kevin Vu	26f289aeb5	testing: include file-level errors in JUnit skipped elements (#37806 ) * testing: include file-level errors in JUnit skipped elements Fixes #37801 * testing: use suite-level system-err for file errors	4 months ago
James Bardin	cfbde8e5fa	CHANGELOG	4 months ago
James Bardin	cac484da16	don't carry all replace addresses through instances Once we have a resource instance we no longer need to have all possible forceReplace addresses available within that instance. We can determine immediately if the instance address is in the set if replacement addresses. This avoids bugs caused by sharing the `-replace` flag addresses across all resource nodes.	4 months ago
alanpchua	b221cc0095	PSP-3163: update scan config to enable osv (#37817 )	4 months ago
Liam Cervante	411f18e6ac	ephemerals: allow root ephemeral outputs in stacks and test (#37813 ) * ephemerals: allow root ephemeral outputs in stacks and test * remember to set new opt for apply stage	4 months ago
Kristin Laemmert	d4e8f17ded	actions: remove unused variable (+ minor typos & comment cleanup) (#37804 ) * actions: remove unused variable * fix minor comments and logged typos	4 months ago
James Bardin	a7e2c9f6b2	Merge pull request #37810 from hashicorp/jbardin/unknown-pure-results filesystem functions, don't cache unknown function results	4 months ago
James Bardin	2227441f7d	don't cache unknown function results The CheckPrior function results validation did not take into account unknown values, because unknown values were not originally allowed in the plugin protocol from which this check was adapted. The test is simple, in that we can just reverse the check which originally didn't allow this change in value. Provider function return values types are defined by the protocol, and should be validated at that call site. The CheckPrior code paths should only be used for the exact purpose of detecting invalid changes in the return value between successive phases of execution.	4 months ago
Sarah French	620264e2c5	GHA to prompt reviewers to think about dependency changes when backporting (#37800 )	4 months ago
Sarah French	2e5b5dee5d	Upgrade protoc and protoc-gen-go-grpc versions to matching terraform-plugin-go (#37647 ) * Update protoc version in downloader script * go get google.golang.org/grpc/cmd/protoc-gen-go-grpc v1.5.1 This matched terraform-plugin-go * make protobuf * Run `make protobuf` * Update generator to handle generic types from google.golang.org/grpc Looks like this was added in v1.69.3 in https://github.com/grpc/grpc-go/pull/7057 ? * Run `make generate` * Fix "cannot infer Res" compile error - more usage of generics * More fixing compile errors due to switching to use of a generic * Make putting `google.golang.org/grpc` import into generated files conditional * Run `make generate` * Update more places where generics now need to be used * Update generator to handle any types from google.golang.org/grpc in same switch case.	4 months ago
Liam Cervante	edf0cd66dd	actions: fail invoke plans when action configurations are unknown (#37793 )	4 months ago
Sarah French	88e4c9e3d3	Update inaccurate comment (#37789 )	4 months ago
Sarah French	efb2a1c567	PSS: Let the `init` command recognise when there are no changes in configuration. (#37777 ) * Pull determining of PSS provider's version from current locks into a separate method * Add code for identifying when config and provider version match existing backend state (i.e. no changes) * Update test - locks are now needed before it hits expected error diag return * Add test showing successful init when no config changes are detected. * Update `getStateStorageProviderVersion` to return nil versions for builtin and re-attached providers. This makes comparison easier when determining if config has changed since last init. * Add test coverage for `getStateStorageProviderVersion` * Move testing fixtures around, preparing for different types of changed state_store config changes being tested * Add test showing that changing the state_store config is detected as a change, but handling this scenario isn't implemented yet * Update hashes in test fixture backend state file to be accurate Previously dummy values were fine, but as tests using hashes to identify changes these values need to be accurate! * Update existing test cases so that Terraform uses the same test provider version as described in the backend state file fixture for the test. * Add test showing that changing the PSS provider's config is detected as a change, but handling this scenario isn't implemented yet * Add test showing that swapping to a different state storage implementation in the same provider is detected as a change, but handling this scenario isn't implemented yet * Add test showing that changing the provider used for PSS is detected as a change, but handling this scenario isn't implemented yet * Add test showing that upgrading a provider is detected as a change, but handling this scenario isn't implemented yet * Update test to use v1.2.3 for consistency with other tests Just to avoid any confusion if copy-pasting happens in future. * More corrections to existing test fixtures - unset config should be null, and replace dummy hash values with correct values. * Fix test for using -reconfigure with state_store; the default workspace would already exist in this scenario * Update TestInit_stateStore_configUnchanged to assert that init was a no-op for backend state * Remove unused fixture * Remove test that's replaced by new tests in command/init_test.go * Replace old references to deleted "state-store-changed" test fixture & update test to not expect a value for region attr in provider config * Make test fixture coupling a little more understandable * Refactor detection of no need to migrate into a function * Add TODO about more involved provider version change tests We will allow downgrades to succeed as long as the schema version number is unchanged * Update (configs.StateStore)Hash method to return a single hash that's impacted by: state store config, provider config, state store type, provider source * Update calling code and test helper code to reflect that the nested provider block no longer has its own hash * Remove test; there is now a single hash that SHOULD be affected by the provider block! * Also use provider name, from config, in hash * Update tests to reflect changes in how hashes are made * Remove unused `stateStoreConfigNeedsMigration` function * Remove duplicate isProviderReattached function. * Fixes to affected tests * Allow provider version to impact the state storage hash, update impacted tests and test fixtures * Update tests that now require locks data to be present in test setup * Update comment for accuracy * Fixes to other test fixtures - remove excess hash field, set hash to 0 to indicate they're not set accurately. * Make upgrade test actually use upgrade code path * Add lock files to test fixture directories that represent a project that's had a successful prior init using PSS	4 months ago
Liam Cervante	106f8c6a1f	actions: refactor to simplify test hooks (#37782 )	4 months ago
Daniel Schmidt	accaa8d027	also check against action references in depends_on during config parsing	4 months ago
Daniel Schmidt	085c762cad	actions can not be used in depends_on Fixed #37780	4 months ago
Radek Simko	cbda324977	backend/oss: Bump github.com/aliyun/aliyun-oss-go-sdk to v2.1.1 (#37442 )	4 months ago
Sarah French	76f2982c68	Update the init command's help text to describe PSS-related flags (#37773 )	4 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	4 months ago
Sebastien Dionne	1047b5355c	Fix typos and linguistic errors in documentation (#37770 ) Signed-off-by: Sebastien Dionne <survivant00@gmail.com>	4 months ago
dependabot[bot]	75a9645fb5	build(deps): bump the github-actions-backward-compatible group with 2 updates (#37706 ) Bumps the github-actions-backward-compatible group with 2 updates: [actions/cache](https://github.com/actions/cache) and [miniscruff/changie-action](https://github.com/miniscruff/changie-action). Updates `actions/cache` from 4.2.4 to 4.3.0 - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](`0400d5f644...0057852bfa`) Updates `miniscruff/changie-action` from 2.0.0 to 2.1.0 - [Release notes](https://github.com/miniscruff/changie-action/releases) - [Changelog](https://github.com/miniscruff/changie-action/blob/main/CHANGELOG.md) - [Commits](`6dcc2533ca...5036dffa79`) --- updated-dependencies: - dependency-name: actions/cache dependency-version: 4.3.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions-backward-compatible - dependency-name: miniscruff/changie-action dependency-version: 2.1.0 dependency-type: direct:production update-type: version-update:semver-minor 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>	4 months ago
dependabot[bot]	0f1f573848	build(deps): bump the github-actions-breaking group with 2 updates (#37705 ) Bumps the github-actions-breaking group with 2 updates: [actions/setup-go](https://github.com/actions/setup-go) and [actions/github-script](https://github.com/actions/github-script). Updates `actions/setup-go` from 5.5.0 to 6.0.0 - [Release notes](https://github.com/actions/setup-go/releases) - [Commits](`d35c59abb0...4469467582`) Updates `actions/github-script` from 7.0.1 to 8.0.0 - [Release notes](https://github.com/actions/github-script/releases) - [Commits](`60a0d83039...ed597411d8`) --- updated-dependencies: - dependency-name: actions/setup-go dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions-breaking - dependency-name: actions/github-script dependency-version: 8.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>	4 months ago
Sarah French	d11bdf6832	Refactor backend error strings as custom errors or pre-made diagnostics (#37762 ) * Replace `errBackendLocalRead` constant with custom error of same name * Replace `errBackendNoExistingWorkspaces` constant with custom error of same name * Replace `errBackendMigrateLocalDelete` constant with custom error of same name * Replace `errBackendNewUnknown` constant with custom error of same name * Replace `errBackendSavedUnknown` constant with custom error of same name * Replace `errBackendClearSaved` constant with custom error of same name * Replace `errBackendInit` constant with custom error of same name * Replace `errBackendInitCloud` constant with custom error of same name * Replace `errBackendWriteSaved` constant with custom error of same name * Move `migrateOrReconfigDiag` next to custom errors * Replace `errBackendInit` custom error with `func errBackendInitDiag` for creating diagnostics directly * Replace `errBackendInitCloud` custom error with `func errBackendInitCloudDiag` for creating diagnostics directly * Replace `errBackendWriteSaved` custom error with `func errBackendWriteSavedDiag` for creating diagnostics directly * Add new usage of errBackendWriteSavedDiag; this is another place where failing to write to backend state files happens * Add godoc comments * Ensure errors aren't repeated in terminal output, and ensure warnings are not lost.	4 months ago
Daniel Banck	bffba7ffbc	Update release Slack channel to new grid (#37765 ) This PR replaces the old Slack channel id in our release tooling configuration with the new one.	4 months ago
Kristin Laemmert	8b0ccce413	actions: fix race condition in tests and capture errors from hooks (#37759 )	4 months ago
Sarah French	d6865bf7a9	PSS : Implement Lock and Unlock methods on remote grpc client (#37741 ) * Implement Lock and Unlock methods on grpcClient * Add tests for Lock and Unlock methods * Reuse same lock info variable	4 months ago
Dirk Avery	fc3b1ed174	Merge pull request #37752 from hashicorp/t-bump-go-getter Bump go-getter v1.8.2	4 months ago
Daniel Banck	cc30a8cf1d	Fix crash when showing a cloud plan without having a cloud backend (#37751 ) * Fix crash when showing a cloud plan without a cloud backend * Add changelog	4 months ago
Dirk Avery	edb3f6487d	Bump go-getter v1.8.2	4 months ago
Daniel Schmidt	2714cfde69	standardize on marks.Has	4 months ago
Sarah French	2657a4daec	Set let require_unimplemented_servers default to true when generating code from .proto files (#37737 ) * Remove `require_unimplemented_servers=false` option when generating code from proto files. Run `make protobuf`. This allows require_unimplemented_servers to default to true, and the generated code shows the impacts of that. * Update generator script to embed 'UnimplementedFoobarServer' structs and skip generating code for the `mustEmbedUnimplementedFoobarServer` method that is implemented via that embedding. * Run `make generate` * Embed UnimplementedProviderServer into implementations of ProviderServer * Embed UnimplementedProvisionerServer into implementations of ProvisionerServer	4 months ago
Liam Cervante	6b17cfe2e5	actions: connect invoke flag with TFC (#37544 ) * actions: connect invoke flag with TFC * use latest go-tfe	4 months ago
Liam Cervante	39d1293cf6	actions: consider event type when comparing action triggers (#37733 )	4 months ago
Dirk Avery	c4a7f00c6f	Merge pull request #37721 from hashicorp/t-bump-aws-sdk-go-base AWS European Sovereign Cloud support, bump aws-sdk-go-base	4 months ago
Liam Cervante	9239dd62e9	actions: enforce ephemeral into write-only attributes behaviour (#37701 ) * actions: add test that validates ephemeral behaviour * actuall prevent ephemeral values into non write-only attributes * remove old invalid test	4 months ago

1 2 3 4 5 ...

34830 Commits (9595517730cd8f06d172810a6a5a11d45b6d8927) All Branches Search

34830 Commits (9595517730cd8f06d172810a6a5a11d45b6d8927)

All Branches