Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Re-organize APIs for consistency and future-proofing #1238

Closed
EricWittmann opened this issue Feb 19, 2021 · 2 comments
Closed

Re-organize APIs for consistency and future-proofing #1238

EricWittmann opened this issue Feb 19, 2021 · 2 comments
Labels
Impacts Documentation Use this to tag Pull Requests that introduce changes that should be documented. type/enhancement New feature or request

Comments

@EricWittmann
Copy link
Member

We have multiple APIs we support right now, including:

  • Apicurio Registry core API
  • Confluent Schema Registry API
  • IBM Schema Registry API
  • CNCF Schema Registry API

We should organize these as follows:

  • /apis/registry/v1 and /apis/registry/v2
  • /apis/ccompat/v6
  • /apis/icompat/v1 (confirm version # with ibm)
  • /apis/cncf/v0
@EricWittmann EricWittmann added the type/enhancement New feature or request label Feb 19, 2021
@gunnarmorling
Copy link
Contributor

gunnarmorling commented Feb 23, 2021 •
edited
Loading

As discussed in our call, it'd be worth considering whether the old V1 URL path can be kept (deprecated), as that'd help a lot with upgrading procedures.

@EricWittmann
Copy link
Member Author

Agreed. That's captured here: #1250

@smccarthy-ie smccarthy-ie added the Impacts Documentation Use this to tag Pull Requests that introduce changes that should be documented. label Feb 23, 2021
@EricWittmann EricWittmann mentioned this issue Mar 1, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Impacts Documentation Use this to tag Pull Requests that introduce changes that should be documented. type/enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gunnarmorling @EricWittmann @smccarthy-ie