No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I have annoying scenario where by our Azure Application Gateway always shows a diff on RequestRoutingRules because the way the values are stored appear to be in a different order than when I generate them.  Does anyone else have this problem? I did try to order the RequestRoutingRules by name, but I can't order by a value that's then inside the Input&lt;string&gt; property. Anyone got any ideas?

Sounds like <https://github.com/terraform-providers/terraform-provider-azurerm/issues/6896> ?

I don't think it's the same, because I can execute exactly the same code and it would diff that something has changed, the diff shows all the values in a different order than described. The issue seems to show an entire request routing rule that is removed and a new one added.

While the diff is OK, it's hard to read when the diff is large like this. Is there anyway to output the original configuration and new configuration, so it can be side by sided?