- Notifications
You must be signed in to change notification settings - Fork17
importstate: UseExpectNonEmptyPlan field to ignore no-op assertion for import block test kinds#518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
… for import block test kinds
Uh oh!
There was an error while loading.Please reload this page.
rainkwan left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Looks reasonable, we can revisit the flagging question later if needed.
SBGoods left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I'm also fine with reusingExpectNonEmptyPlan since it's behavior is already well understood.
baee5c6 intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Related Issue
N/A
Description
This change adds the usage of
(TestStep).ExpectNonEmptyPlanto ignore the assertion that all import block plans must produce a no-op. A no-op plan isn't possible for some resource types that cannot return the entire original value from the remote API after importing. The usage ofImportPlanCheckscan be used to make more fine-grain assertions about the plan to ensure the plan produced during import is correct.Test failure prior to introducing the change:
Rollback Plan
Changes to Security Controls
Nope.