The Default Value Set in the Variable Library poses a risk. The Default Value Set will silently apply values when no explicit value set has been selected for a Test or Prod workspace. There i...
This is a great point. It is related to an issue where if you DO actively set a variable value, but that value doesn't resolve to a valid path, the shortcut is not changed, but still retains the previous (or default) value. This can cause the same problem of exposing DEV or TEST data in PROD for example.
See the following similar, but different use case IDEA. Shortcuts with invalid paths when a variable set is selected should ERROR not default to previous value.
