Deletions from backend local
This commit is contained in:
parent
bb3d513c4f
commit
37d16b2f79
|
@ -261,26 +261,6 @@ func testOperationApply(t *testing.T, configDir string) (*backend.Operation, fun
|
||||||
}, configCleanup
|
}, configCleanup
|
||||||
}
|
}
|
||||||
|
|
||||||
// testApplyState is just a common state that we use for testing refresh.
|
|
||||||
func testApplyState() *terraform.State {
|
|
||||||
return &terraform.State{
|
|
||||||
Version: 2,
|
|
||||||
Modules: []*terraform.ModuleState{
|
|
||||||
&terraform.ModuleState{
|
|
||||||
Path: []string{"root"},
|
|
||||||
Resources: map[string]*terraform.ResourceState{
|
|
||||||
"test_instance.foo": &terraform.ResourceState{
|
|
||||||
Type: "test_instance",
|
|
||||||
Primary: &terraform.InstanceState{
|
|
||||||
ID: "bar",
|
|
||||||
},
|
|
||||||
},
|
|
||||||
},
|
|
||||||
},
|
|
||||||
},
|
|
||||||
}
|
|
||||||
}
|
|
||||||
|
|
||||||
// applyFixtureSchema returns a schema suitable for processing the
|
// applyFixtureSchema returns a schema suitable for processing the
|
||||||
// configuration in testdata/apply . This schema should be
|
// configuration in testdata/apply . This schema should be
|
||||||
// assigned to a mock provider named "test".
|
// assigned to a mock provider named "test".
|
||||||
|
|
|
@ -410,11 +410,3 @@ func (v unparsedUnknownVariableValue) ParseVariableValue(mode configs.VariablePa
|
||||||
SourceType: terraform.ValueFromInput,
|
SourceType: terraform.ValueFromInput,
|
||||||
}, nil
|
}, nil
|
||||||
}
|
}
|
||||||
|
|
||||||
const validateWarnHeader = `
|
|
||||||
There are warnings related to your configuration. If no errors occurred,
|
|
||||||
Terraform will continue despite these warnings. It is a good idea to resolve
|
|
||||||
these warnings in the near future.
|
|
||||||
|
|
||||||
Warnings:
|
|
||||||
`
|
|
||||||
|
|
|
@ -313,16 +313,6 @@ func RenderPlan(plan *plans.Plan, state *states.State, schemas *terraform.Schema
|
||||||
)))
|
)))
|
||||||
}
|
}
|
||||||
|
|
||||||
const planErrNoConfig = `
|
|
||||||
No configuration files found!
|
|
||||||
|
|
||||||
Plan requires configuration to be present. Planning without a configuration
|
|
||||||
would mark everything for destruction, which is normally not what is desired.
|
|
||||||
If you would like to destroy everything, please run plan with the "-destroy"
|
|
||||||
flag or create a single empty configuration file. Otherwise, please create
|
|
||||||
a Terraform configuration file in the path being executed and try again.
|
|
||||||
`
|
|
||||||
|
|
||||||
const planHeaderIntro = `
|
const planHeaderIntro = `
|
||||||
An execution plan has been generated and is shown below.
|
An execution plan has been generated and is shown below.
|
||||||
Resource actions are indicated with the following symbols:
|
Resource actions are indicated with the following symbols:
|
||||||
|
|
Loading…
Reference in New Issue