App Deployments (3a/N): customer catalog + deployment views (read-only)#217
Merged
Conversation
Increment 3a of the App Deployments epic. Read-only customer surface for
the managed app catalog and a user's own deployments.
- GET /api/v1/apps, GET /api/v1/apps/{id}: browse offered catalog apps
(compose exposed so the UI can render the deploy form).
- GET /api/v1/app-deployments, GET /api/v1/app-deployments/{id}: list/show
the authenticated user's deployments (ownership-checked); subscription_id
resolved from the line item for renewal.
- New api/apps.rs module (ApiApp / ApiAppDeployment) merged into the router.
- e2e customer test with a seed_app_deployment helper (app + cluster +
subscription/line-item + deployment); docs + changelog.
Ordering/lifecycle (billing) is increment 3b. Part of work/app-deployments.md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Increment 3a of the managed App Deployments epic (see
work/app-deployments.md). Builds on the DB foundation (#214) and admin API (#215). Read-only customer surface — no billing/ordering here (that's 3b).Endpoints
GET /api/v1/apps— browse offered catalog apps.GET /api/v1/apps/{id}— one offered app (404 if disabled/missing).GET /api/v1/app-deployments— the authenticated user's deployments.GET /api/v1/app-deployments/{id}— one of the user's deployments (ownership-checked).Notes
ApiAppexposes thecomposeYAML so the client can render the deploy form (ports/env).ApiAppDeploymentsurfaces name, hostname, status, desired state, and the billingsubscription_id(resolved from the line item, for renewal).api/apps.rsmodule merged into the router.Tests / docs
seed_app_deploymenthelper (seeds app + cluster + subscription/line-item + deployment): catalog listing/get, deployment listing/get, ownership 404.Next
3b) ordering/lifecycle: create deployment (validate config vs compose env schema → subscription + line item + invoice), delete/stop/start · 4) operator reconcile · 5) seed relay + Blossom.