kayx23 opened a new pull request, #14132:
URL: https://github.com/apache/apisix/pull/14132

   ## Summary
   
   - add the APISIX 3.19 Control API OpenAPI 3.1 contract
   - document all 17 operations implemented by the release branch
   - distinguish core endpoints from configuration-dependent plugin and service 
discovery endpoints
   - use Apache-owned documentation links and source-valid response examples
   
   This is the release/3.19 source portion of 
[api7/docs#2793](https://github.com/api7/docs/issues/2793). It follows the 
version-specific ownership model established for the Admin API: the release 
branch owns its own contract, while the Apache website and downstream sites 
consume that exact source.
   
   ## Source verification
   
   The contract was audited against the 3.19 implementation and tests, 
including:
   
   - built-in routes in `apisix/control/v1.lua`
   - router behavior in `apisix/control/router.lua`
   - `server-info` and service discovery registrations
   - Control API tests under `t/control/` and `t/plugin/server-info.t`
   
   The audit also corrected defects in the former downstream-only document: 
single-resource response envelopes, persisted discovery dump content type, 
`server-info` deprecation history, reload failure behavior, path examples, and 
exact error messages.
   
   ## Validation
   
   - Redocly OpenAPI validation
   - OpenAPI 3.1, version, path, operation, security, and operation-ID 
assertions
   - independent source review of every operation, response, example, and 
availability condition
   - all Apache documentation links resolve
   - `git diff --check`
   
   Redocly reports only its generic missing-4xx warnings for operations whose 
implementation defines no operation-level 4xx response.
   
   ## Compatibility
   
   This adds a documentation contract only. It does not change runtime routes 
or behavior.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to