Conversation
…d missing `DestroyPlan` (#602) * create destroy plan after refresh in destroy step - fixes saved plan is stale * add back refresh on non-refresh plan step for providers still on 1.5.1 * prevent refresh after testStep where nonempty plan is expected
* remove extra refresh from GCP PR * remove changelog --------- Co-authored-by: Austin Valle <austinvalle@gmail.com>
Member
|
fyi, turned this into a draft as we won't actually merge it to main 😄 |
Member
|
closing, as this is superseded by #641 which targets the right branch for the backport |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Related Issue
Since using the latest release involves introducing a new RPC, this patch is for including the necessary
refreshAfterApplychanges without introducing the breaking change of the new RPCDescription
In plain English, describe your approach to addressing the issue linked above. For example, if you made a particular design decision, let us know why you chose this path instead of another solution.
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.