2016-11-14 07:18:18 +01:00
|
|
|
package command
|
|
|
|
|
|
|
|
import (
|
|
|
|
"bufio"
|
2019-08-16 14:31:21 +02:00
|
|
|
"fmt"
|
2016-11-14 07:18:18 +01:00
|
|
|
"strings"
|
|
|
|
|
2018-05-04 05:44:55 +02:00
|
|
|
"github.com/hashicorp/terraform/addrs"
|
2017-01-19 05:50:45 +01:00
|
|
|
"github.com/hashicorp/terraform/backend"
|
2021-01-20 19:18:02 +01:00
|
|
|
"github.com/hashicorp/terraform/internal/helper/wrappedstreams"
|
2016-11-14 07:18:18 +01: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-07 01:41:48 +01:00
|
|
|
"github.com/hashicorp/terraform/tfdiags"
|
2016-11-14 07:18:18 +01: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 {
|
2020-04-01 21:01:08 +02:00
|
|
|
args = c.Meta.process(args)
|
2019-07-19 20:34:12 +02:00
|
|
|
cmdFlags := c.Meta.extendedFlagSet("console")
|
2016-11-14 07:18:18 +01:00
|
|
|
cmdFlags.StringVar(&c.Meta.statePath, "state", DefaultStateFilename, "path")
|
|
|
|
cmdFlags.Usage = func() { c.Ui.Error(c.Help()) }
|
|
|
|
if err := cmdFlags.Parse(args); err != nil {
|
2019-08-16 14:31:21 +02:00
|
|
|
c.Ui.Error(fmt.Sprintf("Error parsing command line flags: %s\n", err.Error()))
|
2016-11-14 07:18:18 +01:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2017-01-19 05:50:45 +01:00
|
|
|
configPath, err := ModulePath(cmdFlags.Args())
|
2016-11-14 07:18:18 +01:00
|
|
|
if err != nil {
|
2017-01-19 05:50:45 +01:00
|
|
|
c.Ui.Error(err.Error())
|
|
|
|
return 1
|
|
|
|
}
|
2020-12-11 19:22:06 +01:00
|
|
|
configPath = c.Meta.normalizePath(configPath)
|
2017-01-19 05:50:45 +01:00
|
|
|
|
2019-08-28 17:57:05 +02:00
|
|
|
// Check for user-supplied plugin path
|
|
|
|
if c.pluginPath, err = c.loadPluginPath(); err != nil {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Error loading plugin path: %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
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
|
2018-03-28 00:31:05 +02:00
|
|
|
backendConfig, backendDiags := c.loadBackendConfig(configPath)
|
|
|
|
diags = diags.Append(backendDiags)
|
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() {
|
|
|
|
c.showDiagnostics(diags)
|
2016-11-14 07:18:18 +01:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2017-01-19 05:50:45 +01:00
|
|
|
// Load the backend
|
2018-03-28 00:31:05 +02:00
|
|
|
b, backendDiags := c.Backend(&BackendOpts{
|
|
|
|
Config: backendConfig,
|
2017-05-01 23:47:53 +02:00
|
|
|
})
|
2018-03-28 00:31:05 +02:00
|
|
|
diags = diags.Append(backendDiags)
|
|
|
|
if backendDiags.HasErrors() {
|
|
|
|
c.showDiagnostics(diags)
|
2016-11-14 07:18:18 +01:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2017-01-19 05:50:45 +01:00
|
|
|
// We require a local backend
|
|
|
|
local, ok := b.(backend.Local)
|
|
|
|
if !ok {
|
2018-03-28 00:31:05 +02:00
|
|
|
c.showDiagnostics(diags) // in case of any warnings in here
|
2017-01-19 05:50:45 +01:00
|
|
|
c.Ui.Error(ErrUnsupportedLocalOp)
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
backend: Validate remote backend Terraform version
When using the enhanced remote backend, a subset of all Terraform
operations are supported. Of these, only plan and apply can be executed
on the remote infrastructure (e.g. Terraform Cloud). Other operations
run locally and use the remote backend for state storage.
This causes problems when the local version of Terraform does not match
the configured version from the remote workspace. If the two versions
are incompatible, an `import` or `state mv` operation can cause the
remote workspace to be unusable until a manual fix is applied.
To prevent this from happening accidentally, this commit introduces a
check that the local Terraform version and the configured remote
workspace Terraform version are compatible. This check is skipped for
commands which do not write state, and can also be disabled by the use
of a new command-line flag, `-ignore-remote-version`.
Terraform version compatibility is defined as:
- For all releases before 0.14.0, local must exactly equal remote, as
two different versions cannot share state;
- 0.14.0 to 1.0.x are compatible, as we will not change the state
version number until at least Terraform 1.1.0;
- Versions after 1.1.0 must have the same major and minor versions, as
we will not change the state version number in a patch release.
If the two versions are incompatible, a diagnostic is displayed,
advising that the error can be suppressed with `-ignore-remote-version`.
When this flag is used, the diagnostic is still displayed, but as a
warning instead of an error.
Commands which will not write state can assert this fact by calling the
helper `meta.ignoreRemoteBackendVersionConflict`, which will disable the
checks. Those which can write state should instead call the helper
`meta.remoteBackendVersionCheck`, which will return diagnostics for
display.
In addition to these explicit paths for managing the version check, we
have an implicit check in the remote backend's state manager
initialization method. Both of the above helpers will disable this
check. This fallback is in place to ensure that future code paths which
access state cannot accidentally skip the remote version check.
2020-11-13 22:43:56 +01:00
|
|
|
// This is a read-only command
|
|
|
|
c.ignoreRemoteBackendVersionConflict(b)
|
|
|
|
|
2017-01-19 05:50:45 +01:00
|
|
|
// Build the operation
|
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 23:24:45 +02:00
|
|
|
opReq := c.Operation(b)
|
2018-03-28 00:31:05 +02:00
|
|
|
opReq.ConfigDir = configPath
|
|
|
|
opReq.ConfigLoader, err = c.initConfigLoader()
|
2019-10-09 23:29:40 +02:00
|
|
|
opReq.AllowUnsetVariables = true // we'll just evaluate them as unknown
|
2018-03-28 00:31:05 +02:00
|
|
|
if err != nil {
|
|
|
|
diags = diags.Append(err)
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
2018-11-21 15:35:27 +01:00
|
|
|
|
2018-10-13 17:07:58 +02:00
|
|
|
{
|
|
|
|
var moreDiags tfdiags.Diagnostics
|
|
|
|
opReq.Variables, moreDiags = c.collectVariableValues()
|
|
|
|
diags = diags.Append(moreDiags)
|
|
|
|
if moreDiags.HasErrors() {
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
}
|
2017-01-19 05:50:45 +01:00
|
|
|
|
|
|
|
// Get the context
|
2018-03-28 00:31:05 +02:00
|
|
|
ctx, _, ctxDiags := local.Context(opReq)
|
2020-08-11 17:23:42 +02:00
|
|
|
diags = diags.Append(ctxDiags)
|
|
|
|
if ctxDiags.HasErrors() {
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
2016-11-14 07:18:18 +01:00
|
|
|
|
2020-08-11 17:23:42 +02:00
|
|
|
// Successfully creating the context can result in a lock, so ensure we release it
|
2018-03-20 17:44:12 +01:00
|
|
|
defer func() {
|
|
|
|
err := opReq.StateLocker.Unlock(nil)
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(err.Error())
|
|
|
|
}
|
|
|
|
}()
|
|
|
|
|
2021-01-26 20:39:11 +01:00
|
|
|
// Set up the UI so we can output directly to stdout
|
2016-11-14 07:18:18 +01:00
|
|
|
ui := &cli.BasicUi{
|
2016-11-14 09:32:01 +01:00
|
|
|
Writer: wrappedstreams.Stdout(),
|
|
|
|
ErrorWriter: wrappedstreams.Stderr(),
|
2016-11-14 07:18:18 +01:00
|
|
|
}
|
|
|
|
|
2018-05-04 05:44:55 +02:00
|
|
|
// Before we can evaluate expressions, we must compute and populate any
|
|
|
|
// derived values (input variables, local values, output values)
|
|
|
|
// that are not stored in the persistent state.
|
|
|
|
scope, scopeDiags := ctx.Eval(addrs.RootModuleInstance)
|
|
|
|
diags = diags.Append(scopeDiags)
|
|
|
|
if scope == nil {
|
|
|
|
// scope is nil if there are errors so bad that we can't even build a scope.
|
|
|
|
// Otherwise, we'll try to eval anyway.
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
if diags.HasErrors() {
|
|
|
|
diags = diags.Append(tfdiags.SimpleWarning("Due to the problems above, some expressions may produce unexpected results."))
|
|
|
|
}
|
|
|
|
|
|
|
|
// Before we become interactive we'll show any diagnostics we encountered
|
|
|
|
// during initialization, and then afterwards the driver will manage any
|
|
|
|
// further diagnostics itself.
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
|
2016-11-14 07:18:18 +01:00
|
|
|
// IO Loop
|
|
|
|
session := &repl.Session{
|
2018-05-04 05:44:55 +02:00
|
|
|
Scope: scope,
|
2016-11-14 07:18:18 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
// 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 09:32:01 +01:00
|
|
|
scanner := bufio.NewScanner(wrappedstreams.Stdin())
|
2016-11-14 07:18:18 +01:00
|
|
|
for scanner.Scan() {
|
2018-05-04 05:44:55 +02:00
|
|
|
result, exit, diags := session.Handle(strings.TrimSpace(scanner.Text()))
|
|
|
|
if diags.HasErrors() {
|
|
|
|
// In piped mode we'll exit immediately on error.
|
|
|
|
c.showDiagnostics(diags)
|
2016-11-14 07:18:18 +01:00
|
|
|
return 1
|
|
|
|
}
|
2018-05-04 05:44:55 +02:00
|
|
|
if exit {
|
|
|
|
return 0
|
|
|
|
}
|
2016-11-14 07:18:18 +01:00
|
|
|
|
|
|
|
// 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-22 03:22:07 +02:00
|
|
|
a file. If "terraform.tfvars" or any ".auto.tfvars"
|
|
|
|
files are present, they will be automatically loaded.
|
2016-11-14 07:18:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
`
|
|
|
|
return strings.TrimSpace(helpText)
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *ConsoleCommand) Synopsis() string {
|
2020-10-24 01:55:32 +02:00
|
|
|
return "Try Terraform expressions at an interactive command prompt"
|
2016-11-14 07:18:18 +01:00
|
|
|
}
|