force creating new condition
if type
is changed
#518
Merged
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.
#517
background: Fastly API doens't support updating the
type
field once it's created.And because
fastly_service_v1
is a mono resource, the usualForceNew
approach doesn't work as it will attempt to re-create afastly_service_v1
resource as a whole.CustomizeDiff
is also not an option either ascondition
is a nested block.So we unfortunately implement it in this way, where we silently call DELETE and CREATE if
type
attribute is changed. Otherwise, call UPDATE.