1. Docs
  2. Pulumi CLI
  3. Commands
  4. pulumi env init

pulumi env init

    Create an empty environment with the given name.

    Synopsis

    Create an empty environment with the given name, ready for editing

    This command creates an empty environment with the given name. It has no definition, but afterwards it can be edited using the edit command.

    To create an environment in an organization when logged in to the Pulumi Cloud, prefix the stack name with the organization name and a slash (e.g. ‘acmecorp/dev’).

    pulumi env init [<org-name>/]<environment-name> [flags]
    

    Options

      -f, --file -   the file to use to initialize the environment, if any. Pass - to read from standard input.
      -h, --help     help for init
    

    Options inherited from parent commands

          --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
      -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
          --env string                   The name of the environment to operate on.
      -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
          --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 6-May-2024
      Introducing Drift Detection, TTL Stacks, and Scheduled Deployments. Learn More.