pulumi cloud api calls Pulumi Cloud API endpoints with pagination
Introduced 2026-05-05 · score 0.95
HOW TO USE IT
When inspecting Pulumi Cloud API data, use the release’s `pulumi cloud api` command to call an endpoint; add `--paginate` to follow continuation cursors and `--emit-events` to report progress to stderr. The current docs describe a differently named command, so its flag details are not applied here.
pulumi cloud api <op-or-path> [documented request flags]WHY THIS HELPS
Inspect Pulumi Cloud API data while debugging or maintaining a Pulumi project.
REQUIREMENTS AND LIMITATIONS
- Version: v3.235.0
- <op-or-path> (required): Endpoint operation or path; argument syntax and resolution details not found for this command.
- --field: Request flag; value syntax and behavior not found for this command.
- --header: Request flag; value syntax and behavior not found for this command.
- --input: Request flag; value syntax and behavior not found for this command.
- --body: Request flag; value syntax and behavior not found for this command.
- --format: Used for content negotiation; accepted values not found for this command.
- --dry-run: Request flag; behavior details not found for this command.
- --paginate: Follows continuation cursors and accumulates items into a single JSON envelope.
- --emit-events: Surfaces page, complete, truncated, partial_failure, and cancelled events to stderr.
- Pagination follows continuation cursors and accumulates items into a single JSON envelope.
- `--emit-events` surfaces page, complete, truncated, partial_failure, and cancelled events to stderr.
- Docs conflict: The current Pulumi CLI documentation describes `pulumi api`, not the release’s `pulumi cloud api`; its syntax and flag details may differ and were not applied. https://www.pulumi.com/docs/iac/cli/api/
FIRST-PARTY EVIDENCE
Check the installed version and the source before using it. Entry JSON