2023-05-02 10:33:06 -05:00
|
|
|
// Copyright (c) HashiCorp, Inc.
|
|
|
|
// SPDX-License-Identifier: MPL-2.0
|
|
|
|
|
2016-03-22 12:41:02 -05:00
|
|
|
package command
|
|
|
|
|
|
|
|
import (
|
|
|
|
"fmt"
|
|
|
|
"strings"
|
|
|
|
|
2021-05-17 14:00:50 -05:00
|
|
|
"github.com/hashicorp/terraform/internal/addrs"
|
2021-05-17 14:43:35 -05:00
|
|
|
"github.com/hashicorp/terraform/internal/states"
|
2021-05-17 12:11:06 -05:00
|
|
|
"github.com/hashicorp/terraform/internal/tfdiags"
|
2016-03-22 12:41:02 -05:00
|
|
|
"github.com/mitchellh/cli"
|
|
|
|
)
|
|
|
|
|
|
|
|
// StateListCommand is a Command implementation that lists the resources
|
|
|
|
// within a state file.
|
|
|
|
type StateListCommand struct {
|
2017-03-01 09:10:47 -06:00
|
|
|
Meta
|
2017-02-28 12:13:03 -06:00
|
|
|
StateMeta
|
2016-03-22 12:41:02 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
func (c *StateListCommand) Run(args []string) int {
|
2020-04-01 14:01:08 -05:00
|
|
|
args = c.Meta.process(args)
|
2019-04-15 11:22:07 -05:00
|
|
|
var statePath string
|
2018-11-21 08:35:27 -06:00
|
|
|
cmdFlags := c.Meta.defaultFlagSet("state list")
|
2019-04-15 11:22:07 -05:00
|
|
|
cmdFlags.StringVar(&statePath, "state", "", "path")
|
2018-10-17 16:01:15 -05:00
|
|
|
lookupId := cmdFlags.String("id", "", "Restrict output to paths with a resource having the specified ID.")
|
2016-03-22 12:41:02 -05:00
|
|
|
if err := cmdFlags.Parse(args); err != nil {
|
2019-08-16 07:31:21 -05:00
|
|
|
c.Ui.Error(fmt.Sprintf("Error parsing command-line flags: %s\n", err.Error()))
|
2016-03-22 12:41:02 -05:00
|
|
|
return cli.RunResultHelp
|
|
|
|
}
|
|
|
|
args = cmdFlags.Args()
|
|
|
|
|
2019-04-15 11:22:07 -05:00
|
|
|
if statePath != "" {
|
|
|
|
c.Meta.statePath = statePath
|
|
|
|
}
|
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
// Load the backend
|
2018-03-27 17:31:05 -05:00
|
|
|
b, backendDiags := c.Backend(nil)
|
|
|
|
if backendDiags.HasErrors() {
|
|
|
|
c.showDiagnostics(backendDiags)
|
2017-01-18 22:50:45 -06:00
|
|
|
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 15:43:56 -06:00
|
|
|
// This is a read-only command
|
2021-08-24 14:28:12 -05: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 15:43:56 -06:00
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
// Get the state
|
2020-06-16 11:23:15 -05:00
|
|
|
env, err := c.Workspace()
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Error selecting workspace: %s", err))
|
|
|
|
return 1
|
|
|
|
}
|
2018-10-17 16:01:15 -05:00
|
|
|
stateMgr, err := b.StateMgr(env)
|
2017-01-18 22:50:45 -06:00
|
|
|
if err != nil {
|
2018-10-22 08:52:53 -05:00
|
|
|
c.Ui.Error(fmt.Sprintf(errStateLoadingState, err))
|
2017-01-18 22:50:45 -06:00
|
|
|
return 1
|
2016-03-22 12:41:02 -05:00
|
|
|
}
|
2018-10-17 16:01:15 -05:00
|
|
|
if err := stateMgr.RefreshState(); err != nil {
|
2019-04-15 11:22:07 -05:00
|
|
|
c.Ui.Error(fmt.Sprintf("Failed to load state: %s", err))
|
2017-02-21 22:35:43 -06:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2018-10-17 16:01:15 -05:00
|
|
|
state := stateMgr.State()
|
|
|
|
if state == nil {
|
2020-12-01 11:34:50 -06:00
|
|
|
c.Ui.Error(errStateNotFound)
|
2016-03-22 12:41:02 -05:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2019-03-15 21:51:26 -05:00
|
|
|
var addrs []addrs.AbsResourceInstance
|
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
if len(args) == 0 {
|
|
|
|
addrs, diags = c.lookupAllResourceInstanceAddrs(state)
|
|
|
|
} else {
|
|
|
|
addrs, diags = c.lookupResourceInstanceAddrs(state, args...)
|
|
|
|
}
|
|
|
|
if diags.HasErrors() {
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
2016-03-22 12:41:02 -05:00
|
|
|
}
|
|
|
|
|
2019-03-15 21:51:26 -05:00
|
|
|
for _, addr := range addrs {
|
|
|
|
if is := state.ResourceInstance(addr); is != nil {
|
2018-10-17 16:01:15 -05:00
|
|
|
if *lookupId == "" || *lookupId == states.LegacyInstanceObjectID(is.Current) {
|
2019-03-15 21:51:26 -05:00
|
|
|
c.Ui.Output(addr.String())
|
2018-02-26 12:54:48 -06:00
|
|
|
}
|
2016-03-22 12:41:02 -05:00
|
|
|
}
|
2018-10-17 16:01:15 -05:00
|
|
|
}
|
2016-03-22 12:41:02 -05:00
|
|
|
|
2019-03-15 21:51:26 -05:00
|
|
|
c.showDiagnostics(diags)
|
|
|
|
|
2016-03-22 12:41:02 -05:00
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *StateListCommand) Help() string {
|
|
|
|
helpText := `
|
2021-02-22 08:25:56 -06:00
|
|
|
Usage: terraform [global options] state list [options] [address...]
|
2016-03-22 12:41:02 -05:00
|
|
|
|
|
|
|
List resources in the Terraform state.
|
|
|
|
|
2019-03-15 21:51:26 -05:00
|
|
|
This command lists resource instances in the Terraform state. The address
|
|
|
|
argument can be used to filter the instances by resource or module. If
|
|
|
|
no pattern is given, all resource instances are listed.
|
2016-03-22 12:41:02 -05:00
|
|
|
|
2019-03-15 21:51:26 -05:00
|
|
|
The addresses must either be module addresses or absolute resource
|
|
|
|
addresses, such as:
|
|
|
|
aws_instance.example
|
|
|
|
module.example
|
|
|
|
module.example.module.child
|
|
|
|
module.example.aws_instance.example
|
2016-03-22 12:41:02 -05:00
|
|
|
|
2019-03-15 21:51:26 -05:00
|
|
|
An error will be returned if any of the resources or modules given as
|
|
|
|
filter addresses do not exist in the state.
|
2016-03-22 12:41:02 -05:00
|
|
|
|
|
|
|
Options:
|
|
|
|
|
|
|
|
-state=statefile Path to a Terraform state file to use to look
|
2019-03-15 21:51:26 -05:00
|
|
|
up Terraform-managed resources. By default, Terraform
|
|
|
|
will consult the state of the currently-selected
|
|
|
|
workspace.
|
2016-03-22 12:41:02 -05:00
|
|
|
|
2019-03-15 21:51:26 -05:00
|
|
|
-id=ID Filters the results to include only instances whose
|
|
|
|
resource types have an attribute named "id" whose value
|
|
|
|
equals the given id string.
|
2018-02-26 12:54:48 -06:00
|
|
|
|
2016-03-22 12:41:02 -05:00
|
|
|
`
|
|
|
|
return strings.TrimSpace(helpText)
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *StateListCommand) Synopsis() string {
|
|
|
|
return "List resources in the state"
|
|
|
|
}
|
|
|
|
|
|
|
|
const errStateLoadingState = `Error loading the state: %[1]s
|
|
|
|
|
|
|
|
Please ensure that your Terraform state exists and that you've
|
|
|
|
configured it properly. You can use the "-state" flag to point
|
|
|
|
Terraform at another state file.`
|
|
|
|
|
|
|
|
const errStateNotFound = `No state file was found!
|
|
|
|
|
|
|
|
State management commands require a state file. Run this command
|
|
|
|
in a directory where Terraform has been run or use the -state flag
|
|
|
|
to point the command to a specific state location.`
|