core: Functional-style API for terraform.Context
Previously terraform.Context was built in an unfortunate way where all of
the data was provided up front in terraform.NewContext and then mutated
directly by subsequent operations. That made the data flow hard to follow,
commonly leading to bugs, and also meant that we were forced to take
various actions too early in terraform.NewContext, rather than waiting
until a more appropriate time during an operation.
This (enormous) commit changes terraform.Context so that its fields are
broadly just unchanging data about the execution context (current
workspace name, available plugins, etc) whereas the main data Terraform
works with arrives via individual method arguments and is returned in
return values.
Specifically, this means that terraform.Context no longer "has-a" config,
state, and "planned changes", instead holding on to those only temporarily
during an operation. The caller is responsible for propagating the outcome
of one step into the next step so that the data flow between operations is
actually visible.
However, since that's a change to the main entry points in the "terraform"
package, this commit also touches every file in the codebase which
interacted with those APIs. Most of the noise here is in updating tests
to take the same actions using the new API style, but this also affects
the main-code callers in the backends and in the command package.
My goal here was to refactor without changing observable behavior, but in
practice there are a couple externally-visible behavior variations here
that seemed okay in service of the broader goal:
- The "terraform graph" command is no longer hooked directly into the
core graph builders, because that's no longer part of the public API.
However, I did include a couple new Context functions whose contract
is to produce a UI-oriented graph, and _for now_ those continue to
return the physical graph we use for those operations. There's no
exported API for generating the "validate" and "eval" graphs, because
neither is particularly interesting in its own right, and so
"terraform graph" no longer supports those graph types.
- terraform.NewContext no longer has the responsibility for collecting
all of the provider schemas up front. Instead, we wait until we need
them. However, that means that some of our error messages now have a
slightly different shape due to unwinding through a differently-shaped
call stack. As of this commit we also end up reloading the schemas
multiple times in some cases, which is functionally acceptable but
likely represents a performance regression. I intend to rework this to
use caching, but I'm saving that for a later commit because this one is
big enough already.
The proximal reason for this change is to resolve the chicken/egg problem
whereby there was previously no single point where we could apply "moved"
statements to the previous run state before creating a plan. With this
change in place, we can now do that as part of Context.Plan, prior to
forking the input state into the three separate state artifacts we use
during planning.
However, this is at least the third project in a row where the previous
API design led to piling more functionality into terraform.NewContext and
then working around the incorrect order of operations that produces, so
I intend that by paying the cost/risk of this large diff now we can in
turn reduce the cost/risk of future projects that relate to our main
workflow actions.
2021-08-24 14:06:38 -05:00
|
|
|
package terraform
|
|
|
|
|
|
|
|
import (
|
|
|
|
"log"
|
|
|
|
|
|
|
|
"github.com/hashicorp/terraform/internal/addrs"
|
|
|
|
"github.com/hashicorp/terraform/internal/configs"
|
|
|
|
"github.com/hashicorp/terraform/internal/states"
|
|
|
|
"github.com/hashicorp/terraform/internal/tfdiags"
|
|
|
|
"github.com/zclconf/go-cty/cty"
|
|
|
|
)
|
|
|
|
|
|
|
|
// Validate performs semantic validation of a configuration, and returns
|
|
|
|
// any warnings or errors.
|
|
|
|
//
|
|
|
|
// Syntax and structural checks are performed by the configuration loader,
|
|
|
|
// and so are not repeated here.
|
|
|
|
//
|
|
|
|
// Validate considers only the configuration and so it won't catch any
|
|
|
|
// errors caused by current values in the state, or other external information
|
|
|
|
// such as root module input variables. However, the Plan function includes
|
|
|
|
// all of the same checks as Validate, in addition to the other work it does
|
|
|
|
// to consider the previous run state and the planning options.
|
|
|
|
func (c *Context) Validate(config *configs.Config) tfdiags.Diagnostics {
|
|
|
|
defer c.acquireRun("validate")()
|
|
|
|
|
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
|
|
|
|
moreDiags := CheckCoreVersionRequirements(config)
|
|
|
|
diags = diags.Append(moreDiags)
|
|
|
|
// If version constraints are not met then we'll bail early since otherwise
|
|
|
|
// we're likely to just see a bunch of other errors related to
|
|
|
|
// incompatibilities, which could be overwhelming for the user.
|
|
|
|
if diags.HasErrors() {
|
|
|
|
return diags
|
|
|
|
}
|
|
|
|
|
|
|
|
log.Printf("[DEBUG] Building and walking validate graph")
|
|
|
|
|
|
|
|
graph, moreDiags := ValidateGraphBuilder(&PlanGraphBuilder{
|
2021-08-31 12:58:05 -05:00
|
|
|
Config: config,
|
|
|
|
Plugins: c.plugins,
|
|
|
|
Validate: true,
|
|
|
|
State: states.NewState(),
|
core: Functional-style API for terraform.Context
Previously terraform.Context was built in an unfortunate way where all of
the data was provided up front in terraform.NewContext and then mutated
directly by subsequent operations. That made the data flow hard to follow,
commonly leading to bugs, and also meant that we were forced to take
various actions too early in terraform.NewContext, rather than waiting
until a more appropriate time during an operation.
This (enormous) commit changes terraform.Context so that its fields are
broadly just unchanging data about the execution context (current
workspace name, available plugins, etc) whereas the main data Terraform
works with arrives via individual method arguments and is returned in
return values.
Specifically, this means that terraform.Context no longer "has-a" config,
state, and "planned changes", instead holding on to those only temporarily
during an operation. The caller is responsible for propagating the outcome
of one step into the next step so that the data flow between operations is
actually visible.
However, since that's a change to the main entry points in the "terraform"
package, this commit also touches every file in the codebase which
interacted with those APIs. Most of the noise here is in updating tests
to take the same actions using the new API style, but this also affects
the main-code callers in the backends and in the command package.
My goal here was to refactor without changing observable behavior, but in
practice there are a couple externally-visible behavior variations here
that seemed okay in service of the broader goal:
- The "terraform graph" command is no longer hooked directly into the
core graph builders, because that's no longer part of the public API.
However, I did include a couple new Context functions whose contract
is to produce a UI-oriented graph, and _for now_ those continue to
return the physical graph we use for those operations. There's no
exported API for generating the "validate" and "eval" graphs, because
neither is particularly interesting in its own right, and so
"terraform graph" no longer supports those graph types.
- terraform.NewContext no longer has the responsibility for collecting
all of the provider schemas up front. Instead, we wait until we need
them. However, that means that some of our error messages now have a
slightly different shape due to unwinding through a differently-shaped
call stack. As of this commit we also end up reloading the schemas
multiple times in some cases, which is functionally acceptable but
likely represents a performance regression. I intend to rework this to
use caching, but I'm saving that for a later commit because this one is
big enough already.
The proximal reason for this change is to resolve the chicken/egg problem
whereby there was previously no single point where we could apply "moved"
statements to the previous run state before creating a plan. With this
change in place, we can now do that as part of Context.Plan, prior to
forking the input state into the three separate state artifacts we use
during planning.
However, this is at least the third project in a row where the previous
API design led to piling more functionality into terraform.NewContext and
then working around the incorrect order of operations that produces, so
I intend that by paying the cost/risk of this large diff now we can in
turn reduce the cost/risk of future projects that relate to our main
workflow actions.
2021-08-24 14:06:38 -05:00
|
|
|
}).Build(addrs.RootModuleInstance)
|
|
|
|
diags = diags.Append(moreDiags)
|
|
|
|
if moreDiags.HasErrors() {
|
|
|
|
return diags
|
|
|
|
}
|
|
|
|
|
|
|
|
// Validate is to check if the given module is valid regardless of
|
|
|
|
// input values, current state, etc. Therefore we populate all of the
|
|
|
|
// input values with unknown values of the expected type, allowing us
|
|
|
|
// to perform a type check without assuming any particular values.
|
|
|
|
varValues := make(InputValues)
|
|
|
|
for name, variable := range config.Module.Variables {
|
|
|
|
ty := variable.Type
|
|
|
|
if ty == cty.NilType {
|
|
|
|
// Can't predict the type at all, so we'll just mark it as
|
|
|
|
// cty.DynamicVal (unknown value of cty.DynamicPseudoType).
|
|
|
|
ty = cty.DynamicPseudoType
|
|
|
|
}
|
|
|
|
varValues[name] = &InputValue{
|
|
|
|
Value: cty.UnknownVal(ty),
|
|
|
|
SourceType: ValueFromUnknown,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
walker, walkDiags := c.walk(graph, walkValidate, &graphWalkOpts{
|
|
|
|
Config: config,
|
|
|
|
RootVariableValues: varValues,
|
|
|
|
})
|
|
|
|
diags = diags.Append(walker.NonFatalDiagnostics)
|
|
|
|
diags = diags.Append(walkDiags)
|
|
|
|
if walkDiags.HasErrors() {
|
|
|
|
return diags
|
|
|
|
}
|
|
|
|
|
|
|
|
return diags
|
|
|
|
}
|