Examples
Verify a managed application deployment
Follow a reviewed application change from repository checks to a managed deployment without relying on cluster access.
Goal
Confirm that an approved pipeline application version reached its managed environment and that one bounded read or write behaves as documented.
Prerequisites
- an onboarded repository and environment;
- a merged application change with passing required checks;
- the deployment status surface supplied during onboarding;
- a non-destructive smoke request and expected result.
Steps
- Record the merged commit identifier and generated application version.
- Wait for the managed deployment status to report that exact version healthy.
- Authenticate with a workspace credential.
- Run the application's smallest owner-scoped read or idempotent smoke request.
- Compare the response with the example committed alongside the application.
- Record the version and result on the originating issue or pull request.
Expected result
The status surface and smoke response name the intended version. The request returns only records owned by the authenticated workspace and matches the documented response shape.
Failure modes
| Symptom | Check |
|---|---|
| Status shows an older version | Wait for the managed deployment or ask the operator to inspect the blocked stage |
| Authentication fails | Refresh the workspace credential; do not place it in an issue or log |
| Empty result | Confirm the workspace owns fixture data and that the query bounds include it |
| Contract differs | Stop promotion and correct the implementation or generated reference in a new pull request |
Reference
The data platform preview defines ownership and compatibility boundaries. The tickets walkthrough is a complete application-level example.