2017-04-26 03:10:10 +02:00
|
|
|
package command
|
|
|
|
|
|
|
|
import (
|
|
|
|
"fmt"
|
2020-04-10 19:26:38 +02:00
|
|
|
"path/filepath"
|
2017-04-26 03:10:10 +02:00
|
|
|
|
2021-05-17 21:17:09 +02:00
|
|
|
"github.com/hashicorp/terraform/internal/configs"
|
2020-04-10 19:26:38 +02:00
|
|
|
"github.com/hashicorp/terraform/internal/getproviders"
|
2021-05-17 19:11:06 +02:00
|
|
|
"github.com/hashicorp/terraform/internal/tfdiags"
|
2017-04-26 03:10:10 +02:00
|
|
|
"github.com/xlab/treeprint"
|
|
|
|
)
|
|
|
|
|
|
|
|
// ProvidersCommand is a Command implementation that prints out information
|
|
|
|
// about the providers used in the current configuration/state.
|
|
|
|
type ProvidersCommand struct {
|
|
|
|
Meta
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *ProvidersCommand) Help() string {
|
|
|
|
return providersCommandHelp
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *ProvidersCommand) Synopsis() string {
|
2020-10-24 01:55:32 +02:00
|
|
|
return "Show the providers required for this configuration"
|
2017-04-26 03:10:10 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
func (c *ProvidersCommand) Run(args []string) int {
|
2020-04-01 21:01:08 +02:00
|
|
|
args = c.Meta.process(args)
|
2018-11-21 15:35:27 +01:00
|
|
|
cmdFlags := c.Meta.defaultFlagSet("providers")
|
2017-04-26 03:10:10 +02:00
|
|
|
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()))
|
2017-04-26 03:10:10 +02:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2020-04-10 19:26:38 +02:00
|
|
|
configPath, err := ModulePath(cmdFlags.Args())
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(err.Error())
|
|
|
|
return 1
|
|
|
|
}
|
2017-04-26 03:10:10 +02:00
|
|
|
|
2020-04-10 19:26:38 +02:00
|
|
|
var diags tfdiags.Diagnostics
|
2018-03-28 00:31:05 +02:00
|
|
|
|
2020-04-10 19:26:38 +02:00
|
|
|
empty, err := configs.IsEmptyDir(configPath)
|
|
|
|
if err != nil {
|
|
|
|
diags = diags.Append(tfdiags.Sourceless(
|
|
|
|
tfdiags.Error,
|
|
|
|
"Error validating configuration directory",
|
|
|
|
fmt.Sprintf("Terraform encountered an unexpected error while verifying that the given configuration directory is valid: %s.", err),
|
|
|
|
))
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
if empty {
|
|
|
|
absPath, err := filepath.Abs(configPath)
|
2018-10-15 01:59:51 +02:00
|
|
|
if err != nil {
|
2020-04-10 19:26:38 +02:00
|
|
|
absPath = configPath
|
2018-10-15 01:59:51 +02:00
|
|
|
}
|
2020-04-10 19:26:38 +02:00
|
|
|
diags = diags.Append(tfdiags.Sourceless(
|
|
|
|
tfdiags.Error,
|
|
|
|
"No configuration files",
|
|
|
|
fmt.Sprintf("The directory %s contains no Terraform configuration files.", absPath),
|
|
|
|
))
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
2018-10-15 01:59:51 +02:00
|
|
|
|
2020-04-10 19:26:38 +02:00
|
|
|
config, configDiags := c.loadConfig(configPath)
|
|
|
|
diags = diags.Append(configDiags)
|
|
|
|
if configDiags.HasErrors() {
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
2017-04-26 03:10:10 +02:00
|
|
|
|
2020-04-10 19:26:38 +02:00
|
|
|
// Load the backend
|
|
|
|
b, backendDiags := c.Backend(&BackendOpts{
|
|
|
|
Config: config.Module.Backend,
|
|
|
|
})
|
|
|
|
diags = diags.Append(backendDiags)
|
|
|
|
if backendDiags.HasErrors() {
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
2017-04-26 03:10:10 +02:00
|
|
|
|
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
|
2021-08-24 21:28:12 +02:00
|
|
|
c.ignoreRemoteVersionConflict(b)
|
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
|
|
|
|
2020-04-10 19:26:38 +02:00
|
|
|
// Get the state
|
2020-06-16 18:23:15 +02:00
|
|
|
env, err := c.Workspace()
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Error selecting workspace: %s", err))
|
|
|
|
return 1
|
|
|
|
}
|
2020-04-10 19:26:38 +02:00
|
|
|
s, err := b.StateMgr(env)
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Failed to load state: %s", err))
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
if err := s.RefreshState(); err != nil {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Failed to load state: %s", err))
|
|
|
|
return 1
|
|
|
|
}
|
2017-04-26 03:10:10 +02:00
|
|
|
|
2020-06-09 19:32:56 +02:00
|
|
|
reqs, reqDiags := config.ProviderRequirementsByModule()
|
|
|
|
diags = diags.Append(reqDiags)
|
|
|
|
if diags.HasErrors() {
|
|
|
|
c.showDiagnostics(diags)
|
2020-04-10 19:26:38 +02:00
|
|
|
return 1
|
|
|
|
}
|
2017-04-26 03:10:10 +02:00
|
|
|
|
2020-04-10 19:26:38 +02:00
|
|
|
state := s.State()
|
2020-06-09 19:32:56 +02:00
|
|
|
var stateReqs getproviders.Requirements
|
2020-04-10 19:26:38 +02:00
|
|
|
if state != nil {
|
2020-06-09 19:32:56 +02:00
|
|
|
stateReqs = state.ProviderRequirements()
|
2020-04-10 19:26:38 +02:00
|
|
|
}
|
2017-04-26 03:10:10 +02:00
|
|
|
|
2020-04-10 19:26:38 +02:00
|
|
|
printRoot := treeprint.New()
|
2020-06-09 19:32:56 +02:00
|
|
|
c.populateTreeNode(printRoot, reqs)
|
2017-04-26 03:10:10 +02:00
|
|
|
|
2020-06-09 19:32:56 +02:00
|
|
|
c.Ui.Output("\nProviders required by configuration:")
|
2020-04-10 19:26:38 +02:00
|
|
|
c.Ui.Output(printRoot.String())
|
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
|
|
|
|
2020-06-09 19:32:56 +02:00
|
|
|
if len(stateReqs) > 0 {
|
|
|
|
c.Ui.Output("Providers required by state:\n")
|
|
|
|
for fqn := range stateReqs {
|
|
|
|
c.Ui.Output(fmt.Sprintf(" provider[%s]\n", fqn.String()))
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-04-10 19:26:38 +02:00
|
|
|
c.showDiagnostics(diags)
|
|
|
|
if diags.HasErrors() {
|
|
|
|
return 1
|
|
|
|
}
|
2017-04-26 03:10:10 +02:00
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
2020-06-09 19:32:56 +02:00
|
|
|
func (c *ProvidersCommand) populateTreeNode(tree treeprint.Tree, node *configs.ModuleRequirements) {
|
|
|
|
for fqn, dep := range node.Requirements {
|
2020-04-10 19:26:38 +02:00
|
|
|
versionsStr := getproviders.VersionConstraintsString(dep)
|
2017-04-26 03:10:10 +02:00
|
|
|
if versionsStr != "" {
|
|
|
|
versionsStr = " " + versionsStr
|
|
|
|
}
|
2020-06-09 19:32:56 +02:00
|
|
|
tree.AddNode(fmt.Sprintf("provider[%s]%s", fqn.String(), versionsStr))
|
|
|
|
}
|
|
|
|
for name, childNode := range node.Children {
|
|
|
|
branch := tree.AddBranch(fmt.Sprintf("module.%s", name))
|
|
|
|
c.populateTreeNode(branch, childNode)
|
2017-04-26 03:10:10 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
const providersCommandHelp = `
|
2021-02-22 15:25:56 +01:00
|
|
|
Usage: terraform [global options] providers [dir]
|
2017-04-26 03:10:10 +02:00
|
|
|
|
2020-06-09 19:32:56 +02:00
|
|
|
Prints out a tree of modules in the referenced configuration annotated with
|
|
|
|
their provider requirements.
|
2017-04-26 03:10:10 +02:00
|
|
|
|
2020-06-09 19:32:56 +02:00
|
|
|
This provides an overview of all of the provider requirements across all
|
|
|
|
referenced modules, as an aid to understanding why particular provider
|
|
|
|
plugins are needed and why particular versions are selected.
|
2017-04-26 03:10:10 +02:00
|
|
|
`
|