azure-service-operator
azure-service-operator copied to clipboard
Azure
Ignore volatile properties when deciding whether to reconcile a resource
We're planning on comparing the resource-as-defined with the resouce-as-read-from-ARM and doing a reconciliation between the two (First steps towards this are PR #2022 and Issue #1491).
As already discussed, we're expecting some false positives due to properties that are service defined and likely to change regularly.
We should look to use the proposed x-ms-volatile property from the Swagger specs to eliminate these properties from consideration.
x-ms-volatile Mark if a property is a system metric or prone to changes without user interaction Examples of applicable properties o nodeUpTimeInSeconds o lastAccessedTime o quotaNextResetTime
Until we have #1491 we don't actually have to do this, so makes sense to defer this until #1491.
Ideally, a solution to this would also allow us to support #2938 - the only difference is the source of the request to ignore the property.
This ties in with diffing, but is not currently needed so not worrying about this quite yet.