Repository navigation
fix(dotnet-service): the Coolify deploy called a verb Coolify refuses - #1
Merged
Merged
Conversation
`deploy-coolify` issued `GET /api/v1/deploy`. Coolify still routes that path, but to `OtherController::post_required`, which answers 405 "This endpoint has changed to a POST request." So the step did not fail at the network and did not fail obscurely — it reached Coolify, was understood, and was refused, on every deploy this profile has ever been capable of running. Switched to POST, and gave the two diagnosable statuses their own messages: 405 names the verb, 401/403 names the missing `deploy` ability (Coolify guards this route with `api.ability:deploy`, so a read-only token fails here and nowhere earlier). Also connects the schema to the platform side. `coolifyUrl` and `coolifyAppUuid` read like values someone types in; they are not. A workspace with a Coolify connection now serves both from the integrations registry — the origin from the `instance-url` connection-anchor template, the credential from `deploy-application`, TTL-bounded and ledgered per issuance — so nothing here belongs in a repo secret. The descriptions say so. Stack 0.2.1 → 0.2.2: this changes what a published composition does. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JMrCB3sCZsboPbuVpvtpA1
ruehowl
marked this pull request as ready for review
August 23, 2026 12:34
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
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.
The defect
deploy-coolifyissuedGET /api/v1/deploy.Coolify still routes that path — but to
OtherController::post_required, which answers:So the step did not fail at the network, and did not fail obscurely. It reached Coolify, was understood, and was refused — on every deploy this profile has ever been capable of running. The
case "$code" in 2*)guard would have caught it, reportingCoolify returned HTTP 405with no hint as to why.Verified against Coolify's own
routes/api.php(Route::get('/deploy', [OtherController::class, 'post_required'])) and its current OpenAPI document, which declares onlyPOST /deploy.The fix
GET→POST(withContent-Length: 0; the parameters are query-string, not a body).deployability. Coolify guards this route withapi.ability:deploy, so aread-only token fails here and nowhere earlier — which is exactly the failure that reads like a broken pipeline rather than a mis-scoped token.Schema: connecting the two halves
coolifyUrlandcoolifyAppUuidread like values someone types in. They are not, any more.A workspace with a Coolify connection now serves both from the integrations registry (orun-cloud, same branch):
coolifyUrlinstance-urltemplateCOOLIFY_TOKENdeploy-applicationtemplatecoolifyAppUuidapplicationUuidparamNothing here belongs in a repo secret, and the descriptions now say so.
Version
0.2.1→0.2.2. This changes what a published composition does, not just what it documents.Verification
./scripts/verify.sh— 4 composition contracts structurally valid, all 4 export from the packed artifact, publish dry-run resolves. YAML parses.Not verified against a live Coolify instance — there isn't one to point at. The verb change rests on Coolify's route table and OpenAPI document rather than on an observed 200.
Generated by Claude Code