Apiops

preview_player
Показать описание
Рекомендации по теме
Комментарии
Автор

Excellent video, very clear and consise.

simonkelso
Автор

great video, I have one question -which I posted as a comment in github as well-...

Generally speaking, how could we support a scenario in which in dev 2 apis (api-1, api-2) were updated but only 1 (api-1) needs to be promoted?
I thought by using the config extract.
So I put api-1 in the config extract and I saw I could "extract" one specific api, api-1, and create PR-A.

Now, my prod apim is already in place and tracked in the git repository. When I look to PR-A this is proposing to delete all the other Apis (which are missing in the branch created by the run - extract pipeline) and update api-1. If I understand this correctly, this will give me in the end a prod apim with api-1 updated and all the other ones deleted.
What I would have expected was to keep all the other apis and update api-1. I hope I made myself clear.

nanogongolo
Автор

How would you recommend implementing this extract/publish process in an APIOps repo shared by different Product Teams?

keithmorris
Автор

Hi Wael, can we use a self-hosted agent with extractor and publisher pipelines, or does It only require a Microsoft-hosted agent?
If we can run with a windows self-hosted agent what will be the dependency on the agent install to run the pipelines??

surbhirajput
Автор

What tool are you using to draw while presenting please?

PhilipReed-wb
Автор

Does this tool support different Tier, Version of apim ?

oscar-chan
Автор

This video is presenting mostly the same information like any other video on the APIOps extractor-publisher tool but doesn't explain properly how the publisher is using the template yaml file to promote the publishing of API by overriding using the configuration.[env].yaml file. Do you have a tutorial on this aspect ? In my scenario I am using the extractor to extract API and all associated resources from the Sandbox environment to then publish it to my UAT environment APIM. If I use this tool as-is, I am not doing anything else but promoting Sandbox data to my UAT APIM... checking NamedValues as 1 example I got them published to UAT but they reference Sandbox urls... There's no youtube video explaining this APIOps extractor-publisher tool sourcing from lower env and promoting to higher environment by making use of the configuration.[env].yaml file !

TheDjexcessive
Автор

When migrating an API from Development to Production, typically the backend from Development cannot be used in Production. In this video, they are copying backend links from Development to Production, meaning that Production is effectively using API resources from Development. Is there any way to control or manage this?

vladsukhachev
Автор

Hi Wael

Amazing walkthrough! It helps greatly

I have a small issue though, is there anything to generate or facilitate me crafting the configuration.prod.yaml?
It could be pretty daunting to craft it if there are many things in APIM.

For your advice, please.

thedevguild
Автор

I am having trouble with patial migration like only few APIs, NamedValues from dev to QA. Can you post a detail video on How to migrate few apis, namedValues from Dev to QA ? We are one of the biggest consumer of Azure APIM .

dibyaranjan
Автор

In my experience with Azure API Management, I usually only want to copy a single API to Production. Based on the video example, I came to the conclusion that all APIs in Development are being copied entirely.

vladsukhachev
Автор

Feels like all of this is an afterthought to incorrectly designing API Management. This software feels like a smell.

last-life