APIOps for one APIM serving as multiple environments
- 主要语言
- TypeScript
- 星标
- 26
- 派生
- 9
- 平均合并
- 1 天 3 小时
- 30 天内合并 PR
- 20
描述
### Question
Hello, I am trying to see if the apiops-cli could be used in this scenario: we use one APIM to serve multiple environments (e.g. dev/test). I plan to create the dev API initially by importing the swagger spec. Now in APIM, the api-id is registered with the imported name (e.g. call it my-dev-api). I want to migrate to a test version within the same APIM. I can use your override configuration yaml to change all the keys I need to. However, I cannot use the same name as the cli apiops publish will just do a PUT to the same API. Am I correct and is there a way to work around this?
### Context
_No response_
贡献指南
调研方向
Begin with the apiops publish behavior and the override configuration YAML described in the issue; verify whether publishing targets the existing api-id with PUT when moving from dev to test. Done means an explicit supported workflow or documented limitation and workaround for serving multiple environments from one APIM.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- azure, typescript
- 领域
- api, cloud
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100