Add protections around "Current Revision"
Currently: When we load APIM in Azure Portal and navigate to an API, the CURRENT Revision for that API is loaded by default. If a user forgets to switch to a non-CURRENT revision and makes edits, they will have changed the live API, potentially harming consumers of the API.
Desired: Allow some way to protect against these accidental changes to the CURRENT revision. Here are two possible solutions:
Make it possible to specify which revision is loaded by default when the APIM instance is loaded in Azure Portal
Lock the CURRENT revision such that changes are impossible unless a user re-enters their credentials, confirming they want to change the current revision
Regardless of how it would be implemented, the end goal would be to prevent accidental changes to the current revision