2023-05-02 10:33:06 -05:00
|
|
|
// Copyright (c) HashiCorp, Inc.
|
|
|
|
// SPDX-License-Identifier: MPL-2.0
|
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
package command
|
|
|
|
|
|
|
|
import (
|
2018-10-18 14:41:05 -05:00
|
|
|
"bytes"
|
2017-01-18 22:50:45 -06:00
|
|
|
"fmt"
|
|
|
|
"strings"
|
|
|
|
|
2023-08-17 07:45:11 -05:00
|
|
|
"github.com/placeholderplaceholderplaceholder/opentf/internal/states/statefile"
|
|
|
|
"github.com/placeholderplaceholderplaceholder/opentf/internal/states/statemgr"
|
2017-01-18 22:50:45 -06:00
|
|
|
)
|
|
|
|
|
|
|
|
// StatePullCommand is a Command implementation that shows a single resource.
|
|
|
|
type StatePullCommand struct {
|
2017-03-01 09:10:47 -06:00
|
|
|
Meta
|
2017-01-18 22:50:45 -06:00
|
|
|
StateMeta
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *StatePullCommand) Run(args []string) int {
|
2020-04-01 14:01:08 -05:00
|
|
|
args = c.Meta.process(args)
|
2018-11-21 08:35:27 -06:00
|
|
|
cmdFlags := c.Meta.defaultFlagSet("state pull")
|
2017-01-18 22:50:45 -06: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()))
|
|
|
|
return 1
|
2017-01-18 22:50:45 -06:00
|
|
|
}
|
|
|
|
|
2022-03-31 12:42:42 -05:00
|
|
|
if diags := c.Meta.checkRequiredVersion(); diags != nil {
|
|
|
|
c.showDiagnostics(diags)
|
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
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
|
|
|
|
2018-11-13 18:48:59 -06:00
|
|
|
// Get the state manager for the current workspace
|
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-18 14:41:05 -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
|
|
|
|
}
|
2018-10-18 14:41:05 -05:00
|
|
|
if err := stateMgr.RefreshState(); err != nil {
|
2018-10-22 08:52:53 -05:00
|
|
|
c.Ui.Error(fmt.Sprintf("Failed to refresh state: %s", err))
|
2017-01-18 22:50:45 -06:00
|
|
|
return 1
|
|
|
|
}
|
|
|
|
|
2018-11-13 18:48:59 -06:00
|
|
|
// Get a statefile object representing the latest snapshot
|
|
|
|
stateFile := statemgr.Export(stateMgr)
|
2017-03-01 14:47:36 -06:00
|
|
|
|
2018-11-13 18:48:59 -06:00
|
|
|
if stateFile != nil { // we produce no output if the statefile is nil
|
|
|
|
var buf bytes.Buffer
|
|
|
|
err = statefile.Write(stateFile, &buf)
|
|
|
|
if err != nil {
|
|
|
|
c.Ui.Error(fmt.Sprintf("Failed to write state: %s", err))
|
|
|
|
return 1
|
|
|
|
}
|
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 16:24:45 -05:00
|
|
|
|
2018-11-13 18:48:59 -06:00
|
|
|
c.Ui.Output(buf.String())
|
2018-10-18 14:41:05 -05:00
|
|
|
}
|
2017-01-18 22:50:45 -06:00
|
|
|
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *StatePullCommand) Help() string {
|
|
|
|
helpText := `
|
2021-02-22 08:25:56 -06:00
|
|
|
Usage: terraform [global options] state pull [options]
|
2017-01-18 22:50:45 -06:00
|
|
|
|
2021-01-22 09:30:01 -06:00
|
|
|
Pull the state from its location, upgrade the local copy, and output it
|
|
|
|
to stdout.
|
2017-01-18 22:50:45 -06:00
|
|
|
|
|
|
|
This command "pulls" the current state and outputs it to stdout.
|
2021-01-22 09:30:01 -06:00
|
|
|
As part of this process, Terraform will upgrade the state format of the
|
|
|
|
local copy to the current version.
|
|
|
|
|
2017-01-18 22:50:45 -06:00
|
|
|
The primary use of this is for state stored remotely. This command
|
|
|
|
will still work with local state but is less useful for this.
|
|
|
|
|
|
|
|
`
|
|
|
|
return strings.TrimSpace(helpText)
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *StatePullCommand) Synopsis() string {
|
|
|
|
return "Pull current state and output to stdout"
|
|
|
|
}
|