pulumi stack history events retrieves update engine events

Introduced 2026-05-18 · score 0.96

HOW TO USE IT

When debugging an update stored in Pulumi Cloud, retrieve its engine events with `pulumi stack history events <update-id>`. Use `--all` for every event or `--count <N>` for at least N; those options are mutually exclusive.

WHY THIS HELPS

Debug a Pulumi Cloud update by inspecting its engine events.

REQUIREMENTS AND LIMITATIONS

• Version: v3.241.0
• <update-id> (required): Identifies the update whose engine events to retrieve.
• --all: Return every event for the update; mutually exclusive with `--count`.
• --count <N>: Fetch enough pages to return at least N events; mutually exclusive with `--all`.
• --event-type <code>: Filter by numeric Pulumi Cloud engine-event type code; repeatable.
• --urn <resource-urn>: Filter events to one resource URN.
• --include-non-activated: Include events not yet marked activated.
• --output <format>: Select `default` or `json` output; JSON emits raw engine event payloads.
• --stack <stack>: Select the stack to operate on; defaults to the current stack.
• Prerequisite: The command requires the Pulumi Cloud backend.
• Docs conflict: The current CLI reference is generated for v3.268.0 and includes `--summary`, which is absent from the v3.241.0 implementation description. Do not rely on that newer option for this card.

FIRST-PARTY EVIDENCE

• https://github.com/pulumi/pulumi/releases/tag/v3.241.0
• https://github.com/pulumi/pulumi/pull/23109
• https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_history_events/

Check the installed version and the source before using it. Entry JSON

Report a problem with this card