pulumi stack schedule commands manage deployment schedules
Introduced 2026-05-18 · score 0.98
HOW TO USE IT
When inspecting or maintaining a Pulumi stack’s scheduled deployment actions, use `pulumi stack schedule get|list|new|edit|remove` with the schedule ID and schedule-kind-specific options as needed.
pulumi stack schedule get <schedule-id> [--stack <stack>] [--output default|json]
pulumi stack schedule list [--stack <stack>] [--count <N>] [--output default|json]pulumi stack schedule new --kind raw --operation refresh --cron '0 */4 * * *'
pulumi stack schedule new --kind drift --cron '0 */4 * * *' --auto-remediate
pulumi stack schedule new --kind ttl --once 2027-01-01T00:00:00Z --delete-after-destroypulumi stack schedule edit <schedule-id> --cron '0 */6 * * *'
pulumi stack schedule remove <schedule-id> --yesWHY THIS HELPS
Inspect or maintain scheduled deployment actions for a Pulumi stack.
BEFORE THIS CHANGE
Before v3.241.0, these five schedule subcommands had not yet been added to the CLI, according to the release note.
REQUIREMENTS AND LIMITATIONS
- Version: v3.241.0
- <schedule-id> (required): Schedule identifier used by `get`, `edit`, and `remove`.
- --kind (required): Schedule kind: `raw`, `drift`, or `ttl`.
- --cron (required): UTC cron expression; required for drift and one of `--cron` or `--once` for raw. Mutually exclusive with `--once` for raw. On edit, valid for raw and drift.
- --once (required): ISO 8601 one-time execution timestamp; required for TTL and one of `--once` or `--cron` for raw. Mutually exclusive with `--cron` for raw. On edit, valid for raw and TTL.
- --operation (required): Raw-only Pulumi operation: `update`, `preview`, `refresh`, or `destroy`.
- --auto-remediate: Drift-only; automatically run a remediation update when drift is detected.
- --delete-after-destroy: TTL-only; delete the stack from Pulumi Cloud after successfully destroying its resources.
- --stack: Stack name; defaults to the current stack.
- --count: List at most the first N schedules; 0 (default) shows all.
- --output: Output format: `default` or `json`; defaults to `default`.
- --yes: For `new`, skip prompts and fail if required values are missing. For `remove`, skip confirmation prompts.
- --schedule-id argument to `edit` (required): Identifies the schedule to edit; only passed fields change, and other fields are preserved.
- Prerequisite: The stack must have deployment settings configured before creating a schedule.
- Docs conflict: The official CLI pages read are generated for Pulumi CLI v3.270.0, newer than the card’s v3.241.0 version. The pages document the same five subcommands; no differing behavior was established.
FIRST-PARTY EVIDENCE
- https://github.com/pulumi/pulumi/releases/tag/v3.241.0
- https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_get/ ; https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_list/
- https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_new/
- https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_edit/ ; https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_remove/
- https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_get/ ; https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_edit/ ; https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_remove/
- https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_new/ ; https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_edit/
- https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_get/
- https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_list/
- https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_new/ ; https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_remove/
- https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_schedule_edit/
Check the installed version and the source before using it. Entry JSON