2016-11-14 00:18:18 -06:00
|
|
|
package command
|
|
|
|
|
|
|
|
import (
|
|
|
|
"bufio"
|
|
|
|
"fmt"
|
|
|
|
"strings"
|
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
"github.com/hashicorp/terraform/backend"
|
2017-05-01 16:47:53 -05:00
|
|
|
"github.com/hashicorp/terraform/config"
|
2016-11-14 02:32:01 -06:00
|
|
|
"github.com/hashicorp/terraform/helper/wrappedstreams"
|
2016-11-14 00:18:18 -06:00
|
|
|
"github.com/hashicorp/terraform/repl"
|
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-06 18:41:48 -06:00
|
|
|
"github.com/hashicorp/terraform/tfdiags"
|
2016-11-14 00:18:18 -06:00
|
|
|
|
|
|
|
"github.com/mitchellh/cli"
|
|
|
|
)
|
|
|
|
|
|
|
|
// ConsoleCommand is a Command implementation that applies a Terraform
|
|
|
|
// configuration and actually builds or changes infrastructure.
|
|
|
|
type ConsoleCommand struct {
|
|
|
|
Meta
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *ConsoleCommand) Run(args []string) int {
|
2017-03-07 22:09:48 -06:00
|
|
|
args, err := c.Meta.process(args, true)
|
|
|
|
if err != nil {
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2016-11-14 00:18:18 -06:00
|
|
|
cmdFlags := c.Meta.flagSet("console")
|
|
|
|
cmdFlags.StringVar(&c.Meta.statePath, "state", DefaultStateFilename, "path")
|
|
|
|
cmdFlags.Usage = func() { c.Ui.Error(c.Help()) }
|
|
|
|
if err := cmdFlags.Parse(args); err != nil {
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
configPath, err := ModulePath(cmdFlags.Args())
|
2016-11-14 00:18:18 -06:00
|
|
|
if err != nil {
|
2017-01-18 22:50:45 -06:00
|
|
|
c.Ui.Error(err.Error())
|
|
|
|
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-06 18:41:48 -06:00
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
// Load the module
|
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-06 18:41:48 -06:00
|
|
|
mod, diags := c.Module(configPath)
|
|
|
|
if diags.HasErrors() {
|
|
|
|
c.showDiagnostics(diags)
|
2016-11-14 00:18:18 -06:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2017-05-01 16:47:53 -05:00
|
|
|
var conf *config.Config
|
|
|
|
if mod != nil {
|
|
|
|
conf = mod.Config()
|
|
|
|
}
|
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
// Load the backend
|
2017-05-01 16:47:53 -05:00
|
|
|
b, err := c.Backend(&BackendOpts{
|
|
|
|
Config: conf,
|
|
|
|
})
|
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Failed to load backend: %s", err))
|
2016-11-14 00:18:18 -06:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
// We require a local backend
|
|
|
|
local, ok := b.(backend.Local)
|
|
|
|
if !ok {
|
|
|
|
c.Ui.Error(ErrUnsupportedLocalOp)
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
|
|
|
// Build the operation
|
|
|
|
opReq := c.Operation()
|
|
|
|
opReq.Module = mod
|
|
|
|
|
|
|
|
// Get the context
|
|
|
|
ctx, _, err := local.Context(opReq)
|
2016-11-14 00:18:18 -06:00
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(err.Error())
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
|
|
|
// Setup the UI so we can output directly to stdout
|
|
|
|
ui := &cli.BasicUi{
|
2016-11-14 02:32:01 -06:00
|
|
|
Writer: wrappedstreams.Stdout(),
|
|
|
|
ErrorWriter: wrappedstreams.Stderr(),
|
2016-11-14 00:18:18 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
// IO Loop
|
|
|
|
session := &repl.Session{
|
|
|
|
Interpolater: ctx.Interpolater(),
|
|
|
|
}
|
|
|
|
|
|
|
|
// Determine if stdin is a pipe. If so, we evaluate directly.
|
|
|
|
if c.StdinPiped() {
|
|
|
|
return c.modePiped(session, ui)
|
|
|
|
}
|
|
|
|
|
|
|
|
return c.modeInteractive(session, ui)
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *ConsoleCommand) modePiped(session *repl.Session, ui cli.Ui) int {
|
|
|
|
var lastResult string
|
2016-11-14 02:32:01 -06:00
|
|
|
scanner := bufio.NewScanner(wrappedstreams.Stdin())
|
2016-11-14 00:18:18 -06:00
|
|
|
for scanner.Scan() {
|
|
|
|
// Handle it. If there is an error exit immediately
|
|
|
|
result, err := session.Handle(strings.TrimSpace(scanner.Text()))
|
|
|
|
if err != nil {
|
|
|
|
ui.Error(err.Error())
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
|
|
|
// Store the last result
|
|
|
|
lastResult = result
|
|
|
|
}
|
|
|
|
|
|
|
|
// Output the final result
|
|
|
|
ui.Output(lastResult)
|
|
|
|
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *ConsoleCommand) Help() string {
|
|
|
|
helpText := `
|
|
|
|
Usage: terraform console [options] [DIR]
|
|
|
|
|
|
|
|
Starts an interactive console for experimenting with Terraform
|
|
|
|
interpolations.
|
|
|
|
|
|
|
|
This will open an interactive console that you can use to type
|
|
|
|
interpolations into and inspect their values. This command loads the
|
|
|
|
current state. This lets you explore and test interpolations before
|
|
|
|
using them in future configurations.
|
|
|
|
|
|
|
|
This command will never modify your state.
|
|
|
|
|
|
|
|
DIR can be set to a directory with a Terraform state to load. By
|
|
|
|
default, this will default to the current working directory.
|
|
|
|
|
|
|
|
Options:
|
|
|
|
|
|
|
|
-state=path Path to read state. Defaults to "terraform.tfstate"
|
|
|
|
|
|
|
|
-var 'foo=bar' Set a variable in the Terraform configuration. This
|
|
|
|
flag can be set multiple times.
|
|
|
|
|
|
|
|
-var-file=foo Set variables in the Terraform configuration from
|
2017-06-21 20:22:07 -05:00
|
|
|
a file. If "terraform.tfvars" or any ".auto.tfvars"
|
|
|
|
files are present, they will be automatically loaded.
|
2016-11-14 00:18:18 -06:00
|
|
|
|
|
|
|
|
|
|
|
`
|
|
|
|
return strings.TrimSpace(helpText)
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *ConsoleCommand) Synopsis() string {
|
|
|
|
return "Interactive console for Terraform interpolations"
|
|
|
|
}
|