Fork me on GitHub

pulumi refresh

Refresh the resources in a stack

Synopsis

Refresh the resources in a stack.

This command compares the current stack’s resource state with the state known to exist in the actual cloud provider. Any such changes are adopted into the current stack. Note that if the program text isn’t updated accordingly, subsequent updates may still appear to be out of synch with respect to the cloud provider’s source of truth.

The program to run is loaded from the project in the current directory. Use the -C or --cwd flag to use a different directory.

pulumi refresh [flags]

Options

      --analyzer stringSlice        Run one or more analyzers as part of this update
  -c, --color colors.Colorization   Colorize output. Choices are: always, never, raw, auto (default always)
  -d, --debug                       Print detailed debugging output during resource operations
      --diff                        Display operation as a rich diff showing the overall change
  -h, --help                        help for refresh
  -m, --message string              Optional message to associate with the update operation
      --non-interactive             Disable interactive mode
  -p, --parallel int                Allow P resource operations to run in parallel at once (<=1 for no parallelism)
      --show-replacement-steps      Show detailed resource replacement creates and deletes instead of a single step
      --show-sames                  Show resources that needn't be updated because they haven't changed, alongside those that do
      --skip-preview                Do not perform a preview before performing the refresh
  -s, --stack string                Choose a stack other than the currently selected one
  -y, --yes                         Automatically approve and perform the refresh after previewing it

Options inherited from parent commands

  -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 (default true)
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --tracing string               Emit tracing to a Zipkin-compatible tracing endpoint
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose

SEE ALSO

Auto generated by spf13/cobra on 14-Jun-2018