Deployment Diagnostics Built for the CLI and AI Agents
Rapids now reports a truthful, machine-readable deployment state with a typed reason, plus APIs for logs, revisions and events — so a script or coding agent can diagnose a failed deploy without opening the dashboard.
What's changed
- Deployment status is machine-readable, with typed detail explaining exactly what went wrong
- New API endpoints for container logs, revisions and events
- Registry credentials are attached automatically when you deploy from your private registry
- A registry context endpoint and push preflight tell you where to push and whether it will succeed
- POST /serverless accepts an Idempotency-Key, so a retried create never produces a second container
- A container in a degraded state can now be edited to fix it, instead of being stuck