The GraphQL API was added as a sub-node of 'service https api', though it is, in practice and implementation, a distinct entity. Refactor the http-api server into distinct configuration nodes.
Description
Description
Details
Details
- Version
- -
- Is it a breaking change?
- Perfectly compatible
Related Objects
Related Objects
- Mentioned In
- rVYOSONEX9f7767c8022f: http-api: T6736: regenerate openapi docs
rVYOSONEX954be34bc938: http-api: T6736: remove routes on config delete
rVYOSONEXfc9885f85961: http-api: T6736: separate REST API and GraphQL API activation
rVYOSONEX3ad911a20620: http-api: T6736: update for deprecated/renamed in Pydantic V2
rVYOSONEX8183e2cc8178: http-api: T6736: add distinct XML path for REST API
rVYOSONEX40d966310cb5: http-api: T6736: add migration script and update version
rVYOSONEX8322cc4d8206: http-api: T6736: update smoketest for syntax change
rVYOSONEXc21fa1fb7726: http-api: T6736: sanitize error message containing user input
rVYOSONEX7e23fd9da028: http-api: T6736: normalize formatting
rVYOSONEX5a59d8529c56: Merge pull request #4110 from jestabro/distinct-api
Event Timeline
Comment Actions
PR to follow tests and migration script:
https://github.com/vyos/vyos-1x/compare/current...jestabro:distinct-api