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

How to remove subject-specific compatibility config #596

Closed
javierholguera opened this issue Jul 31, 2017 · 3 comments
Closed

How to remove subject-specific compatibility config #596

javierholguera opened this issue Jul 31, 2017 · 3 comments

Comments

@javierholguera
Copy link

javierholguera commented Jul 31, 2017

I'd like to know how to remove a subject-specific compatibility config value.

The scenario would be:

  1. Global config is, let's say, FULL
  2. Temporarily, a subject is configured to be BACKWARD
  3. After some changes have gone into the Registry, we don't need step 2 anymore.

Obviously the config can be updated to FULL, but that is a risk. If by any change the global value is changed to anything, that subject will stay to FULL for the time being.

The point is that it should possible to delete a custom-specific compatibility value so global is applied again. Is this possible?

@mageshn
Copy link
Member

mageshn commented Oct 6, 2017

@javierholguera unfortunately this is not supported yet. Just to understand the use case, how often do you do something like this and what would be the reason for the same.

@javierholguera
Copy link
Author

@mageshn it's not often because making incompatible changes is painful. However, it does happen and when it does, removing the specific subject configuration is housekeeping that we can't do today because of the lack of this feature

@rayokota
Copy link
Member

Fixed by #1780

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

4 participants