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.

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

Export just a single group #5798

Open
wolfchimneyrock opened this issue Jan 9, 2025 · 0 comments
Open

Export just a single group #5798

wolfchimneyrock opened this issue Jan 9, 2025 · 0 comments

Comments

@wolfchimneyrock
Copy link
Contributor

Feature or Problem Description

We are implementing a multi-tier multi-tenancy (based on groups) schema registry where each tier is an independent instance of apicurio registry.

we want to support a workflow where users can "deploy" i.e. copy the contents of their group from one tier to another, without our infrastructure having to manually fetch all the artifacts / versions / rules from the source tier and register in the destination tier.

Proposed Solution

the /admin/export api call could be modified to add an optional registryGroup parameter, which would restrict the rules / artifacts / versions exported to just those in the single group specified.

/admin/import wouldn't need any change, except that we would have to ensure that requireEmptyRegistry=false

Additional Context

in this case it would be ok for the contentId / globalId to differ between tiers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant