add support for cross version provider import #778
Closed
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.
This solution is used to detect SDK behavioral change when upgrade SDK for terraform providers. It takes advantage of existing acceptance tests. By deploying resources with released provider and using import step with developing provider to check whether there's a behavioral change.
Here's an example of detecting breaking change like https://azure.microsoft.com/en-us/updates/zone-behavior-change/. If there's a breaking behavioral change after SDK upgrade, running acc tests will show
ImportStateVerify attributes not equivalent
.And this feature is disabled by default. So it won't affect regular acceptance tests.
Similar issue: #628
This is just an idea to prevent breaking change in SDK upgrade, I'm open to all suggestions. 😃