Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow the API Management - Set or update an operation policy task to consume operations from a previous task #122

Open
orty opened this issue Mar 24, 2022 · 0 comments

Comments

@orty
Copy link

orty commented Mar 24, 2022

Hi,

I am currently implementing your extension in our DevOps pipeline for an Azure Function behind an APIM service.
Most specifically, I really enjoyed the ability to consume a data contract from a Swagger endpoint, and my process is now to

  • Build & Deploy the AzFunction
  • Use the API Management - Create or update product task
  • Use the API Management - Create or Update API task, with the Product created by previous task option checked, and consuming the Swagger output from the newly deployed Azure Function (to get the latest endpoints signatures)

It does the job up to 95%, but the resulting API operations lose their link to the Azure Function, and it is definitely a breaking change for us if we chose to go with your extension. I am currently working on a proposal for an update though, using the API Management - Create or update an operation policy task. The idea would be to use it to override the policies for all the operations previously created/updated, and thus restoring their link to the Azure Function.

My proposal is to add a setting similar to Product created by previous task but that would be called Operation(s) created by previous task and it would auto-fill the API and Operation inputs.

I am running some tests, I should be able to issue the Pull Request in the next days.

Thanks again for your great work on this extension !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant