如何更改Azure API管理服务中端点/操作的Azure功能后端？
我正在开发一个新版本的Azure功能应用程序，我们已经使用了几年。该应用程序已经浏览了许多版本。对于每个主要版本，按照建议，我创建了一个新功能应用程序。在上一个版本中，我使用Azure函数中的代理功能将呼叫从旧版本重定向到新版本，以逐函数为基础，以便我可以以受控的方式推出新版本。从技术上讲，代理仍然是一种选项，但它们在Azure功能V4中没有可用，建议使用API管理。
我已经研究了API管理，它看起来像是一个更好的解决方案，除了我找不到如何更改特定API终点/操作的Azure功能后端。我根据旧的Azure功能应用程序和API管理创建了一个新的API，并正确生成了所有端点/操作。我希望我可以进入每个端点/操作并更改后端，但是我发现的是Azure资源值仅读取。
有没有办法将不同的Azure资源（Azure函数应用程序）分配给终点/操作？
我的问题是让API管理自动生成API，因此它锁定在生成它的Azure函数应用程序中？
建议使用一个API的推荐方法是什么，我可以根据需要每个终点/操作更改后端？
I am developing a new version of an Azure Functions app that we have been using for several years. The app has gone through a number of versions. For each major version, following the recommendations, I have created a new Function App. In the last version I used the Proxy capability in Azure Functions to redirect calls from the old version to the new version on a function by function basis so that I could roll out the new version in a controlled fashion. Proxies are technically still an option but they are not available in Azure Functions v4 and the use of API Management is suggested.
I have look into API Management and it looks like a better solution moving forward except I can't find out how to change the Azure Function backend for a particular API end-point/operation. I created a new API based on my older Azure Functions app and API Management correctly generated all the end-point/operation. I was hoping that I could just go into each end-point/operation and change the backend but what I find is the Azure Resource value is read-only.
Is there a way to assign a different Azure Resource (Azure Function app) to an end-point/operation?
Is my problem that I let API management automatically generate the API and so it is locked in to the Azure Functions app that generated it?
What would be the recommended way to have one API where I can change the backend as needed per end-point/operation?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我想我可能已经找到了我想要的东西。
在端点/操作设计的“入站处理”部分中，有一个“固定支持”策略，使我能够更改后端服务。我认为这将为我带来技巧。
I think I may have found what I was looking for.
In the "Inbound processing" section of the design of an endpoint/operation there was a "set-backend-service" policy that allowed me to change the backend service. This will do the trick for me I think.