[Question] Does APIM publisher support deployment of selected apis to UAT or PROD version?

[ParthVyas2912]

Release version

5.1.1

Question Details

I am able to extract selected APIs that I want from my APIM dev instance. Now, currently when I try to run publish pipeline, it deploys all the APIs I have in "artifact" folder, to UAT. Is there a way to limit or target specific APIs that should be deployed into UAT environment..?

Expected behavior

Currently when I use publisher pipeline, it works as expected. But it deploys all the apis in the "artifact" folder to UAT. I want to pick and choose which apis will be deployed through publisher pipeline.

Actual behavior

Deploys all APIs present in the "artifact" folder to UAT.

I tried with default "configuration.uat.yaml" file, and I tried to remove some parameters:

But the deployment seems to deploy every API from "artifact" folder.

Reproduction Steps

Run extractor to extract couple of APIs, try to publish it using publisher pipeline. I have tried with default "configuration.uat.yaml" file and this file as well.

Still all APIs gets deployed.

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[waelkdouh]

Please search closed issues that asked about the same scenario. The purpose of the configuration file is to allow you to override values as your promote them between environments. It doesn't provide you with the ability to exclude artifacts. In order to exclude artifacts, you could always use a git ignore file as the publisher is using git in the background to detect the differences and publish them, read our documentation which talks about multiple API teams were different teams would like to promote at a different pace.

[ParthVyas2912]

Ok, thanks. I will do that.

[waelkdouh]

@ParthVyas2912 sorry I forgot to mention that we also provide the ability to create a configuration.extractor.yaml file which allows your to extract select artifacts instead of extracting everything. Here is a sample file for you. Here is link to the documentation.