Aiven API
/v1/project/{id}/service/{id}/kafka/schema/subjects/{id}/versions/{id}/schema endpoint removal
Deprecated, no dateSubscribe to Aiven APIShare
Aiven API deprecated /v1/project/{id}/service/{id}/kafka/schema/subjects/{id}/versions/{id}/schema without giving a shutdown date yet.
Calls it hits
/v1/project/{id}/service/{id}/kafka/schema/subjects/{id}/versions/{id}/schema
What to use instead of these calls
No replacement is named for this endpoint.
In Aiven API's words
The API endpoint /v1/project/{project}/service/{service_name}/kafka/schema/subjects/{subject_name}/versions/{version_id}/schema is deprecated and will be removed.
Facts
- API
- Aiven API
api.aiven.io - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Aiven API's own pages
Questions
When does this change take effect?
Aiven API deprecated /v1/project/{id}/service/{id}/kafka/schema/subjects/{id}/versions/{id}/schema without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Aiven API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Aiven API 10
-
/v1/account/{id}/billing-groupEndpoint removal Stopped working -
/v1/billing-groupEndpoint removal Stopped working -
/v1/billing-group/{id}Endpoint removal Stopped working -
/v1/billing-group/{id}/invoiceEndpoint removal Stopped working -
/v1/billing-group/{id}/invoice/{id}/csvEndpoint removal Stopped working -
/v1/billing-group/{id}/invoice/{id}/linesEndpoint removal Stopped working -
/v1/billing-group/{id}/projectsEndpoint removal Stopped working -
/v1/invoices/{id}Endpoint removal Stopped working -
DELETE /v1/card/{id}Endpoint removal Stopped working -
/v1/account/{id}/users/searchEndpoint removal Stopped working
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.