2024-02-08 03:48:59 -06:00
|
|
|
// Copyright (c) The OpenTofu Authors
|
|
|
|
// SPDX-License-Identifier: MPL-2.0
|
|
|
|
// Copyright (c) 2023 HashiCorp, Inc.
|
2023-05-02 10:33:06 -05:00
|
|
|
// SPDX-License-Identifier: MPL-2.0
|
|
|
|
|
2023-09-20 07:16:53 -05:00
|
|
|
package tofu
|
2018-05-03 22:41:46 -05:00
|
|
|
|
|
|
|
import (
|
2023-09-20 06:35:35 -05:00
|
|
|
"github.com/opentofu/opentofu/internal/addrs"
|
|
|
|
"github.com/opentofu/opentofu/internal/configs"
|
|
|
|
"github.com/opentofu/opentofu/internal/dag"
|
|
|
|
"github.com/opentofu/opentofu/internal/states"
|
|
|
|
"github.com/opentofu/opentofu/internal/tfdiags"
|
2018-05-03 22:41:46 -05:00
|
|
|
)
|
|
|
|
|
|
|
|
// EvalGraphBuilder implements GraphBuilder and constructs a graph suitable
|
|
|
|
// for evaluating in-memory values (input variables, local values, output
|
|
|
|
// values) in the state without any other side-effects.
|
|
|
|
//
|
2023-09-26 12:09:27 -05:00
|
|
|
// This graph is used only in weird cases, such as the "tofu console"
|
2018-05-03 22:41:46 -05:00
|
|
|
// CLI command, where we need to evaluate expressions against the state
|
|
|
|
// without taking any other actions.
|
|
|
|
//
|
|
|
|
// The generated graph will include nodes for providers, resources, etc
|
|
|
|
// just to allow indirect dependencies to be resolved, but these nodes will
|
|
|
|
// not take any actions themselves since we assume that their parts of the
|
|
|
|
// state, if any, are already complete.
|
|
|
|
//
|
|
|
|
// Although the providers are never configured, they must still be available
|
|
|
|
// in order to obtain schema information used for type checking, etc.
|
|
|
|
type EvalGraphBuilder struct {
|
|
|
|
// Config is the configuration tree.
|
|
|
|
Config *configs.Config
|
|
|
|
|
|
|
|
// State is the current state
|
terraform: Ugly huge change to weave in new State and Plan types
Due to how often the state and plan types are referenced throughout
Terraform, there isn't a great way to switch them out gradually. As a
consequence, this huge commit gets us from the old world to a _compilable_
new world, but still has a large number of known test failures due to
key functionality being stubbed out.
The stubs here are for anything that interacts with providers, since we
now need to do the follow-up work to similarly replace the old
terraform.ResourceProvider interface with its replacement in the new
"providers" package. That work, along with work to fix the remaining
failing tests, will follow in subsequent commits.
The aim here was to replace all references to terraform.State and its
downstream types with states.State, terraform.Plan with plans.Plan,
state.State with statemgr.State, and switch to the new implementations of
the state and plan file formats. However, due to the number of times those
types are used, this also ended up affecting numerous other parts of core
such as terraform.Hook, the backend.Backend interface, and most of the CLI
commands.
Just as with 5861dbf3fc49b19587a31816eb06f511ab861bb4 before, I apologize
in advance to the person who inevitably just found this huge commit while
spelunking through the commit history.
2018-08-14 16:24:45 -05:00
|
|
|
State *states.State
|
2018-05-03 22:41:46 -05:00
|
|
|
|
core: Handle root and child module input variables consistently
Previously we had a significant discrepancy between these two situations:
we wrote the raw root module variables directly into the EvalContext and
then applied type conversions only at expression evaluation time, while
for child modules we converted and validated the values while visiting
the variable graph node and wrote only the _final_ value into the
EvalContext.
This confusion seems to have been the root cause for #29899, where
validation rules for root module variables were being applied at the wrong
point in the process, prior to type conversion.
To fix that bug and also make similar mistakes less likely in the future,
I've made the root module variable handling more like the child module
variable handling in the following ways:
- The "raw value" (exactly as given by the user) lives only in the graph
node representing the variable, which mirrors how the _expression_
for a child module variable lives in its graph node. This means that
the flow for the two is the same except that there's no expression
evaluation step for root module variables, because they arrive as
constant values from the caller.
- The set of variable values in the EvalContext is always only "final"
values, after type conversion is complete. That in turn means we no
longer need to do "just in time" conversion in
evaluationStateData.GetInputVariable, and can just return the value
exactly as stored, which is consistent with how we handle all other
references between objects.
This diff is noisier than I'd like because of how much it takes to wire
a new argument (the raw variable values) through to the plan graph builder,
but those changes are pretty mechanical and the interesting logic lives
inside the plan graph builder itself, in NodeRootVariable, and
the shared helper functions in eval_variable.go.
While here I also took the opportunity to fix a historical API wart in
EvalContext, where SetModuleCallArguments was built to take a set of
variable values all at once but our current caller always calls with only
one at a time. That is now just SetModuleCallArgument singular, to match
with the new SetRootModuleArgument to deal with root module variables.
2021-11-10 19:29:45 -06:00
|
|
|
// RootVariableValues are the raw input values for root input variables
|
|
|
|
// given by the caller, which we'll resolve into final values as part
|
|
|
|
// of the plan walk.
|
|
|
|
RootVariableValues InputValues
|
|
|
|
|
2021-08-31 12:58:05 -05:00
|
|
|
// Plugins is a library of plug-in components (providers and
|
2018-05-03 22:41:46 -05:00
|
|
|
// provisioners) available for use.
|
2021-08-31 12:58:05 -05:00
|
|
|
Plugins *contextPlugins
|
2018-05-03 22:41:46 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
// See GraphBuilder
|
|
|
|
func (b *EvalGraphBuilder) Build(path addrs.ModuleInstance) (*Graph, tfdiags.Diagnostics) {
|
|
|
|
return (&BasicGraphBuilder{
|
2022-03-11 08:31:24 -06:00
|
|
|
Steps: b.Steps(),
|
|
|
|
Name: "EvalGraphBuilder",
|
2018-05-03 22:41:46 -05:00
|
|
|
}).Build(path)
|
|
|
|
}
|
|
|
|
|
|
|
|
// See GraphBuilder
|
|
|
|
func (b *EvalGraphBuilder) Steps() []GraphTransformer {
|
|
|
|
concreteProvider := func(a *NodeAbstractProvider) dag.Vertex {
|
|
|
|
return &NodeEvalableProvider{
|
|
|
|
NodeAbstractProvider: a,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
steps := []GraphTransformer{
|
|
|
|
// Creates all the data resources that aren't in the state. This will also
|
|
|
|
// add any orphans from scaling in as destroy nodes.
|
|
|
|
&ConfigTransformer{
|
2020-10-06 16:39:53 -05:00
|
|
|
Config: b.Config,
|
2018-05-03 22:41:46 -05:00
|
|
|
},
|
|
|
|
|
2020-10-06 16:39:53 -05:00
|
|
|
// Add dynamic values
|
2023-11-08 17:07:09 -06:00
|
|
|
&RootVariableTransformer{Config: b.Config, RawValues: b.RootVariableValues},
|
|
|
|
&ModuleVariableTransformer{Config: b.Config},
|
2018-05-03 22:41:46 -05:00
|
|
|
&LocalTransformer{Config: b.Config},
|
2022-10-19 15:11:35 -05:00
|
|
|
&OutputTransformer{
|
|
|
|
Config: b.Config,
|
|
|
|
Planning: true,
|
|
|
|
},
|
2018-05-03 22:41:46 -05:00
|
|
|
|
2020-10-06 16:39:53 -05:00
|
|
|
// Attach the configuration to any resources
|
|
|
|
&AttachResourceConfigTransformer{Config: b.Config},
|
|
|
|
|
|
|
|
// Attach the state
|
|
|
|
&AttachStateTransformer{State: b.State},
|
2018-05-03 22:41:46 -05:00
|
|
|
|
2021-08-31 12:16:44 -05:00
|
|
|
transformProviders(concreteProvider, b.Config),
|
2018-05-31 15:00:17 -05:00
|
|
|
|
2018-06-01 15:00:52 -05:00
|
|
|
// Must attach schemas before ReferenceTransformer so that we can
|
|
|
|
// analyze the configuration to find references.
|
2021-08-31 18:36:27 -05:00
|
|
|
&AttachSchemaTransformer{Plugins: b.Plugins, Config: b.Config},
|
2018-05-31 15:00:17 -05:00
|
|
|
|
2024-04-18 08:11:38 -05:00
|
|
|
// After schema transformer, we can add function references
|
|
|
|
&ProviderFunctionTransformer{Config: b.Config},
|
|
|
|
|
|
|
|
// Remove unused providers and proxies
|
|
|
|
&PruneProviderTransformer{},
|
|
|
|
|
2020-04-27 12:09:08 -05:00
|
|
|
// Create expansion nodes for all of the module calls. This must
|
|
|
|
// come after all other transformers that create nodes representing
|
|
|
|
// objects that can belong to modules.
|
2020-10-06 16:39:53 -05:00
|
|
|
&ModuleExpansionTransformer{Config: b.Config},
|
2020-04-27 12:09:08 -05:00
|
|
|
|
2018-05-03 22:41:46 -05:00
|
|
|
// Connect so that the references are ready for targeting. We'll
|
|
|
|
// have to connect again later for providers and so on.
|
|
|
|
&ReferenceTransformer{},
|
|
|
|
|
|
|
|
// Although we don't configure providers, we do still start them up
|
|
|
|
// to get their schemas, and so we must shut them down again here.
|
|
|
|
&CloseProviderTransformer{},
|
|
|
|
|
2020-04-02 14:49:32 -05:00
|
|
|
// Close root module
|
2024-06-06 05:20:41 -05:00
|
|
|
&CloseRootModuleTransformer{
|
|
|
|
RootConfig: b.Config,
|
|
|
|
},
|
2018-05-03 22:41:46 -05:00
|
|
|
|
|
|
|
// Remove redundant edges to simplify the graph.
|
|
|
|
&TransitiveReductionTransformer{},
|
|
|
|
}
|
|
|
|
|
|
|
|
return steps
|
|
|
|
}
|