2016-09-13 12:56:37 -05:00
|
|
|
package terraform
|
|
|
|
|
|
|
|
import (
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 12:33:53 -05:00
|
|
|
"github.com/hashicorp/terraform/addrs"
|
|
|
|
"github.com/hashicorp/terraform/configs"
|
2016-09-21 16:30:41 -05:00
|
|
|
"github.com/hashicorp/terraform/dag"
|
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
|
|
|
"github.com/hashicorp/terraform/plans"
|
|
|
|
"github.com/hashicorp/terraform/states"
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 12:33:53 -05:00
|
|
|
"github.com/hashicorp/terraform/tfdiags"
|
2016-09-13 12:56:37 -05:00
|
|
|
)
|
|
|
|
|
|
|
|
// ApplyGraphBuilder implements GraphBuilder and is responsible for building
|
|
|
|
// a graph for applying a Terraform diff.
|
|
|
|
//
|
|
|
|
// Because the graph is built from the diff (vs. the config or state),
|
|
|
|
// this helps ensure that the apply-time graph doesn't modify any resources
|
|
|
|
// that aren't explicitly in the diff. There are other scenarios where the
|
|
|
|
// diff can be deviated, so this is just one layer of protection.
|
|
|
|
type ApplyGraphBuilder struct {
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 12:33:53 -05:00
|
|
|
// Config is the configuration tree that the diff was built from.
|
|
|
|
Config *configs.Config
|
2016-09-13 12:56:37 -05:00
|
|
|
|
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
|
|
|
// Changes describes the changes that we need apply.
|
|
|
|
Changes *plans.Changes
|
2016-09-13 12:56:37 -05:00
|
|
|
|
2016-09-13 19:52:09 -05:00
|
|
|
// 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
|
2016-09-13 19:52:09 -05:00
|
|
|
|
2018-05-02 22:16:22 -05:00
|
|
|
// Components is a factory for the plug-in components (providers and
|
|
|
|
// provisioners) available for use.
|
|
|
|
Components contextComponentFactory
|
2016-09-22 13:03:03 -05:00
|
|
|
|
2018-05-31 14:39:45 -05:00
|
|
|
// Schemas is the repository of schemas we will draw from to analyse
|
|
|
|
// the configuration.
|
|
|
|
Schemas *Schemas
|
|
|
|
|
2017-02-13 14:52:45 -06:00
|
|
|
// Targets are resources to target. This is only required to make sure
|
|
|
|
// unnecessary outputs aren't included in the apply graph. The plan
|
|
|
|
// builder successfully handles targeting resources. In the future,
|
|
|
|
// outputs should go into the diff so that this is unnecessary.
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 12:33:53 -05:00
|
|
|
Targets []addrs.Targetable
|
2017-02-13 14:52:45 -06:00
|
|
|
|
2016-12-02 21:38:49 -06:00
|
|
|
// Validate will do structural validation of the graph.
|
|
|
|
Validate bool
|
2016-09-13 12:56:37 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
// See GraphBuilder
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 12:33:53 -05:00
|
|
|
func (b *ApplyGraphBuilder) Build(path addrs.ModuleInstance) (*Graph, tfdiags.Diagnostics) {
|
2016-09-13 12:56:37 -05:00
|
|
|
return (&BasicGraphBuilder{
|
|
|
|
Steps: b.Steps(),
|
2016-12-02 21:38:49 -06:00
|
|
|
Validate: b.Validate,
|
2016-11-15 15:36:10 -06:00
|
|
|
Name: "ApplyGraphBuilder",
|
2016-09-13 12:56:37 -05:00
|
|
|
}).Build(path)
|
|
|
|
}
|
|
|
|
|
|
|
|
// See GraphBuilder
|
|
|
|
func (b *ApplyGraphBuilder) Steps() []GraphTransformer {
|
2016-09-15 01:58:16 -05:00
|
|
|
// Custom factory for creating providers.
|
2016-12-03 17:27:38 -06:00
|
|
|
concreteProvider := func(a *NodeAbstractProvider) dag.Vertex {
|
2016-09-15 01:58:16 -05:00
|
|
|
return &NodeApplyableProvider{
|
2016-12-03 17:27:38 -06:00
|
|
|
NodeAbstractProvider: a,
|
2016-09-15 01:58:16 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-09-11 16:22:25 -05:00
|
|
|
concreteResource := func(a *NodeAbstractResource) dag.Vertex {
|
2020-03-20 14:45:39 -05:00
|
|
|
return &nodeExpandApplyableResource{
|
2018-09-11 16:22:25 -05:00
|
|
|
NodeAbstractResource: a,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
concreteResourceInstance := func(a *NodeAbstractResourceInstance) dag.Vertex {
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 12:33:53 -05:00
|
|
|
return &NodeApplyableResourceInstance{
|
|
|
|
NodeAbstractResourceInstance: a,
|
2016-09-21 16:30:41 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-09-13 12:56:37 -05:00
|
|
|
steps := []GraphTransformer{
|
2018-09-11 16:22:25 -05:00
|
|
|
// Creates all the resources represented in the config. During apply,
|
|
|
|
// we use this just to ensure that the whole-resource metadata is
|
|
|
|
// updated to reflect things such as whether the count argument is
|
|
|
|
// set in config, or which provider configuration manages each resource.
|
|
|
|
&ConfigTransformer{
|
2016-09-21 16:30:41 -05:00
|
|
|
Concrete: concreteResource,
|
2018-09-11 16:22:25 -05:00
|
|
|
Config: b.Config,
|
|
|
|
},
|
|
|
|
|
2020-10-06 16:39:53 -05:00
|
|
|
// Add dynamic values
|
|
|
|
&RootVariableTransformer{Config: b.Config},
|
|
|
|
&ModuleVariableTransformer{Config: b.Config},
|
|
|
|
&LocalTransformer{Config: b.Config},
|
2020-10-09 10:09:36 -05:00
|
|
|
&OutputTransformer{Config: b.Config, Changes: b.Changes},
|
2020-10-06 16:39:53 -05:00
|
|
|
|
2018-09-11 16:22:25 -05:00
|
|
|
// Creates all the resource instances represented in the diff, along
|
|
|
|
// with dependency edges against the whole-resource nodes added by
|
|
|
|
// ConfigTransformer above.
|
|
|
|
&DiffTransformer{
|
|
|
|
Concrete: concreteResourceInstance,
|
2018-09-20 14:30:52 -05:00
|
|
|
State: b.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
|
|
|
Changes: b.Changes,
|
2016-09-13 19:52:09 -05:00
|
|
|
},
|
2016-09-13 16:34:15 -05:00
|
|
|
|
2020-10-06 16:39:53 -05:00
|
|
|
// Attach the state
|
|
|
|
&AttachStateTransformer{State: b.State},
|
|
|
|
|
2016-09-18 23:45:19 -05:00
|
|
|
// Create orphan output nodes
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 12:33:53 -05:00
|
|
|
&OrphanOutputTransformer{Config: b.Config, State: b.State},
|
2016-09-18 23:45:19 -05:00
|
|
|
|
2016-09-20 12:23:48 -05:00
|
|
|
// Attach the configuration to any resources
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 12:33:53 -05:00
|
|
|
&AttachResourceConfigTransformer{Config: b.Config},
|
2016-09-20 12:23:48 -05:00
|
|
|
|
2016-09-15 11:32:37 -05:00
|
|
|
// Provisioner-related transformations
|
2018-05-02 22:16:22 -05:00
|
|
|
&MissingProvisionerTransformer{Provisioners: b.Components.ResourceProvisioners()},
|
2017-01-20 20:07:51 -06:00
|
|
|
&ProvisionerTransformer{},
|
2016-09-15 11:32:37 -05:00
|
|
|
|
2018-05-25 18:27:11 -05:00
|
|
|
// add providers
|
|
|
|
TransformProviders(b.Components.ResourceProviders(), concreteProvider, b.Config),
|
|
|
|
|
2017-11-09 09:34:56 -06:00
|
|
|
// Remove modules no longer present in the config
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 12:33:53 -05:00
|
|
|
&RemovedModuleTransformer{Config: b.Config, State: b.State},
|
2017-11-09 09:34:56 -06:00
|
|
|
|
2018-06-01 15:00:52 -05:00
|
|
|
// Must attach schemas before ReferenceTransformer so that we can
|
|
|
|
// analyze the configuration to find references.
|
2020-03-10 13:43:57 -05:00
|
|
|
&AttachSchemaTransformer{Schemas: b.Schemas, Config: b.Config},
|
2018-06-01 15:00:52 -05:00
|
|
|
|
2019-11-21 20:45:43 -06: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.
|
|
|
|
&ModuleExpansionTransformer{Config: b.Config},
|
|
|
|
|
2016-09-15 20:30:11 -05:00
|
|
|
// Connect references so ordering is correct
|
|
|
|
&ReferenceTransformer{},
|
2019-10-17 15:05:27 -05:00
|
|
|
&AttachDependenciesTransformer{},
|
2016-09-15 20:30:11 -05:00
|
|
|
|
2020-05-14 13:08:33 -05:00
|
|
|
// Detect when create_before_destroy must be forced on for a particular
|
|
|
|
// node due to dependency edges, to avoid graph cycles during apply.
|
|
|
|
&ForcedCBDTransformer{},
|
|
|
|
|
2019-09-25 12:20:24 -05:00
|
|
|
// Destruction ordering
|
|
|
|
&DestroyEdgeTransformer{
|
|
|
|
Config: b.Config,
|
|
|
|
State: b.State,
|
|
|
|
Schemas: b.Schemas,
|
|
|
|
},
|
2019-09-26 11:36:44 -05:00
|
|
|
&CBDEdgeTransformer{
|
|
|
|
Config: b.Config,
|
|
|
|
State: b.State,
|
|
|
|
Schemas: b.Schemas,
|
|
|
|
},
|
2019-09-25 12:20:24 -05:00
|
|
|
|
2020-05-20 12:45:31 -05:00
|
|
|
// We need to remove configuration nodes that are not used at all, as
|
|
|
|
// they may not be able to evaluate, especially during destroy.
|
|
|
|
// These include variables, locals, and instance expanders.
|
|
|
|
&pruneUnusedNodesTransformer{},
|
2019-12-18 13:37:28 -06:00
|
|
|
|
2020-06-23 16:22:44 -05:00
|
|
|
// Target
|
|
|
|
&TargetsTransformer{Targets: b.Targets},
|
|
|
|
|
2016-09-19 11:28:24 -05:00
|
|
|
// Add the node to fix the state count boundaries
|
2018-08-27 14:03:20 -05:00
|
|
|
&CountBoundaryTransformer{
|
|
|
|
Config: b.Config,
|
|
|
|
},
|
2016-09-19 11:28:24 -05:00
|
|
|
|
2017-04-12 16:25:15 -05:00
|
|
|
// Close opened plugin connections
|
|
|
|
&CloseProviderTransformer{},
|
|
|
|
&CloseProvisionerTransformer{},
|
|
|
|
|
2020-04-02 14:49:32 -05:00
|
|
|
// close the root module
|
|
|
|
&CloseRootModuleTransformer{},
|
2016-09-19 11:28:24 -05:00
|
|
|
|
|
|
|
// Perform the transitive reduction to make our graph a bit
|
2020-10-18 11:56:51 -05:00
|
|
|
// more understandable if possible (it usually is possible).
|
2020-08-14 13:13:33 -05:00
|
|
|
&TransitiveReductionTransformer{},
|
2016-09-13 12:56:37 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
return steps
|
|
|
|
}
|