APIOps for one APIM serving as multiple environments

Open
#223 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
azure, typescript
Domain
api, cloud

Research direction

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.

Written by the indexing model from the issue text.

Description

P2 Question
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

Dominant language
TypeScript
Stars
29
Forks
10
Avg merge
1d 13h
Merged PRs (30d)
23

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/apiops-cli

All issues in Azure/apiops-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.