Publisher Pipeline

[josielewis]

Release version

v6.0.1-rc1

Question Details

Can you publish across different subscriptions?

Expected behavior

Publish to different subscriptions all under the same tenancy

Actual behavior

Run publisher task fails when trying to publish to APIM located in a different subscription

Reproduction Steps

Publisher pipeline runs source APIM deploys ok... publishing to another environment in a different subscription fails

[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.

[guythetechie]

@josielewis - you should be able to. The publisher expects a subscription ID and resource group name in configuration. If you use our GitHub starter pipeline, this gets passed here.

apiops/tools/github_workflows/run-publisher-with-env.yaml

Line 228 in bf5cc12

AZURE_SUBSCRIPTION_ID: ${{ secrets.AZURE_SUBSCRIPTION_ID }}

The starter pipeline uses the same secret value in the extractor and publisher, but you can certainly change it to suit your needs.