[BUG] publisher pipeline not changing backend.

[mykube-in]

Release version

v5.1.4

Describe the bug

My extractor pipeline is able to extract the Azure function API. It extract the functionapp (I just added) . publisher pipeline given no error but when i checked my APIM GUI in qa and prod environment then it still points to dev function app .

configuration.prod.yaml

apimServiceName: apim-amit-mycommpany-prd--->this is name of production APIM namedValues:

• name: func-amit-mycommpany-dev-key ---> key from function app deployed in dev env. properties: displayName: func-amit-mycommpany-dev-key ---> key from function app deployed in dev env. keyVault: identityClientId: 9f5be961-c982-4a2a-90b0-a8fb8d12913b ---> APIM resource application id. secretIdentifier: https://kv-amit-mycommpany-prd.vault.azure.net/secrets/func-amit-mycommpany-prd-key-4-apim/a6a71638882a4391a963bbd25d90fc03
  loggers: diagnostics: backends:
• name: mycommpany ------> function properties: url: https://func-amit-mycommpany-prd.azurewebsites.net/api ---> url to prod function resourceid: https://management.azure.com/subscriptions/XXXXX-XXXXX-XXXXXX-XXXXXX-XXXXX/resourceGroups/rg_amit_mycommpany_prd/providers/Microsoft.Web/sites/func-amit-mycommpany-prd ----> resource id of prod function apis:

Expected behavior

backend should point to production function App "func-amit-mycommpany-prd"

Actual behavior

backend is pointing to dev instance function App "func-amit-mycommpany-dev"

Reproduction Steps

try to deploy function App & publish API's via APIM

[github-actions[bot]]

  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 enable logging as documented in our wiki here. Make sure you set the value to trace. Then scrub your logs and post them here.

[smiddler]

Same issue in v6.0.1

resourceId doesn't update from configuration file in subsequent environments. See how our wip/dev resource is falsely referenced in the portal for our "int" (integration testing) environment, therefore creating a blank azure resource entry which I can then manually select the correct resource from. However next run of the pipeline will break it again.