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
I'd like to know how to remove a subject-specific compatibility config value.
The scenario would be:
Global config is, let's say, FULL
Temporarily, a subject is configured to be BACKWARD
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?
The text was updated successfully, but these errors were encountered:
@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.
@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
I'd like to know how to remove a subject-specific compatibility config value.
The scenario would be:
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?
The text was updated successfully, but these errors were encountered: