2024-02-08 04:48:59 -05:00
|
|
|
// Copyright (c) The OpenTofu Authors
|
|
|
|
|
// SPDX-License-Identifier: MPL-2.0
|
|
|
|
|
// Copyright (c) 2023 HashiCorp, Inc.
|
2023-05-02 11:33:06 -04:00
|
|
|
// SPDX-License-Identifier: MPL-2.0
|
|
|
|
|
|
2017-01-18 23:50:45 -05:00
|
|
|
package command
|
|
|
|
|
|
|
|
|
|
import (
|
2018-10-18 15:41:05 -04:00
|
|
|
"bytes"
|
statemgr+remote: context.Context parameters
This extends statemgr.Persistent, statemgr.Locker and remote.Client to
all expect context.Context parameters, and then updates all of the existing
implementations of those interfaces to support them.
All of the calls to statemgr.Persistent and statemgr.Locker methods outside
of tests are consistently context.TODO() for now, because the caller
landscape of these interfaces has some complications:
1. statemgr.Locker is also used by the clistate package for its state
implementation that was derived from statemgr.Filesystem's predecessor,
even though what clistate manages is not actually "state" in the sense
of package statemgr. The callers of that are not yet ready to provide
real contexts.
In a future commit we'll either need to plumb context through to all of
the clistate callers, or continue the effort to separate statemgr from
clistate by introducing a clistate-specific "locker" API for it
to use instead.
2. We call statemgr.Persistent and statemgr.Locker methods in situations
where the active context might have already been cancelled, and so we'll
need to make sure to ignore cancellation when calling those.
This is mainly limited to PersistState and Unlock, since both need to
be able to complete after a cancellation, but there are various
codepaths that perform a Lock, Refresh, Persist, Unlock sequence and so
it isn't yet clear where is the best place to enforce the invariant that
Persist and Unlock must not be called with a cancelable context. We'll
deal with that more in subsequent commits.
Within the various state manager and remote client implementations the
contexts _are_ wired together as best as possible with how these subsystems
are already laid out, and so once we deal with the problems above and make
callers provide suitable contexts they should be able to reach all of the
leaf API clients that might want to generate OpenTelemetry traces.
Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
2025-07-07 19:57:57 -04:00
|
|
|
"context"
|
2017-01-18 23:50:45 -05:00
|
|
|
"fmt"
|
|
|
|
|
"strings"
|
|
|
|
|
|
2026-03-09 06:25:18 -04:00
|
|
|
"github.com/mitchellh/cli"
|
|
|
|
|
"github.com/opentofu/opentofu/internal/command/arguments"
|
|
|
|
|
"github.com/opentofu/opentofu/internal/command/views"
|
2024-03-04 09:25:14 -05:00
|
|
|
"github.com/opentofu/opentofu/internal/encryption"
|
2023-09-20 07:35:35 -04:00
|
|
|
"github.com/opentofu/opentofu/internal/states/statefile"
|
|
|
|
|
"github.com/opentofu/opentofu/internal/states/statemgr"
|
2026-03-26 11:19:27 -04:00
|
|
|
"github.com/opentofu/opentofu/internal/tfdiags"
|
2017-01-18 23:50:45 -05:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
// StatePullCommand is a Command implementation that shows a single resource.
|
|
|
|
|
type StatePullCommand struct {
|
2017-03-01 10:10:47 -05:00
|
|
|
Meta
|
2017-01-18 23:50:45 -05:00
|
|
|
StateMeta
|
|
|
|
|
}
|
|
|
|
|
|
2026-03-09 06:25:18 -04:00
|
|
|
func (c *StatePullCommand) Run(rawArgs []string) int {
|
2025-04-30 11:28:19 -04:00
|
|
|
ctx := c.CommandContext()
|
|
|
|
|
|
2026-03-09 06:25:18 -04:00
|
|
|
common, rawArgs := arguments.ParseView(rawArgs)
|
|
|
|
|
c.View.Configure(common)
|
|
|
|
|
// Because the legacy UI was using println to show diagnostics and the new view is using, by default, print,
|
|
|
|
|
// in order to keep functional parity, we setup the view to add a new line after each diagnostic.
|
|
|
|
|
c.View.DiagsWithNewline()
|
|
|
|
|
|
|
|
|
|
// Parse and validate flags
|
|
|
|
|
args, closer, diags := arguments.ParseStatePull(rawArgs)
|
|
|
|
|
defer closer()
|
|
|
|
|
|
|
|
|
|
// Instantiate the view, even if there are flag errors, so that we render
|
|
|
|
|
// diagnostics according to the desired view
|
|
|
|
|
view := views.NewState(args.ViewOptions, c.View)
|
|
|
|
|
if diags.HasErrors() {
|
|
|
|
|
view.Diagnostics(diags)
|
|
|
|
|
return cli.RunResultHelp
|
2017-01-18 23:50:45 -05:00
|
|
|
}
|
|
|
|
|
|
2026-03-31 07:22:31 -04:00
|
|
|
c.Meta.variableArgs = args.Vars.All()
|
2026-03-09 06:25:18 -04:00
|
|
|
|
2025-04-30 11:28:19 -04:00
|
|
|
if diags := c.Meta.checkRequiredVersion(ctx); diags != nil {
|
2026-03-09 06:25:18 -04:00
|
|
|
view.Diagnostics(diags)
|
2022-03-31 13:42:42 -04:00
|
|
|
return 1
|
|
|
|
|
}
|
|
|
|
|
|
2024-03-07 08:55:57 -05:00
|
|
|
// Load the encryption configuration
|
2025-04-30 11:28:19 -04:00
|
|
|
enc, encDiags := c.Encryption(ctx)
|
2024-03-07 08:55:57 -05:00
|
|
|
if encDiags.HasErrors() {
|
2026-03-09 06:25:18 -04:00
|
|
|
view.Diagnostics(encDiags)
|
2024-03-07 08:55:57 -05:00
|
|
|
return 1
|
|
|
|
|
}
|
|
|
|
|
|
2017-01-18 23:50:45 -05:00
|
|
|
// Load the backend
|
2025-04-30 11:28:19 -04:00
|
|
|
b, backendDiags := c.Backend(ctx, nil, enc.State())
|
2018-03-27 18:31:05 -04:00
|
|
|
if backendDiags.HasErrors() {
|
2026-03-09 06:25:18 -04:00
|
|
|
view.Diagnostics(backendDiags)
|
2017-01-18 23:50:45 -05: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 16:43:56 -05:00
|
|
|
// This is a read-only command
|
2021-08-24 15:28:12 -04: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 16:43:56 -05:00
|
|
|
|
2018-11-13 19:48:59 -05:00
|
|
|
// Get the state manager for the current workspace
|
2025-04-30 11:28:19 -04:00
|
|
|
env, err := c.Workspace(ctx)
|
2020-06-16 12:23:15 -04:00
|
|
|
if err != nil {
|
2026-03-26 11:19:27 -04:00
|
|
|
view.Diagnostics(diags.Append(tfdiags.Sourceless(
|
|
|
|
|
tfdiags.Error,
|
|
|
|
|
"Error selecting workspace",
|
|
|
|
|
err.Error(),
|
|
|
|
|
)))
|
2020-06-16 12:23:15 -04:00
|
|
|
return 1
|
|
|
|
|
}
|
2025-05-06 16:50:41 -04:00
|
|
|
stateMgr, err := b.StateMgr(ctx, env)
|
2017-01-18 23:50:45 -05:00
|
|
|
if err != nil {
|
2026-03-09 06:25:18 -04:00
|
|
|
view.StateLoadingFailure(err.Error())
|
2017-01-18 23:50:45 -05:00
|
|
|
return 1
|
|
|
|
|
}
|
statemgr+remote: context.Context parameters
This extends statemgr.Persistent, statemgr.Locker and remote.Client to
all expect context.Context parameters, and then updates all of the existing
implementations of those interfaces to support them.
All of the calls to statemgr.Persistent and statemgr.Locker methods outside
of tests are consistently context.TODO() for now, because the caller
landscape of these interfaces has some complications:
1. statemgr.Locker is also used by the clistate package for its state
implementation that was derived from statemgr.Filesystem's predecessor,
even though what clistate manages is not actually "state" in the sense
of package statemgr. The callers of that are not yet ready to provide
real contexts.
In a future commit we'll either need to plumb context through to all of
the clistate callers, or continue the effort to separate statemgr from
clistate by introducing a clistate-specific "locker" API for it
to use instead.
2. We call statemgr.Persistent and statemgr.Locker methods in situations
where the active context might have already been cancelled, and so we'll
need to make sure to ignore cancellation when calling those.
This is mainly limited to PersistState and Unlock, since both need to
be able to complete after a cancellation, but there are various
codepaths that perform a Lock, Refresh, Persist, Unlock sequence and so
it isn't yet clear where is the best place to enforce the invariant that
Persist and Unlock must not be called with a cancelable context. We'll
deal with that more in subsequent commits.
Within the various state manager and remote client implementations the
contexts _are_ wired together as best as possible with how these subsystems
are already laid out, and so once we deal with the problems above and make
callers provide suitable contexts they should be able to reach all of the
leaf API clients that might want to generate OpenTelemetry traces.
Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
2025-07-07 19:57:57 -04:00
|
|
|
if err := stateMgr.RefreshState(context.TODO()); err != nil {
|
2026-03-09 06:25:18 -04:00
|
|
|
view.Diagnostics(diags.Append(fmt.Errorf("Failed to refresh state: %s", err)))
|
2017-01-18 23:50:45 -05:00
|
|
|
return 1
|
|
|
|
|
}
|
|
|
|
|
|
2018-11-13 19:48:59 -05:00
|
|
|
// Get a statefile object representing the latest snapshot
|
|
|
|
|
stateFile := statemgr.Export(stateMgr)
|
2017-03-01 15:47:36 -05:00
|
|
|
|
2018-11-13 19:48:59 -05:00
|
|
|
if stateFile != nil { // we produce no output if the statefile is nil
|
|
|
|
|
var buf bytes.Buffer
|
2024-03-07 08:55:57 -05:00
|
|
|
err = statefile.Write(stateFile, &buf, encryption.StateEncryptionDisabled()) // Don't encrypt to stdout
|
2018-11-13 19:48:59 -05:00
|
|
|
if err != nil {
|
2026-03-09 06:25:18 -04:00
|
|
|
view.Diagnostics(diags.Append(fmt.Errorf("Failed to write state: %s", err)))
|
2018-11-13 19:48:59 -05:00
|
|
|
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 17:24:45 -04:00
|
|
|
|
2026-03-09 06:25:18 -04:00
|
|
|
view.PrintPulledState(buf.String())
|
2018-10-18 15:41:05 -04:00
|
|
|
}
|
2017-01-18 23:50:45 -05:00
|
|
|
|
|
|
|
|
return 0
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
func (c *StatePullCommand) Help() string {
|
|
|
|
|
helpText := `
|
2023-09-21 08:38:46 -04:00
|
|
|
Usage: tofu [global options] state pull [options]
|
2017-01-18 23:50:45 -05:00
|
|
|
|
2021-01-22 10:30:01 -05:00
|
|
|
Pull the state from its location, upgrade the local copy, and output it
|
|
|
|
|
to stdout.
|
2017-01-18 23:50:45 -05:00
|
|
|
|
|
|
|
|
This command "pulls" the current state and outputs it to stdout.
|
2023-09-21 08:38:46 -04:00
|
|
|
As part of this process, OpenTofu will upgrade the state format of the
|
2021-01-22 10:30:01 -05:00
|
|
|
local copy to the current version.
|
|
|
|
|
|
2017-01-18 23:50:45 -05: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.
|
|
|
|
|
|
2024-07-11 11:00:18 -04:00
|
|
|
Options:
|
|
|
|
|
|
|
|
|
|
-var 'foo=bar' Set a value for one of the input variables in the root
|
|
|
|
|
module of the configuration. Use this option more than
|
|
|
|
|
once to set more than one variable.
|
|
|
|
|
|
|
|
|
|
-var-file=filename Load variable values from the given file, in addition
|
|
|
|
|
to the default files terraform.tfvars and *.auto.tfvars.
|
|
|
|
|
Use this option more than once to include more than one
|
|
|
|
|
variables file.
|
2017-01-18 23:50:45 -05:00
|
|
|
`
|
|
|
|
|
return strings.TrimSpace(helpText)
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
func (c *StatePullCommand) Synopsis() string {
|
|
|
|
|
return "Pull current state and output to stdout"
|
|
|
|
|
}
|