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

having config name as unique vs name and schema #61

Open
CptSchnitz opened this issue Nov 21, 2024 · 0 comments
Open

having config name as unique vs name and schema #61

CptSchnitz opened this issue Nov 21, 2024 · 0 comments

Comments

@CptSchnitz
Copy link
Collaborator

Today the config name is unique and cannot be duplicated at all.
we might consider changing it so name and schema combination will be unique.
this will make it so we can create multiple versions with the same name and will make schema upgrades easier.
the problem is it will make it harder to make api calls, and to reference configs by name as its combined.

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

No branches or pull requests

1 participant