chore(drive): record the pinned deployment-logs HTTP contract - #189
chore(drive): record the pinned deployment-logs HTTP contract#189wmadden-electric wants to merge 1 commit into
Conversation
The platform endpoint shipped (prisma/pdp-control-plane#4886): plain GET returns one NDJSON page ending in a terminal record with a resume cursor. Updates the S8 deferred entry so the service-logs follow-up slice can start from the pinned contract. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
Important Review available on request
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
commit: |
|
Deployed: the production management API now serves the paged contract ( |
|
Redundant: #181 already implements service logs against this contract and carries the context. One useful fact from here: pdp-control-plane#4886 deployed to production today — the paged GET is live (verified against https://api.prisma.io/v1/doc). |
Purpose of change
The platform endpoint for deployment logs shipped: prisma/pdp-control-plane#4886. This updates the S8 deferred entry (
service logs) with the pinned contract so the follow-up slice can come off the shelf.What's changed
.drive/projects/prisma-cli-v8/deferred.md: the R-S8-5 entry now records the merged contract — plain authenticatedGET /v1/deployments/{deploymentId}/logsreturns one NDJSON page (unchangedlog/terminalrecord shapes) ending in a terminal record with a resumecursor;tail/from_start/cursorquery params; WebSocket live tail unchanged on the same path; SDK exposure arrives with the next management-api production deploy.🤖 Generated with Claude Code