fix(deploy): use live Coolify webhook route - #13
Merged
Conversation
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.
Problem and outcome
The checked-in deployment controller allowed the wrong manual Coolify webhook path. The running Coolify 4.0.0-beta.470 instance mounts the handler at /webhooks/source/github/events/manual; the previous /source/github/events/manual target returns HTTP 419. This change updates the exact fail-closed allowlist and the cutover documentation.
Compatibility, security, and migrations
No A2A, MCP, API, database, or migration changes. The controller still accepts only one exact AgoraHub webhook target. The generic Coolify deploy API remains blocked at Cloudflare Access. COOLIFY_CD_ENABLED remains false during this PR.
Verification
Commands and results: