Skip to content
This repository was archived by the owner on Feb 23, 2024. It is now read-only.

Commit af0763a

Browse files
authored
Update FAQ.md
1 parent ace8417 commit af0763a

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

FAQ.md

+3-6
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,10 @@
11
# Azure API Management DevOps FAQ
22

3-
### Is everything available through ARM templates now?
3+
### Can I deploy everything through ARM templates now?
44
The only thing that's not available is developer portal content. Everything else is available through ARM.
55

6-
### Is there a size limit of ARM templates?
7-
Yes, each template is limited to 1MB. Our proposed approach uses linked templates, which helps to keep each template relatively small.
8-
96
### Your example is hosted in a public repo on Github, what if I want to use a private repo?
107
Check out this [article](https://blog.eldert.net/api-management-ci-cd-using-arm-templates-linked-template/), if you use a private repo, you can add a step in your pipeline to copy the linked templates to a blob container and access the files with a SAS token.
118

12-
### How do I deploy all configurations versus just deploy an API?
13-
In our example, each template can be deployed individually. You can also use the master template, which ties everything together, to deploy all templates.
9+
### Why did I run into `PessimisticConcurrencyConflict` error when trying to deploy the templates?
10+
If you are trying to make multiple changes to the same API (e.g., import an Open API definition, add to a product), then you should daisy chain the operations using the DependsOn element.

0 commit comments

Comments
 (0)