fix: set ForceNew fields, that are not in the DTO #2089
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
byashimov
force-pushed
the
byashimov-NEX-1311-validate-force-new
branch
from
9d20d35 to
43fb745
Compare
vmyroslav
approved these changes
Mar 10, 2025
byashimov
force-pushed
the
byashimov-NEX-1311-validate-force-new
branch
from
ecd6983 to
6350814
Compare
byashimov
force-pushed
the
byashimov-NEX-1311-validate-force-new
branch
from
6350814 to
04ee31f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When ForceNew field not in the DTO, terraform fails to import the resource.
Fixes #2065