pulumi config cp
Copy config to another stack
Synopsis
Copies the config from the current stack to the destination stack. If key
is omitted,
then all of the config from the current stack will be copied to the destination stack.
pulumi config cp [key] [flags]
Options
-d, --dest string The name of the new stack to copy the config to
-h, --help help for cp
--path The key contains a path to a property in a map or list to set
Options inherited from parent commands
--color string Colorize output. Choices are: always, never, raw, auto (default "auto")
--config-file string Use the configuration values in the specified file rather than detecting the file name
-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
-s, --stack string The name of the stack to operate on. Defaults to the current stack
--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 config - Manage configuration
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.