pulumi new

Create a new Pulumi project


--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
-s, --stack <stack-name>The name of the stack to operate on. Defaults to the current stack
-y, --yes
  • Dangerous 💥
--secrets-provider <providerType>The type of the provider that should be used to encrypt and decrypt secrets (possible choices: default, passphrase, awskms, azurekeyvault, gcpkms, hashivault) (default "default")
-c, --config <stringArray>Config to save
--config-pathConfig keys contain a path to a property in a map or list to set
-d, --description <desc>The project description; if not specified, a prompt will request it
--dir <location>The location to place the generated project; if not specified, the current directory is used
-f, --force
  • Dangerous 💥
-g, --generate-onlyGenerate the project only; do not create a stack, save config, or install dependencies
-n, --name <projectName>The project name; if not specified, a prompt will request it
-o, --offlineUse locally cached templates without making any network requests