Open JanneMattila opened 4 years ago
Thanks for filing this. Technically, this is not a what-if noise issue. What-if is accurately telling you the difference between these two payloads. On PUT (creation), you submit a url, but on GET you are returned the actual content.
We'd like to work with the ApiManagement team to propose an alternative API design that would fix this. Will keep you updated on this thread.
Any updates on this?
Describe the noise
Resource type (i.e. Microsoft.Storage/storageAccounts) Microsoft.ApiManagement/service/policies
apiVersion (i.e. 2019-04-01) 2019-01-01
Client (PowerShell, Azure CLI, or API) PowerShell
Relevant ARM Template code (we only need the resource object for the above
resourceType
andapiVersion
, but if it's easier you can include the entire template link to relevant clipExpected response (i.e. "I expected no noise since the template has not been modified since the resources were deployed) Expected no noise
Current (noisy) response (either include a screenshot of the what-if output, or copy/paste the text)
Additional context Problems seems to be clearly this:
It does not understand difference of xml content and link to xml content.
This same problem happens with policies in different levels (e.g. API or API operation) if
rawxml-link
is used.