Complete az apim commands
See original GitHub issueIs your feature request related to a problem? Please describe.
Azure API Management is a critical, core service for creating modern web architectures, particularly when coupled with app service, functions, etc. The az apim module is missing nearly all required functionality to create and manage apis, policies, products, etc within apim. The feature request is to complete the module, to get it on parity with Powershell: https://docs.microsoft.com/en-us/powershell/module/azurerm.apimanagement/?view=azurermps-6.13.0
It is really unfortunate to use az cli for 95% of code and then switch to ARM/Powershell.
Describe the solution you’d like
Complete the az apim module to reach parity with ARM/Powershell (https://docs.microsoft.com/en-us/powershell/module/azurerm.apimanagement/?view=azurermps-6.13.0)
Describe alternatives you’ve considered ARM or Powershell, but switching languages/platforms is cumbersome when the rest is using az cli.
Additional context If possible, if this is planned or being planned, could you provide a timeline so that we can plan our roadmaps accordingly?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6

Top Related StackOverflow Question
If it helps, I am able to create a Developer tier API Management service, as shown in the help of the
apimcommand, but not a Consumption tier, which is also shown in the help.Results in:
Totally agree and would love to see a full (or at least fuller) support. One of our teams has worked during the fall with serverless Function apps fronted by APIM, and we find ourselves in a lot of issues that we have to hack around (some including manual labor). As far as I am concerned, I don’t think the bash version of
az apimis production-ready as it works currently. Our use cases relate to serverless microservice architectures, where (unrelated but may be contextually interesting) the poor fit between Serverless Framework (the Azure provider specifically) is what lead us to do things with bash instead. We were totally caught off-guard on that even the bash CLI wasn’t up to snuff.