What would you like to be added?
part of #12913
If the v2store still contains custom content, 3.6 should panic on bootstrap. But if users change --v2-deprecation to V2Depr0NotYet, then it won't panic anymore even if v2store contains user data (custom content). It may lead to data inconsistency in such case.
To ensure a smoother upgrade from 3.5 to 3.6, we still keep the option, but ignore users' provided value; and print a warning if present.
Why is this needed?
To avoid potential data inconsistency due to users misconfiguration.
What would you like to be added?
part of #12913
If the v2store still contains custom content, 3.6 should panic on bootstrap. But if users change
--v2-deprecationto V2Depr0NotYet, then it won't panic anymore even if v2store contains user data (custom content). It may lead to data inconsistency in such case.To ensure a smoother upgrade from 3.5 to 3.6, we still keep the option, but ignore users' provided value; and print a warning if present.
Why is this needed?
To avoid potential data inconsistency due to users misconfiguration.