2014-07-01 19:02:13 +02:00
|
|
|
package command
|
|
|
|
|
|
|
|
import (
|
|
|
|
"flag"
|
|
|
|
"fmt"
|
|
|
|
"strings"
|
2015-02-20 07:58:42 +01:00
|
|
|
|
command: validate config as part of loading it
Previously we required callers to separately call .Validate on the root
module to determine if there were any value errors, but we did that
inconsistently and would thus see crashes in some cases where later code
would try to use invalid configuration as if it were valid.
Now we run .Validate automatically after config loading, returning the
resulting diagnostics. Since we return a diagnostics here, it's possible
to return both warnings and errors.
We return the loaded module even if it's invalid, so callers are free to
ignore returned errors and try to work with the config anyway, though they
will need to be defensive against invalid configuration themselves in
that case.
As a result of this, all of the commands that load configuration now need
to use diagnostic printing to signal errors. For the moment this just
allows us to return potentially-multiple config errors/warnings in full
fidelity, but also sets us up for later when more subsystems are able
to produce rich diagnostics so we can show them all together.
Finally, this commit also removes some stale, commented-out code for the
"legacy" (pre-0.8) graph implementation, which has not been available
for some time.
2017-12-07 01:41:48 +01:00
|
|
|
"github.com/hashicorp/terraform/tfdiags"
|
|
|
|
|
2017-01-19 05:50:45 +01:00
|
|
|
"github.com/hashicorp/terraform/backend"
|
2017-05-01 23:47:53 +02:00
|
|
|
"github.com/hashicorp/terraform/config"
|
2017-01-19 05:50:45 +01:00
|
|
|
"github.com/hashicorp/terraform/config/module"
|
2016-11-09 15:58:52 +01:00
|
|
|
"github.com/hashicorp/terraform/dag"
|
2015-02-20 07:58:42 +01:00
|
|
|
"github.com/hashicorp/terraform/terraform"
|
2014-07-01 19:02:13 +02:00
|
|
|
)
|
|
|
|
|
|
|
|
// GraphCommand is a Command implementation that takes a Terraform
|
|
|
|
// configuration and outputs the dependency tree in graphical form.
|
|
|
|
type GraphCommand struct {
|
2014-07-13 05:37:30 +02:00
|
|
|
Meta
|
2014-07-01 19:02:13 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
func (c *GraphCommand) Run(args []string) int {
|
2014-09-25 02:36:27 +02:00
|
|
|
var moduleDepth int
|
2015-04-23 20:24:26 +02:00
|
|
|
var verbose bool
|
|
|
|
var drawCycles bool
|
2016-12-04 00:00:34 +01:00
|
|
|
var graphTypeStr string
|
2014-09-25 02:36:27 +02:00
|
|
|
|
2017-03-08 05:09:48 +01:00
|
|
|
args, err := c.Meta.process(args, false)
|
|
|
|
if err != nil {
|
|
|
|
return 1
|
|
|
|
}
|
2014-07-13 05:37:30 +02:00
|
|
|
|
2014-07-01 19:02:13 +02:00
|
|
|
cmdFlags := flag.NewFlagSet("graph", flag.ContinueOnError)
|
2015-04-30 21:05:39 +02:00
|
|
|
c.addModuleDepthFlag(cmdFlags, &moduleDepth)
|
2015-04-23 20:24:26 +02:00
|
|
|
cmdFlags.BoolVar(&verbose, "verbose", false, "verbose")
|
|
|
|
cmdFlags.BoolVar(&drawCycles, "draw-cycles", false, "draw-cycles")
|
2016-12-04 00:00:34 +01:00
|
|
|
cmdFlags.StringVar(&graphTypeStr, "type", "", "type")
|
2014-07-01 19:02:13 +02:00
|
|
|
cmdFlags.Usage = func() { c.Ui.Error(c.Help()) }
|
|
|
|
if err := cmdFlags.Parse(args); err != nil {
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2017-01-19 05:50:45 +01:00
|
|
|
configPath, err := ModulePath(cmdFlags.Args())
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(err.Error())
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
|
|
|
// Check if the path is a plan
|
|
|
|
plan, err := c.Plan(configPath)
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(err.Error())
|
2014-07-01 19:02:13 +02:00
|
|
|
return 1
|
2017-01-19 05:50:45 +01:00
|
|
|
}
|
|
|
|
if plan != nil {
|
|
|
|
// Reset for backend loading
|
|
|
|
configPath = ""
|
|
|
|
}
|
|
|
|
|
command: validate config as part of loading it
Previously we required callers to separately call .Validate on the root
module to determine if there were any value errors, but we did that
inconsistently and would thus see crashes in some cases where later code
would try to use invalid configuration as if it were valid.
Now we run .Validate automatically after config loading, returning the
resulting diagnostics. Since we return a diagnostics here, it's possible
to return both warnings and errors.
We return the loaded module even if it's invalid, so callers are free to
ignore returned errors and try to work with the config anyway, though they
will need to be defensive against invalid configuration themselves in
that case.
As a result of this, all of the commands that load configuration now need
to use diagnostic printing to signal errors. For the moment this just
allows us to return potentially-multiple config errors/warnings in full
fidelity, but also sets us up for later when more subsystems are able
to produce rich diagnostics so we can show them all together.
Finally, this commit also removes some stale, commented-out code for the
"legacy" (pre-0.8) graph implementation, which has not been available
for some time.
2017-12-07 01:41:48 +01:00
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
|
2017-01-19 05:50:45 +01:00
|
|
|
// Load the module
|
|
|
|
var mod *module.Tree
|
|
|
|
if plan == nil {
|
command: validate config as part of loading it
Previously we required callers to separately call .Validate on the root
module to determine if there were any value errors, but we did that
inconsistently and would thus see crashes in some cases where later code
would try to use invalid configuration as if it were valid.
Now we run .Validate automatically after config loading, returning the
resulting diagnostics. Since we return a diagnostics here, it's possible
to return both warnings and errors.
We return the loaded module even if it's invalid, so callers are free to
ignore returned errors and try to work with the config anyway, though they
will need to be defensive against invalid configuration themselves in
that case.
As a result of this, all of the commands that load configuration now need
to use diagnostic printing to signal errors. For the moment this just
allows us to return potentially-multiple config errors/warnings in full
fidelity, but also sets us up for later when more subsystems are able
to produce rich diagnostics so we can show them all together.
Finally, this commit also removes some stale, commented-out code for the
"legacy" (pre-0.8) graph implementation, which has not been available
for some time.
2017-12-07 01:41:48 +01:00
|
|
|
var modDiags tfdiags.Diagnostics
|
|
|
|
mod, modDiags = c.Module(configPath)
|
|
|
|
diags = diags.Append(modDiags)
|
|
|
|
if modDiags.HasErrors() {
|
|
|
|
c.showDiagnostics(diags)
|
2017-01-19 05:50:45 +01:00
|
|
|
return 1
|
2014-07-12 05:41:47 +02:00
|
|
|
}
|
2014-07-01 19:02:13 +02:00
|
|
|
}
|
|
|
|
|
2017-05-01 23:47:53 +02:00
|
|
|
var conf *config.Config
|
|
|
|
if mod != nil {
|
|
|
|
conf = mod.Config()
|
|
|
|
}
|
|
|
|
|
2017-01-19 05:50:45 +01:00
|
|
|
// Load the backend
|
|
|
|
b, err := c.Backend(&BackendOpts{
|
2017-05-01 23:47:53 +02:00
|
|
|
Config: conf,
|
|
|
|
Plan: plan,
|
2014-09-22 19:56:50 +02:00
|
|
|
})
|
2014-07-01 19:02:13 +02:00
|
|
|
if err != nil {
|
2017-01-19 05:50:45 +01:00
|
|
|
c.Ui.Error(fmt.Sprintf("Failed to load backend: %s", err))
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
|
|
|
// We require a local backend
|
|
|
|
local, ok := b.(backend.Local)
|
|
|
|
if !ok {
|
|
|
|
c.Ui.Error(ErrUnsupportedLocalOp)
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2017-07-18 19:03:57 +02:00
|
|
|
// Building a graph may require config module to be present, even if it's
|
|
|
|
// empty.
|
|
|
|
if mod == nil && plan == nil {
|
|
|
|
mod = module.NewEmptyTree()
|
|
|
|
}
|
|
|
|
|
2017-01-19 05:50:45 +01:00
|
|
|
// Build the operation
|
|
|
|
opReq := c.Operation()
|
|
|
|
opReq.Module = mod
|
|
|
|
opReq.Plan = plan
|
|
|
|
|
|
|
|
// Get the context
|
|
|
|
ctx, _, err := local.Context(opReq)
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(err.Error())
|
2014-07-01 19:02:13 +02:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2016-12-04 00:00:34 +01:00
|
|
|
// Determine the graph type
|
|
|
|
graphType := terraform.GraphTypePlan
|
2017-01-19 05:50:45 +01:00
|
|
|
if plan != nil {
|
2016-12-04 00:00:34 +01:00
|
|
|
graphType = terraform.GraphTypeApply
|
|
|
|
}
|
|
|
|
|
|
|
|
if graphTypeStr != "" {
|
|
|
|
v, ok := terraform.GraphTypeMap[graphTypeStr]
|
|
|
|
if !ok {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Invalid graph type requested: %s", graphTypeStr))
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
|
|
|
graphType = v
|
|
|
|
}
|
|
|
|
|
2015-04-23 20:24:26 +02:00
|
|
|
// Skip validation during graph generation - we want to see the graph even if
|
|
|
|
// it is invalid for some reason.
|
2016-12-04 00:00:34 +01:00
|
|
|
g, err := ctx.Graph(graphType, &terraform.ContextGraphOpts{
|
2015-04-23 20:24:26 +02:00
|
|
|
Verbose: verbose,
|
|
|
|
Validate: false,
|
2015-04-23 17:52:31 +02:00
|
|
|
})
|
2014-07-01 19:02:13 +02:00
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Error creating graph: %s", err))
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2016-11-09 15:58:52 +01:00
|
|
|
graphStr, err := terraform.GraphDot(g, &dag.DotOpts{
|
2015-04-23 20:24:26 +02:00
|
|
|
DrawCycles: drawCycles,
|
|
|
|
MaxDepth: moduleDepth,
|
|
|
|
Verbose: verbose,
|
|
|
|
})
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Error converting graph: %s", err))
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
command: validate config as part of loading it
Previously we required callers to separately call .Validate on the root
module to determine if there were any value errors, but we did that
inconsistently and would thus see crashes in some cases where later code
would try to use invalid configuration as if it were valid.
Now we run .Validate automatically after config loading, returning the
resulting diagnostics. Since we return a diagnostics here, it's possible
to return both warnings and errors.
We return the loaded module even if it's invalid, so callers are free to
ignore returned errors and try to work with the config anyway, though they
will need to be defensive against invalid configuration themselves in
that case.
As a result of this, all of the commands that load configuration now need
to use diagnostic printing to signal errors. For the moment this just
allows us to return potentially-multiple config errors/warnings in full
fidelity, but also sets us up for later when more subsystems are able
to produce rich diagnostics so we can show them all together.
Finally, this commit also removes some stale, commented-out code for the
"legacy" (pre-0.8) graph implementation, which has not been available
for some time.
2017-12-07 01:41:48 +01:00
|
|
|
if diags.HasErrors() {
|
|
|
|
// For this command we only show diagnostics if there are errors,
|
|
|
|
// because printing out naked warnings could upset a naive program
|
|
|
|
// consuming our dot output.
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2015-04-23 20:24:26 +02:00
|
|
|
c.Ui.Output(graphStr)
|
2014-07-01 19:02:13 +02:00
|
|
|
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *GraphCommand) Help() string {
|
|
|
|
helpText := `
|
2015-04-23 20:24:26 +02:00
|
|
|
Usage: terraform graph [options] [DIR]
|
2014-07-01 19:02:13 +02:00
|
|
|
|
2016-12-04 00:00:34 +01:00
|
|
|
Outputs the visual execution graph of Terraform resources according to
|
2015-04-23 20:24:26 +02:00
|
|
|
configuration files in DIR (or the current directory if omitted).
|
2014-07-01 19:02:13 +02:00
|
|
|
|
2014-07-12 05:38:03 +02:00
|
|
|
The graph is outputted in DOT format. The typical program that can
|
|
|
|
read this format is GraphViz, but many web services are also available
|
|
|
|
to read this format.
|
|
|
|
|
2016-12-04 00:00:34 +01:00
|
|
|
The -type flag can be used to control the type of graph shown. Terraform
|
|
|
|
creates different graphs for different operations. See the options below
|
|
|
|
for the list of types supported. The default type is "plan" if a
|
|
|
|
configuration is given, and "apply" if a plan file is passed as an
|
|
|
|
argument.
|
2014-09-25 02:36:27 +02:00
|
|
|
|
2016-12-04 00:00:34 +01:00
|
|
|
Options:
|
2015-04-23 20:24:26 +02:00
|
|
|
|
2016-12-04 00:00:34 +01:00
|
|
|
-draw-cycles Highlight any cycles in the graph with colored edges.
|
|
|
|
This helps when diagnosing cycle errors.
|
2014-09-25 02:36:27 +02:00
|
|
|
|
2016-12-04 00:00:34 +01:00
|
|
|
-no-color If specified, output won't contain any color.
|
2015-06-22 14:14:01 +02:00
|
|
|
|
2016-12-04 00:00:34 +01:00
|
|
|
-type=plan Type of graph to output. Can be: plan, plan-destroy, apply,
|
2017-01-27 00:18:42 +01:00
|
|
|
validate, input, refresh.
|
|
|
|
|
2015-06-22 14:14:01 +02:00
|
|
|
|
2014-07-01 19:02:13 +02:00
|
|
|
`
|
|
|
|
return strings.TrimSpace(helpText)
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *GraphCommand) Synopsis() string {
|
2014-07-13 04:28:38 +02:00
|
|
|
return "Create a visual graph of Terraform resources"
|
2014-07-01 19:02:13 +02:00
|
|
|
}
|