terraform

Commit Graph

Author	SHA1	Message	Date
Daniel Schmidt	b701e152e5	show value is ephemeral in terraform test	2 years ago
Daniel Schmidt	3e7fdd0de9	improve wording of error message	2 years ago
Daniel Schmidt	ae103fc491	test: emit a nice error message if the user uses ephemeral resource in terrafom test	2 years ago
Daniel Schmidt	97ba67edea	test: ensure ephemeral values are not shown in diagnostics and warning is printed	2 years ago
Daniel Schmidt	725add6a1a	test: pass in variables during apply ephemeral variables need to be re-supplied	2 years ago
MicahKimel	3258744166	Remove invalid warning during cleanup phase (#35172 ) * stop invalid warning during cleanup phase * stop invalid warning during cleanup phase * invalid warning during cleanup phase * remove unwanted comment * update GetVariables parameter for including warnings * invalid warning during cleanup phase test case * update invalid warnings in cleanup test case to throw a warning for the validation variable before cleanup phase * remove unwanted warnings	2 years ago
Liam Cervante	448775102c	terraform test: Push evaluation of variables to as late as possible (#35014 ) * terraform test: Push evaluation of variables to as late as possible * Update internal/moduletest/hcl/variable_cache.go Co-authored-by: kmoe <5575356+kmoe@users.noreply.github.com> * address comments --------- Co-authored-by: kmoe <5575356+kmoe@users.noreply.github.com>	2 years ago
Liam Cervante	6963c54bec	terraform test: don't remove sensitive marks from inputs (#35021 )	2 years ago
UKEME BASSEY	0ea25e3b40	fixing tests internal/command/init, view and argumento	2 years ago
UKEME BASSEY	370a471ecb	fix json -help display and failing tests	2 years ago
Martin Atkins	14b08c3745	terraform: Move variable validation into its separate node type The parent commit added a new node to the graph for each existing input variable node, but that node didn't do anything yet. Now those new nodes are actually responsible for checking the variable's validation rules, instead of that being included in the same graph node that decides the variable's final value. This also refines the validation node graph transformer to only insert a validation node if there's at least one rule to check, which should avoid bloating the graph for anyone who isn't actually using input variable validation. Therefore the plan graph builder tests revert back to their old expected result because that input configuration does not include any validation rules. For the moment this just moves around functionality that already existed and doesn't add anything new, but having the validation handled in a separate graph node means that we can evaluate the validation rules in the EvalContext of the module where the variable was declared instead of where it was defined, and so a future commit will allow -- initially just as an experiment -- validation rules that can refer to other objects in the module where the variable is declared, including the values of other input variables. As a nice bonus, this fixed a small bug in "terraform test" where problems with variable values defined in the test run were reported as problems with the variable declaration, rather than with the expression assigning the value to it. Since it's now NodeRootVariable that decides the definition source range, rather than the validation-rule-checking helper, it has access to the source range provided in a terraform.InputValue object, which was already populated correctly for per-test-run definitions.	2 years ago
Liam Cervante	c6ff573180	Include provider functions in scope used to evaluate test assertions (#34825 )	2 years ago
Daniel Schmidt	7ae7a203d8	test: allow using global variables in suite-level variable definitions Closes #34534	2 years ago
Liam Cervante	9658f9df6b	mocking overrides: default to concrete empty object when values are missing (#34563 )	2 years ago
Liam Cervante	430970c02b	terraform test: Fix crash when file level variables reference variables. (#34531 ) * terraform test: Fix crash when referencing variables within the file level variable block * also allow functions within variables blocks * add tests	2 years ago
Liam Cervante	7e18b1183d	Add test verifying issue #34476 has been fixed (#34478 )	2 years ago
Jamie Finnigan	05b0bdac99	adopt hashicorp/cli fork of mitchellh/cli (#34429 )	2 years ago
Liam Cervante	5cbf7c5f96	Add docs for automatic var files in test directories (#34349 )	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
Liam Cervante	9ea1aa0a86	terraform test: skip destroy step for empty run blocks (#34331 )	2 years ago
Liam Cervante	392e2a6e21	Fix the compile error in command/test_test.go (#34324 )	2 years ago
Liam Cervante	6670ab43f7	terraform test: rearrange the order of destroy operations (#34293 )	2 years ago
Liam Cervante	08eafe0f2e	Fix flaky test in command/test_test.go (#34320 )	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
Liam Cervante	b9f6b23ba3	testing framework: add support for functions in variables and providers (#34204 )	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
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
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
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
Liam Cervante	041b54fb4b	explicitely disallow duplicate run block names in test files (#33836 )	3 years ago
Liam Cervante	a560730376	Make the test command fail if resources could not be cleaned up (#33809 ) * Make the test command fail if resources could not be cleaned up * remove redundant return statement	3 years ago
Liam Cervante	91d26b6ea6	Refactor file and run block feedback frequency (#33840 ) * Refactor file and run block feedback frequency * fix consistency checks * make generate	3 years ago
Liam Cervante	802d49a9ca	Handle null outputs in Terraform test files (#33781 )	3 years ago
Liam Cervante	4c83e2d524	Terraform test directory must be local to the config directory (#33760 )	3 years ago
Liam Cervante	5e63aa01c7	Allow referencing higher level variables from run blocks (#33722 )	3 years ago
CJ Horton	98b81d3c50	add missing copyright headers	3 years ago
Liam Cervante	9742f22c4e	Introduce 'run' keyword for referencing outputs from earlier run blocks (#33683 ) * introduce 'run' keyword for referencing outputs from earlier run blocks * fix code consistency	3 years ago
Liam Cervante	126f34e4e8	Implement updates to testing framework based on recent feedback	3 years ago
Liam Cervante	3bea1171af	test framework: expand variables available to test assertions (#33611 )	3 years ago
Liam Cervante	4560a83721	test framework: include transformed config before validating config (#33608 )	3 years ago
Liam Cervante	f397954c52	testing framework: allow users to specify deeply nested testing directories (#33584 )	3 years ago
Liam Cervante	4122ba86fc	terraform test: fix crash when using nested modules from test run blocks (#33589 )	3 years ago
Liam Cervante	e1019b3641	testing framework: validate the configuration before terraform test (#33559 ) * testing framework: call validate on the configuration before running terraform test * address comments * make tests pass after merge * fix tests	3 years ago

1 2

66 Commits (ca35e204eef230ce75d43cb7db358a063e20fc92)