pulumi config set

Set configuration value

Synopsis

Configuration values can be accessed when a stack is being deployed and used to configure behavior. If a value is not present on the command line, pulumi will prompt for the value. Multi-line values may be set by piping a file to standard in.

The --path flag can be used to set a value inside a map or list:

- `pulumi config set --path names[0] a` will set the value to a list with the first item `a`.
- `pulumi config set --path parent.nested value` will set the value of `parent` to a map `nested: value`.
- `pulumi config set --path '["parent.name"].["nested.name"]' value` will set the value of 
`parent.name` to a map `nested.name: value`.
pulumi config set <key> [value] [flags]

Options

  -h, --help        help for set
      --path        The key contains a path to a property in a map or list to set
      --plaintext   Save the value as plaintext (unencrypted)
      --secret      Encrypt the value instead of storing it in plaintext

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
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --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

Auto generated by spf13/cobra on 7-Aug-2020