IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2024-12-25 08:21:07 -06:00
Code Issues Packages Projects Releases Wiki Activity
838a42d218
opentofu/terraform/graph_builder_plan_test.go

134 lines
3.2 KiB
Go
Raw Normal View History

terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
package terraform
import (
"strings"
"testing"
core: Get tests compiling again After the refactoring to integrate HCL2 many of the tests were no longer using correct types, attribute names, etc. This is a bulk update of all of the tests to make them compile again, with minimal changes otherwise. Although the tests now compile, many of them do not yet pass. The tests will be gradually repaired in subsequent commits, as we continue to complete the refactoring and retrofit work.
2018-05-04 21:24:06 -05:00
"github.com/hashicorp/terraform/addrs"
core: Fix various compile-time errors in tests Significant changes to the provider interface left a lot of the tests in a non-buildable state. This set of changes gets the tests building again but does not attempt to make them run to completion or pass. After this commit, it is possible to build a test program for the ./terraform package but it will panic during its run. That will be addressed in subsequent commits.
2018-09-05 16:35:30 -05:00
"github.com/hashicorp/terraform/configs/configschema"
replace provider and provisioner types in tests The field assignments and methods are incorrect still, but the type definitions and returns are now updated.
2018-08-17 14:32:35 -05:00
"github.com/hashicorp/terraform/providers"
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
)
func TestPlanGraphBuilder_impl(t *testing.T) {
var _ GraphBuilder = new(PlanGraphBuilder)
}
func TestPlanGraphBuilder(t *testing.T) {
replace provider and provisioner types in tests The field assignments and methods are incorrect still, but the type definitions and returns are now updated.
2018-08-17 14:32:35 -05:00
awsProvider := &MockProvider{
core: Fix various compile-time errors in tests Significant changes to the provider interface left a lot of the tests in a non-buildable state. This set of changes gets the tests building again but does not attempt to make them run to completion or pass. After this commit, it is possible to build a test program for the ./terraform package but it will panic during its run. That will be addressed in subsequent commits.
2018-09-05 16:35:30 -05:00
GetSchemaReturn: &ProviderSchema{
Provider: simpleTestSchema(),
ResourceTypes: map[string]*configschema.Block{
"aws_security_group": simpleTestSchema(),
"aws_instance": simpleTestSchema(),
"aws_load_balancer": simpleTestSchema(),
core: Fetch schemas during context construction Previously we fetched schemas during the AttachSchemaTransformer, potentially multiple times as that was re-run for each graph built. Now we fetch the schemas just once during context construction, passing that result into each of the graph builders. This only addresses the schema accesses during graph construction. We're still separately loading schemas during the main walk for evaluation purposes. This will be addressed in a later commit.
2018-05-31 14:39:45 -05:00
},
},
}
replace provider and provisioner types in tests The field assignments and methods are incorrect still, but the type definitions and returns are now updated.
2018-08-17 14:32:35 -05:00
openstackProvider := &MockProvider{
core: Fix various compile-time errors in tests Significant changes to the provider interface left a lot of the tests in a non-buildable state. This set of changes gets the tests building again but does not attempt to make them run to completion or pass. After this commit, it is possible to build a test program for the ./terraform package but it will panic during its run. That will be addressed in subsequent commits.
2018-09-05 16:35:30 -05:00
GetSchemaReturn: &ProviderSchema{
Provider: simpleTestSchema(),
ResourceTypes: map[string]*configschema.Block{
"openstack_floating_ip": simpleTestSchema(),
core: Fetch schemas during context construction Previously we fetched schemas during the AttachSchemaTransformer, potentially multiple times as that was re-run for each graph built. Now we fetch the schemas just once during context construction, passing that result into each of the graph builders. This only addresses the schema accesses during graph construction. We're still separately loading schemas during the main walk for evaluation purposes. This will be addressed in a later commit.
2018-05-31 14:39:45 -05:00
},
},
}
components := &basicComponentFactory{
replace provider and provisioner types in tests The field assignments and methods are incorrect still, but the type definitions and returns are now updated.
2018-08-17 14:32:35 -05:00
providers: map[string]providers.Factory{
"aws": providers.FactoryFixed(awsProvider),
"openstack": providers.FactoryFixed(openstackProvider),
core: Fetch schemas during context construction Previously we fetched schemas during the AttachSchemaTransformer, potentially multiple times as that was re-run for each graph built. Now we fetch the schemas just once during context construction, passing that result into each of the graph builders. This only addresses the schema accesses during graph construction. We're still separately loading schemas during the main walk for evaluation purposes. This will be addressed in a later commit.
2018-05-31 14:39:45 -05:00
},
}
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
b := &PlanGraphBuilder{
core: Fetch schemas during context construction Previously we fetched schemas during the AttachSchemaTransformer, potentially multiple times as that was re-run for each graph built. Now we fetch the schemas just once during context construction, passing that result into each of the graph builders. This only addresses the schema accesses during graph construction. We're still separately loading schemas during the main walk for evaluation purposes. This will be addressed in a later commit.
2018-05-31 14:39:45 -05:00
Config: testModule(t, "graph-builder-plan-basic"),
Components: components,
Schemas: &Schemas{
terraform.Schemas: export struct fields There does not appear to be any real reason that these Schemas fields are not exported, and exporting them makes it possible to directly construct Schemas for tests without pulling in an entire context.
2018-09-25 12:12:56 -05:00
Providers: map[string]*ProviderSchema{
core: Fetch schemas during context construction Previously we fetched schemas during the AttachSchemaTransformer, potentially multiple times as that was re-run for each graph built. Now we fetch the schemas just once during context construction, passing that result into each of the graph builders. This only addresses the schema accesses during graph construction. We're still separately loading schemas during the main walk for evaluation purposes. This will be addressed in a later commit.
2018-05-31 14:39:45 -05:00
"aws": awsProvider.GetSchemaReturn,
"openstack": openstackProvider.GetSchemaReturn,
core: Get tests compiling again After the refactoring to integrate HCL2 many of the tests were no longer using correct types, attribute names, etc. This is a bulk update of all of the tests to make them compile again, with minimal changes otherwise. Although the tests now compile, many of them do not yet pass. The tests will be gradually repaired in subsequent commits, as we continue to complete the refactoring and retrofit work.
2018-05-04 21:24:06 -05:00
},
},
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
DisableReduce: true,
}
core: Get tests compiling again After the refactoring to integrate HCL2 many of the tests were no longer using correct types, attribute names, etc. This is a bulk update of all of the tests to make them compile again, with minimal changes otherwise. Although the tests now compile, many of them do not yet pass. The tests will be gradually repaired in subsequent commits, as we continue to complete the refactoring and retrofit work.
2018-05-04 21:24:06 -05:00
g, err := b.Build(addrs.RootModuleInstance)
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
if err != nil {
t.Fatalf("err: %s", err)
}
core: Get tests compiling again After the refactoring to integrate HCL2 many of the tests were no longer using correct types, attribute names, etc. This is a bulk update of all of the tests to make them compile again, with minimal changes otherwise. Although the tests now compile, many of them do not yet pass. The tests will be gradually repaired in subsequent commits, as we continue to complete the refactoring and retrofit work.
2018-05-04 21:24:06 -05:00
if g.Path.String() != addrs.RootModuleInstance.String() {
t.Fatalf("wrong module path %q", g.Path)
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
}
actual := strings.TrimSpace(g.String())
expected := strings.TrimSpace(testPlanGraphBuilderStr)
if actual != expected {
core: Restore CountBoundaryTransformer to apply, add/adjust tests Moving the transformer wholesale looks like it broke some tests, with some actually doing legit work in normalizing singular resources from a foo.0 notation to just foo. Adjusted the TestPlanGraphBuilder to account for the extra meta.count-boundary nodes in the graph output now, as well as added another context test that tests this case. It appears the issue happens during validate, as this is where the state can be altered to a broken state if things are not properly transformed in the plan graph.
2017-04-20 00:23:52 -05:00
t.Fatalf("expected:\n%s\n\ngot:\n%s", expected, actual)
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
}
}
terraform: don't include providers if not targeted Fixes #12009 This is a simple change similar to #10911 where we need to exclude providers that aren't targeted.
2017-02-17 11:21:29 -06:00
func TestPlanGraphBuilder_targetModule(t *testing.T) {
b := &PlanGraphBuilder{
core: Fix tests for TestPlanGraphBuilder Previously this was just stubbing out provider types, but we now need to include schema for each of the providers and resource types the tests use in order for the references to be properly detected. The test fixtures are adjusted slightly here so we can use the simpleTestSchema as the schema for all of the different blocks in these tests. The relationships between the resources are still preserved, but the attributes are renamed to comply with this schema.
2018-05-10 11:56:32 -05:00
Config: testModule(t, "graph-builder-plan-target-module-provider"),
Components: simpleMockComponentFactory(),
core: Fetch schemas during context construction Previously we fetched schemas during the AttachSchemaTransformer, potentially multiple times as that was re-run for each graph built. Now we fetch the schemas just once during context construction, passing that result into each of the graph builders. This only addresses the schema accesses during graph construction. We're still separately loading schemas during the main walk for evaluation purposes. This will be addressed in a later commit.
2018-05-31 14:39:45 -05:00
Schemas: simpleTestSchemas(),
core: Get tests compiling again After the refactoring to integrate HCL2 many of the tests were no longer using correct types, attribute names, etc. This is a bulk update of all of the tests to make them compile again, with minimal changes otherwise. Although the tests now compile, many of them do not yet pass. The tests will be gradually repaired in subsequent commits, as we continue to complete the refactoring and retrofit work.
2018-05-04 21:24:06 -05:00
Targets: []addrs.Targetable{
addrs.RootModuleInstance.Child("child2", addrs.NoKey),
},
terraform: don't include providers if not targeted Fixes #12009 This is a simple change similar to #10911 where we need to exclude providers that aren't targeted.
2017-02-17 11:21:29 -06:00
}
core: Get tests compiling again After the refactoring to integrate HCL2 many of the tests were no longer using correct types, attribute names, etc. This is a bulk update of all of the tests to make them compile again, with minimal changes otherwise. Although the tests now compile, many of them do not yet pass. The tests will be gradually repaired in subsequent commits, as we continue to complete the refactoring and retrofit work.
2018-05-04 21:24:06 -05:00
g, err := b.Build(addrs.RootModuleInstance)
terraform: don't include providers if not targeted Fixes #12009 This is a simple change similar to #10911 where we need to exclude providers that aren't targeted.
2017-02-17 11:21:29 -06:00
if err != nil {
t.Fatalf("err: %s", err)
}
t.Logf("Graph: %s", g.String())
core: Fix tests for TestPlanGraphBuilder Previously this was just stubbing out provider types, but we now need to include schema for each of the providers and resource types the tests use in order for the references to be properly detected. The test fixtures are adjusted slightly here so we can use the simpleTestSchema as the schema for all of the different blocks in these tests. The relationships between the resources are still preserved, but the attributes are renamed to comply with this schema.
2018-05-10 11:56:32 -05:00
testGraphNotContains(t, g, "module.child1.provider.test")
testGraphNotContains(t, g, "module.child1.test_object.foo")
terraform: don't include providers if not targeted Fixes #12009 This is a simple change similar to #10911 where we need to exclude providers that aren't targeted.
2017-02-17 11:21:29 -06:00
}
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
const testPlanGraphBuilderStr = `
aws_instance.web
aws_security_group.firewall
provider.aws
var.foo
aws_load_balancer.weblb
aws_instance.web
provider.aws
aws_security_group.firewall
provider.aws
core: graph nodes and edges for local values A local value is similar to an output in that it exists only within state and just always evaluates its value as best it can with the current state. Therefore it has a single graph node type for all walks, which will deal with that evaluation operation.
2017-07-01 11:48:37 -05:00
local.instance_id
aws_instance.web
core: update test fixtures for new name of the "count boundary" vertex
2018-09-07 18:58:32 -05:00
meta.count-boundary (EachMode fixup)
core: Restore CountBoundaryTransformer to apply, add/adjust tests Moving the transformer wholesale looks like it broke some tests, with some actually doing legit work in normalizing singular resources from a foo.0 notation to just foo. Adjusted the TestPlanGraphBuilder to account for the extra meta.count-boundary nodes in the graph output now, as well as added another context test that tests this case. It appears the issue happens during validate, as this is where the state can be altered to a broken state if things are not properly transformed in the plan graph.
2017-04-20 00:23:52 -05:00
aws_instance.web
aws_load_balancer.weblb
aws_security_group.firewall
core: graph nodes and edges for local values A local value is similar to an output in that it exists only within state and just always evaluates its value as best it can with the current state. Therefore it has a single graph node type for all walks, which will deal with that evaluation operation.
2017-07-01 11:48:37 -05:00
local.instance_id
core: Restore CountBoundaryTransformer to apply, add/adjust tests Moving the transformer wholesale looks like it broke some tests, with some actually doing legit work in normalizing singular resources from a foo.0 notation to just foo. Adjusted the TestPlanGraphBuilder to account for the extra meta.count-boundary nodes in the graph output now, as well as added another context test that tests this case. It appears the issue happens during validate, as this is where the state can be altered to a broken state if things are not properly transformed in the plan graph.
2017-04-20 00:23:52 -05:00
openstack_floating_ip.random
core: graph nodes and edges for local values A local value is similar to an output in that it exists only within state and just always evaluates its value as best it can with the current state. Therefore it has a single graph node type for all walks, which will deal with that evaluation operation.
2017-07-01 11:48:37 -05:00
output.instance_id
core: Restore CountBoundaryTransformer to apply, add/adjust tests Moving the transformer wholesale looks like it broke some tests, with some actually doing legit work in normalizing singular resources from a foo.0 notation to just foo. Adjusted the TestPlanGraphBuilder to account for the extra meta.count-boundary nodes in the graph output now, as well as added another context test that tests this case. It appears the issue happens during validate, as this is where the state can be altered to a broken state if things are not properly transformed in the plan graph.
2017-04-20 00:23:52 -05:00
provider.aws
provider.openstack
var.foo
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
openstack_floating_ip.random
provider.openstack
core: graph nodes and edges for local values A local value is similar to an output in that it exists only within state and just always evaluates its value as best it can with the current state. Therefore it has a single graph node type for all walks, which will deal with that evaluation operation.
2017-07-01 11:48:37 -05:00
output.instance_id
local.instance_id
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
provider.aws
openstack_floating_ip.random
Add the close provider and provisioner transformers (#13102)
2017-04-12 16:25:15 -05:00
provider.aws (close)
aws_instance.web
aws_load_balancer.weblb
aws_security_group.firewall
provider.aws
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
provider.openstack
Add the close provider and provisioner transformers (#13102)
2017-04-12 16:25:15 -05:00
provider.openstack (close)
openstack_floating_ip.random
provider.openstack
root
core: update test fixtures for new name of the "count boundary" vertex
2018-09-07 18:58:32 -05:00
meta.count-boundary (EachMode fixup)
Add the close provider and provisioner transformers (#13102)
2017-04-12 16:25:15 -05:00
provider.aws (close)
provider.openstack (close)
terraform: tests for the plan graph builder
2016-11-05 19:58:38 -05:00
var.foo
`
Reference in New Issue Copy Permalink