Enable the use of SSH protocol for authentication to APIM Git repos
Current: Interacting with our APIM git repos requires the use of username/password credentials, with the password being generated on the "Access credentials" section of APIM on Portal. This password is valid for 30 days, max: https://docs.microsoft.com/en-us/azure/api-management/api-management-configuration-repository-git#to-clone-the-repository-to-your-local-machine
Desired: Allow users to upload public ssh keys to the APIM tenant, so that users, remote servers, and services can connect to the repo using the SSH protocol. Github currently allows this: https://help.github.com/en/articles/about-ssh
This is especially important for our CLI configuration. We have our APIM git repo loaded as a submodule for our project, as we have integration tests that compare our backend controllers against what we expose in APIM by examining the configuration files in our APIM git repos. Our CLI solution, Appveyor, recommends using SSH keys to allow it to update remote private submodules: https://www.appveyor.com/docs/how-to/private-git-sub-modules/
We have a secure work-around that uses username/password authorization instead, but this requires us to update our CLI configuration every 30 days, as that's the longest amount of time these passwords are valid.
Robert Abraham commented
Related thoughts: App Service Git deployment does not impose the same 30-day limit on Git-compatible keys.
Read-only keys would be helpful as well. Our use case does not require us to deploy with git, only clone for validation purposes.