You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is pretty uncomfortable, because it is not possible to run it in Postman / Insomnia (REST Clients). So I suppose to create a new REST API endpoint for it
Goal
As a developer, I need an option to delete all schemas by one REST API call, to reduce time on managing Schema Registry
Solution
Create a new REST API endpoint to delete all schemas by one REST API call
It must support soft and hard deletes
Possible API: curl -X DELETE "http://localhost:8081/subjects[?permanent=true]"
Hey! I would like to work on this feature and open a PR to add a new endpoint for deleting all subjects, supporting both soft and hard deletes. Please let me know if there is any guidance or preferences I should be aware of before I start.
I'm currently contributing to this schema-registry issue and have been able to get most of the environment set up and started working through the changes locally.
However, I'm hitting a blocker while trying to build the common module — specifically:
Failed to execute goal io.confluent:resolver-maven-plugin:0.6.0:resolve-kafka-range
MojoExecutionException: Could not find any ccs-kafka artifacts.
It seems the resolver-maven-plugin is trying to pull in internal ccs-kafka artifacts that aren't publicly resolvable.
Is there an OSS-friendly build profile or a documented workaround to bypass this dependency, especially for external contributors?
Just looking to get past these steps so I can validate and test the changes I'm working on.
Problematic
Hey, I have ~200 schemas at Schema Registry and I need to delete them all. Now I need to write bash script for it:
It is pretty uncomfortable, because it is not possible to run it in Postman / Insomnia (REST Clients). So I suppose to create a new REST API endpoint for it
Goal
Solution
curl -X DELETE "http://localhost:8081/subjects[?permanent=true]"
Sources
The text was updated successfully, but these errors were encountered: