You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The applyAzureSpecificDiff method does not currently have any awareness of what type of resource it's applying to. When introducing resource-specific customisations, we should accurately target specific resources, therefore we should ensure that the required information is passed to this method to make accurate decisions.
Additionally, the API version could be critical information when considering changes, as old API versions might use different values for fields which cause replacement, such as the existing SKU migration for Managed Clusters.
The missing ingredient at the provider protocol level is the type token associated with the old state. Combined with #3766 we would have all the information needed to drive migration logic.
The
applyAzureSpecificDiff
method does not currently have any awareness of what type of resource it's applying to. When introducing resource-specific customisations, we should accurately target specific resources, therefore we should ensure that the required information is passed to this method to make accurate decisions.pulumi-azure-native/provider/pkg/provider/diff.go
Line 458 in ba9989d
Additionally, the API version could be critical information when considering changes, as old API versions might use different values for fields which cause replacement, such as the existing SKU migration for Managed Clusters.
The text was updated successfully, but these errors were encountered: