Skip to content

fix(dotnet-service): the Coolify deploy called a verb Coolify refuses - #1

Merged
ruehowl merged 1 commit into
mainfrom
claude/dotnet-microservices-baseline-odjp47
Aug 23, 2026
Merged

ruehowl merged 1 commit into
mainfrom
claude/dotnet-microservices-baseline-odjp47

Conversation

@ruehowl

@ruehowl ruehowl commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

The defect

deploy-coolify issued GET /api/v1/deploy.

Coolify still routes that path — but to OtherController::post_required, which answers:

405  {"message": "This endpoint has changed to a POST request."}
Allow: POST

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, reporting Coolify returned HTTP 405 with 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 only POST /deploy.

The fix

  • GET → POST (with Content-Length: 0; the parameters are query-string, not a body).
  • Two statuses get their own message instead of the generic one:
    • 405 names the verb, so a future re-break is self-diagnosing.
    • 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 — which is exactly the failure that reads like a broken pipeline rather than a mis-scoped token.

Schema: connecting the two halves

coolifyUrl and coolifyAppUuid read 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):

value comes from shape
coolifyUrl instance-url template connection-anchor fact — no token read, nothing to revoke
COOLIFY_TOKEN deploy-application template TTL-bounded, ledgered per issuance
coolifyAppUuid the template's applicationUuid param —

Nothing 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

`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
ruehowl marked this pull request as ready for review August 23, 2026 12:34
@ruehowl
ruehowl merged commit 741a2fd into main Aug 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants