[BUG] Can't use configuration to overwrite global policy.

Release version

v4.1.2

Describe the bug

We have our CORS config setup in the global policy of our APIM instance which is different across 3 separate environments. Hence we need to be able to change this between each environment however the following doesn’t seem to work:

apimServiceName: "{apimName}"
policies:
  name: "policy"
  properties:
    value: "{policy}"

This configuration seemingly gets ignored.

Expected behavior

For the global policy to be replaced with whatever {policy} is set to

Actual behavior

The config file is ignored and the policy.xml is pushed.

Reproduction Steps

Use this as your configuration:

apimServiceName: "{apimName}"
policies:
  name: "policy"
  properties:
    value: "{policy}"

[nathan-j-codes]

@guythetechie I tried it and it works. Thank you.

[guythetechie]

@yaterchatter - We unfortunately don’t support overriding fragments either. That said, would a solution like this work?