GET API中的SubscriptionRequired具有奇怪的行为 [英] SubscriptionRequired in GET API has strange behaviour

问题描述

我在GET https://management.azure.com/subscriptions/ {subscriptionId} / resourceGroups / {resourceGroupName} /providers/Microsoft.ApiManagement/service/ {的帮助下得到API的定义serviceName} / apis / {apiId}？api-version = 2018-06-01-preview

无论我使用什么api版本，我总是得到一个属性  "subscriptionRequired" ：
true ，

我尝试了以下api版本：  2018-06-01-preview，2018-01-01,2017-03-01,2016-10-10,2016- 07-07,2015-09-15,2014-02-14

当我尝试使用带有使用api-version 2017-03指定的subscriptionRequired的arm-template部署api时01我收到错误：  " 20180601之前的版本不支持SubscriptionRequired属性"

当我在20180601之前询问有关使用api版本的API的信息时，我会如果您不包含SubscriptionRe，则更喜欢quired属性，因为在20180601之前使用带有api-version的arm模板部署API时不支持该属性。

解决方案

嗨  Nisse1

很高兴听到您遇到此问题。产品团队最近推出了一个新的开源项目，使客户能够管理ARM部署和更简单，更简单的DevOps场景： Azure
API管理DevOps资源工具包 

此外，请务必在此处查看随附的博文：  构建用于API管理的CI / CD管道



我们邀请您尝试使用此工具不仅可以解决这个问题，还可以更灵活地管理整个APIM DevOps配置和实施。如果您遇到任何问题，请随时直接在回购中打开问题，
在这种情况下，APIM产品团队和其他MSFT团队的工程师可以称重。

I get the definition of an API with the help of GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/apis/{apiId}?api-version=2018-06-01-preview

No matter what api-version I use, I always get a property "subscriptionRequired": true,

I tried the following api-versions: 2018-06-01-preview, 2018-01-01, 2017-03-01, 2016-10-10, 2016-07-07, 2015-09-15, 2014-02-14

When I try to deploy an api using an arm-template with the subscriptionRequired specified using api-version 2017-03-01 I get an error:  "SubscriptionRequired property is not supported for versions before 20180601"

When I ask for information about an API using a api-version before 20180601 I would prefer if you did not include the SubscriptionRequired property because it is not supported when deploying an API with an arm template with api-version before 20180601.

解决方案

Hi Nisse1

Sorry to hear that you encountered this issue. Product team, recently, launched a new open source project to enable customers manage ARM deployments and DevOps scenarios in simpler & easier fashion: Azure API Management DevOps Resource Kit 

Also, be sure see the accompanying blog post here: Build a CI/CD pipeline for API Management

We invite you to try using this tool to not just overcome this issue but also to manage your overall APIM DevOps configs & implementations in more resilient manner. Should you run into any issues, please feel free to open an issue directly on the repo, in which case, engineers from APIM product team & other MSFT teams can weigh in.

这篇关于GET API中的SubscriptionRequired具有奇怪的行为的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！