gateway-controller deployment push to platform-api fails with 400 due to APIConfiguration schema mismatch
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
When deployment_push_enabled = true, the gateway-controller's HTTP push to POST /api/internal/v1/apis/:apiId/gateway-deployments fails with HTTP 400:
"Invalid request body:
Key: 'DeploymentNotification.Configuration.Version' Error: required
Key: 'DeploymentNotification.Configuration.Spec.Name' Error: required
Key: 'DeploymentNotification.Configuration.Spec.Upstreams' Error: required"
Steps to Reproduce
- Start platform-api and gateway-controller with
deployment_push_enabled = true - Deploy any API via
ap gateway apply - Gateway-controller calls
POST /api/internal/v1/apis/:apiId/gateway-deployments - Platform-api returns 400
Expected Behavior
The deployment notification should be accepted by platform-api and the API deployment state should be recorded.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the gateway-controller request for POST /api/internal/v1/apis/:apiId/gateway-deployments with the platform-api APIConfiguration schema, starting from the deployment_push_enabled flow. Reproduce with ap gateway apply; done means the notification is accepted without HTTP 400 and the API deployment state is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100