Update azurerm_(linux|windows)_virtual_machine_scale_set
- Fix #8454
#11362
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partially fixes #8454
We could do this work around because the service team has confirmed that the default value when absence of this attribute is
Regular
(details here)And the service cannot return anything when a property is not set in the request, they call this principal as "PUT-GET consistency".
In some circumstances, this helps - sometimes absence of a property means it was automatically assigned to a value chosen by Azure, and in this way, we will not be getting any diff, which is convenient. They usually will provide another operation to query the actual value of this. An example for this behaviour is the "managed boot diagnostics" here