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

the current Apicurio Registry API is not built to be idempotent ? #222

Open
LittleWat opened this issue Oct 28, 2024 · 1 comment
Open

the current Apicurio Registry API is not built to be idempotent ? #222

LittleWat opened this issue Oct 28, 2024 · 1 comment

Comments

@LittleWat
Copy link
Contributor

The readme says:

some of them being that this is a "broken by design" approach as the current Apicurio Registry API is not built to be idempotent and used in such a way

If so, what would you recommend when multiple teams use one Apicurio registry?

AWS Glue schema registry provides a way to manage schemas in the declarative manner using Terraform:

so I'm wondering what is the main difference between Apicurio registry and AWS Glue schema registry
@LittleWat
Copy link
Contributor Author

@carlesarnal thank you for your continuous support and I'd be glad if I could get your reply 🙇‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LittleWat