pulumi refresh

Refresh the resources in a stack

Options

NameDescription
--color <mode>Colorize output. Choices are: always, never, raw, auto (default "auto")
-C, --cwd <path>Run pulumi as if it had been started in another directory
--disable-integrity-checkingDisable integrity checking of checkpoint files
-e, --emojiEnable emojis in the output
--logflowFlow log settings to child processes (like plugins)
--logtostderrLog to stderr instead of to files
--non-interactiveDisable interactive mode for all commands
--profilingEmit 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
--config-file <file>Use the configuration values in the specified file rather than detecting the file name
-d, --debugPrint detailed debugging output during resource operations
--diffDisplay operation as a rich diff showing the overall change
-m, --message <message>Optional message to associate with the destroy operation
-p, --parallel <int>Allow P resource operations to run in parallel at once (1 for no parallelism). Defaults to unbounded. (default 2147483647)
-f, --skip-previewDo not perform a preview before performing the destroy
-s, --stack <stack-name>The name of the stack to operate on. Defaults to the current stack
-y, --yes
  • Dangerous 💥
--suppress-permalink <bool>Suppress display of the state permalink
-t, --target <stringArray>Specify a single resource URN to destroy. All resources necessary to destroy this target will also be destroyed. Multiple resources can be specified using: --target urn1 --target urn2
-j, --jsonSerialize the refresh diffs, operations, and overall output as JSON
--expect-no-changesReturn an error if any changes occur during this update
--show-replacement-stepsShow detailed resource replacement creates and deletes instead of a single step
--show-samesShow resources that needn't be updated because they haven't changed, alongside those that do
--suppress-outputsSuppress display of stack outputs (in case they contain sensitive values)