Skip to main content
Sign in Dashboard Get started
  1. Docs
  2. pulumi stack schedule edit | CLI commands

pulumi stack schedule edit | CLI commands

Generated for Pulumi CLI v3.245.0.

    [EXPERIMENTAL] Update the configuration of a scheduled deployment action

    Synopsis

    [EXPERIMENTAL] Update the configuration of a scheduled deployment action.

    Only the fields you pass are changed; everything else is preserved. Each flag is only valid for a subset of kinds: raw: –cron, –once, –operation drift: –cron, –auto-remediate ttl: –once, –delete-after-destroy

    pulumi stack schedule edit <schedule-id> [flags]

    Examples

      # Switch a raw schedule to a different cron
  pulumi stack schedule edit <id> --cron '0 */6 * * *'

  # Enable auto-remediation on a drift schedule
  pulumi stack schedule edit <id> --auto-remediate

  # Disable delete-after-destroy on a TTL schedule
  pulumi stack schedule edit <id> --delete-after-destroy=false

    Options

          --auto-remediate         (drift only) Automatically run a remediation update when drift is detected
      --cron string            Cron expression for recurring executions, evaluated in UTC (raw and drift)
      --delete-after-destroy   (ttl only) Delete the stack from Pulumi Cloud after successfully destroying its resources
  -h, --help                   help for edit
      --once string            ISO 8601 timestamp for a one-time execution (raw and ttl)
      --operation string       (raw only) Pulumi operation to run. One of: update, preview, refresh, destroy
      --output string          Output format. Supported values are: default and json (default "default")
  -s, --stack string           The name of the stack to operate on. Defaults to the current stack

    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
  -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