1

We have multiple teams working on the same Api Management instance, and the current git-based configuration that API Management provides, does not really facilitate a good process for us (with support for code reviews, pull requests, deploys etc.).

Can we use a GIT repository in Azure DevOps to control the configuration instead of having to use the repository provided directly by API Management?

Our primary use cases are:

  1. Merge/sync changes from API Management into our central repository
  2. Performing changes in a DevOps repo in separate branches, merge the changes to the main branch via pull requests and sync'ing the changes to API Management
pwind
  • 401
  • 1
  • 3
  • 13

1 Answers1

0

We can clone the configuration repository and push changes back- using our familiar Git commands.

You can try to run the following command in cmd task of azure devops pipeline.

git clone https://username:password@{name}.scm.azure-api.net/
git add .
git commit -m "abc"
git push

Here are the document and similar case you can refer to.

Hugh Lin
  • 17,829
  • 2
  • 21
  • 25
  • Hi Hugh Lin. I know the GIT-feature of API Management, but that does not enable us to store the configuration in a repository inside of Azure Devops, where we can collaborate via pull requests, pipelines etc. In my eyes, the GIT-feature og APIM is simply another way to store the configuration, but it is not very flexible. – pwind Apr 12 '21 at 06:01