Bug: applicationGateways@2024-05-01 requestRoutingRules false positive drift due to ordering mismatch

[CezaryKlus]

Microsoft.Network/applicationGateways@2024-05-01 I observe a permanent plan drift that is not caused by any change but due to a change in the order of the requestRoutingRules compared against API response.

In my case the collection contains 12 rules, and I construct it via flatten([for ... in ... : [ pattern.

I construct the other collection in the same way however only requestRoutingRules reports false drift.

It seems it does not fit in this fix: #455

[ms-henglu]

Hi @CezaryKlus ,

Thank you for taking time to report the issue.

The #455 was aimed at reducing noise when there're more elements in the response comparing with the config.

But I think we could add this feature in the plan phase as well, to suppress the diff if only order is changed?