346 Commits (1298fcd41259c2cf66306cce2453efd2c19f445d)

Author	SHA1	Message	Date
Graham Davison	57ec131e80	Ignores `AccessDenied` errors when listing bucket with default prefix	2 years ago
Graham Davison	40e593ddc1	Adds constant for default workspace prefix	2 years ago
Jamie Finnigan	05b0bdac99	adopt hashicorp/cli fork of mitchellh/cli (#34429)	2 years ago
Graham Davison	a8028da56f	Adds test for standard envvar overriding legacy envvar	2 years ago
Graham Davison	c9eae74ba7	Adds tests to handle legacy config and envvars	2 years ago
Graham Davison	c701ad1e2a	Adds tests for STS endpoint override	2 years ago
Martin Atkins	b0b8d4aa6f	states: Only track root module output values ... For a very long time we've had an annoying discrepancy between the in-memory state model and our state snapshot format where the in-memory format stores output values for all modules whereas the snapshot format only tracks the root module output values because those are all we actually need to preserve between runs. That design wart was a result of us using the state both as an internal and an external artifact, due to having nowhere else to store the transient values of non-root module output values while Terraform Core does its work. We now have namedvals.State to internally track all of the throwaway results from named values that don't need to persist between runs, so now we'll use that for our internal work instead and reserve the states.State model only for the data that we will preserve between runs in state snapshots. The namedvals internal model isn't really designed to support enumerating all of the output values for a particular module call, but our expression evaluator currently depends on being able to do that and so we have a temporary inefficient implementation of that which just scans the entire table of values as a stopgap just to avoid this commit growing even larger than it already is. In a future commit we'll rework the evaluator to support the PartialEval mode and at the same time move the responsiblity for enumerating all of the output values into the evaluator itself, since it should be able to determine what it's expecting by analyzing the configuration rather than just by trusting that earlier evaluation has completed correctly. Because our legacy state string serialization previously included output values for all modules, some of our context tests were accidentally depending on the implementation detail of how those got stored internally. Those tests are updated here to test only the data that is a real part of Terraform Core's result, by ensuring that the relevant data appears somewhere either in a root output value or in a resource attribute.	2 years ago
Jared Baker	4729af3ccf	Merge pull request #34337 from hashicorp/s3/use_legacy_workflow-deprecation ... backend/s3: default `use_legacy_workflow` to false, deprecate	2 years ago
Kubo	c98e355ca1	terraform test: Collect variables from default var file within testing directory (#34341) ... * Add logic to collect variables for terrafrom test * Add tests for test variable collection * Update the test variable collection implementation * Update internal/backend/local/test.go Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com> * Update internal/backend/local/test.go Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com> * Move test variables into var file * resolve diff from cross-branch switch * go fmt --------- Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com>	2 years ago
Martin Atkins	0f845adfdb	moduletest: EvalContext lives outside of the "terraform" package ... The initial implementation of the module testing language included some elements deeply embedded inside "package terraform", which is primarily concerned with the traditional Terraform language, which we might now call the "module language" to distinguish it from the test language and the stacks language. That was a reasonable design decision due to the modules runtime needing to evaluate some expressions in a similar way to how the modules language does it, but unfortunately it caused the test language runtime to depend a little too closely on some current implementation details of how the modules runtime deals with expression evaluation, and those details are about to change as we teach Terraform to be able to deal with unknown values in new places, as part of resolving this issue: https://github.com/hashicorp/terraform/issues/30937 This commit therefore refactors the test runtime a little so that it doesn't intrude so deeply into the module runtime's business. Instead of directly extending the module runtime's expression evaluator, we'll instead call into it in a similar way to how the "terraform console" command does, by wrapping the evaluation data produced by the module runtime to extend it with the only two special things that the test runtime needs: references to the output values of previous runs, and references to test-only variables that aren't declared as part of the module under test. This effectively means that the test runtime can now evaluate a superset of the expressions that would be valid in the global scope of the module under test using only the public API of the modules runtime, with no testing-specific evaluation logic embedded inside the modules runtime. This new strategy is also somewhat similar to how the stacks runtime calls into the modules runtime to evaluate components, but the stacks runtime only actually cares about output values and so doesn't need a full evaluation scope. This means the result here is a little more symmetrical with the approach we took in stacks, which will hopefully allow experience working on one to translate better to the other.	2 years ago
Jared Baker	470a851e45	backend/s3: default use_legacy_workflow to false, deprecate ... In Terraform 1.7 we'll begin phasing out the legacy credential chain evaluation order by defaulting use_legacy_workflow to false and deprecating the argument. This will bring the default behavior into alignment with the AWS SDKs and CLI. Practitioners can still preserve the legacy behavior by setting this argument to `true`. In Terraform 1.8 this argument will be removed, and the S3 backend will always use the default credential chain evaluation order from the AWS SDK for Go.	2 years ago
Liam Cervante	9ea1aa0a86	terraform test: skip destroy step for empty run blocks (#34331)	2 years ago
Liam Cervante	6670ab43f7	terraform test: rearrange the order of destroy operations (#34293)	2 years ago
Graham Davison	39b7def2bd	Updates `aws-sdk-go-base`	2 years ago
Graham Davison	4df60b4b90	Adds `https_proxy` and `no_proxy` parameters	2 years ago
Graham Davison	c018798f15	Merge pull request #34195 from hashicorp/f-sso-endpoint ... backend/s3: Adds SSO endpoint override	2 years ago
Martin Atkins	42d40f73b6	core: Context.Apply takes "opts" argument ... We don't yet have any special apply-time options, but we'll add some in future commits. This separate commit is just to get all of the mechanical noise of updating the tests and callers out of the way before doing anything more interesting.	2 years ago
Liam Cervante	dedb296773	terraform test: connect mock behaviour to test framework (#34205) ... * connect mock behaviour to test framework * fix calling unconfigured providers	2 years ago
Liam Cervante	57edb9c248	testing framework: add warnings for override blocks with invalid targets (#34181) ... * testing framework: add warnings for override blocks with invalid targets * pre-add the override sources for upcoming features * address comments	2 years ago
Graham Davison	c3d4124ccf	Updates `aws-sdk-go-base`	2 years ago
Graham Davison	43215009c2	Moves SSO testing to shared config tests in `aws-sdk-go-base`	2 years ago
Graham Davison	a0e85b2434	Replaces `ValidateDiags` with `cmp.Diff`	2 years ago
Graham Davison	fce0cf6d9c	Adds support for `sso` endpoint override	2 years ago
Graham Davison	63fdeec004	Updates `aws-sdk-go-base` to `v2.0.0-beta.38`	2 years ago
Liam Cervante	ad77877136	terraform test: remove marks before passing variables as inputs to a plan (#34190) ... * remove marks before passing variables as inputs to a plan * fix doc comments	2 years ago
Liam Cervante	f90d71f723	testing framework: allow providers to reference run blocks (#34118) ... * testing framework: allow providers to reference run block * missing copywrite header	2 years ago
Graham Davison	aab15a9bce	Renames variables	3 years ago
Graham Davison	807fc3e6d0	Fixes error check	3 years ago
Graham Davison	142a73b513	Adds parameter `skip_s3_checksum` to skip checksum on upload	3 years ago
Liam Cervante	5bbdc4c3b6	terraform test: allow providers in test files to reference variables (#34069) ... * Process only relevant variables in the testing framework * add support for variables within test provider configurations * remove unused function * fix consistency checks	3 years ago
Liam Cervante	5294c2bb47	Process only relevant variables in the testing framework (#34072)	3 years ago
Jared Baker	95d56b567d	Merge pull request #33993 from andrewhertog/fix/s3-backend-kms-alias ... fix(s3): allow aliases for kms key	3 years ago
Jared Baker	a87a7eb404	backend/s3: use aws alias name regex pattern	3 years ago
Graham Davison	3de6dbc7a8	Keeps validation error for IMDS endpoint and replaces error with warning for other services	3 years ago
Jonas Wagner	09df2213f9	Add skip_requesting_account_id Parameter to S3 Backend ... Signed-off-by: Jonas Wagner <jwagner@knoppiks.de>	3 years ago
Andrew den Hertog	6088002a2d	fix(s3): allow aliases for kms key	3 years ago
Liam Cervante	01c0480e77	Test framework will produce regular updates in -json mode (#33953) ... * Test framework will produce regular updates in -json mode * add tests * docs * docs tweaking	3 years ago
Liam Cervante	fba5dad097	Test files should be marked as skipped if all their run blocks were skipped (#33950)	3 years ago
Graham Davison	5ad8c7cdcc	Updates checksum to work with multi-part upload	3 years ago
Graham Davison	f4e63ca2c1	Sets MD5 as required if S3 Object Locks are enabled	3 years ago
Graham Davison	567afc4ff0	Merge pull request #33899 from hashicorp/s3/f-assume-role-source-identity ... backend/s3: Adds `source_identity` to `assume_role` block	3 years ago
Jared Baker	c39b98df7b	backend/s3(test): add CoerceValue cases	3 years ago
Jared Baker	0bb8e4ca4e	backend/s3: set required or optional for single nested attribute	3 years ago
Graham Davison	30e24ed6a9	Merge pull request #33885 from hashicorp/s3/f-add-wrong-s3-region-error ... backend/s3: Add wrong bucket region handling to all of S3 client	3 years ago
Graham Davison	5396646ad8	Consolidates validators for assume role names	3 years ago
Graham Davison	ca8c26dcfd	Adds `source_identity` to `assume_role` biock	3 years ago
Liam Cervante	f8d4664bcd	Add additional validation around unknown and null values in test variables (#33861) ... * Add additional validation around unknown values in test variables * address comments	3 years ago
Liam Cervante	1c7dfa22b7	Add warning when testing and combining expect_failures with apply operations	3 years ago
Liam Cervante	84e2ebc225	apply defaults when processing variables for assertions	3 years ago
Graham Davison	9437c43540	Merge pull request #33872 from hashicorp/s3/f-schema-single-nested-object ... backend/s3: Adds `singleNestedAttribute` to internal schema	3 years ago