pulumi stack import
Import a deployment from standard in into an existing stack
Synopsis
Import a deployment from standard in into an existing stack.
A deployment that was exported from a stack using pulumi stack export
and
hand-edited to correct inconsistencies due to failed updates, manual changes
to cloud resources, etc. can be reimported to the stack using this command.
The updated deployment will be read from standard in.
pulumi stack import [flags]
Options
--file string A filename to read stack input from
-f, --force Force the import to occur, even if apparent errors are discovered beforehand (not recommended)
-h, --help help for import
-s, --stack string The name of the stack to operate on. Defaults to the current stack
Options inherited from parent commands
--color string Colorize output. Choices are: always, never, raw, auto (default "auto")
-C, --cwd string Run pulumi as if it had been started in another directory
--disable-integrity-checking Disable integrity checking of checkpoint files
-e, --emoji Enable emojis in the output
-Q, --fully-qualify-stack-names Show fully-qualified stack names
--logflow Flow log settings to child processes (like plugins)
--logtostderr Log to stderr instead of to files
--memprofilerate int Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
--non-interactive Disable interactive mode for all commands
--profiling string Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
--tracing file: Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
-v, --verbose int Enable verbose logging (e.g., v=3); anything >3 is very verbose
SEE ALSO
- pulumi stack - Manage stacks and view stack state
Auto generated by spf13/cobra on 8-Oct-2024
Thank you for your feedback!
If you have a question about how to use Pulumi, reach out in Community Slack.
Open an issue on GitHub to report a problem or suggest an improvement.