pulumi env schedule new | CLI commands

Create a new scheduled action on an environment.

Synopsis

[EXPERIMENTAL] Create a new scheduled action on an environment

This command schedules a secret rotation against the environment. Use –cron to schedule a recurring rotation or –once to schedule a single rotation at a specific time (ISO 8601 / RFC 3339).

Only one schedule per environment is currently supported; creating a second schedule will fail. The minimum cron interval is once per day.

pulumi env schedule new [<org-name>/][<project-name>/]<environment-name> [flags]

Options

      --cron string   a cron expression for a recurring schedule (minimum interval: once daily)
  -h, --help          help for new
      --once string   an ISO 8601 / RFC 3339 timestamp in the future for a one-time schedule

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
      --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// for remote collectors
      --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

• pulumi env schedule - Manage environment scheduled actions