Skip to content

Backport of account for noop deposed instances in json plan into v1.0#28923

Merged
jbardin merged 1 commit intov1.0from
backport/jbardin/noop-deposed-change/needlessly-concrete-bluejay
Jun 10, 2021
Merged

Backport of account for noop deposed instances in json plan into v1.0#28923
jbardin merged 1 commit intov1.0from
backport/jbardin/noop-deposed-change/needlessly-concrete-bluejay

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented Jun 10, 2021

Backport

This PR is auto-generated from #28922 to be assessed for backporting due to the inclusion of the label 1.0-backport.

The below text is copied from the body of the original PR.


When rendering a json plan, we need to account for deposed instances
that have become a noop rather than a destroy.

Fixes #28903

@ghost ghost force-pushed the backport/jbardin/noop-deposed-change/needlessly-concrete-bluejay branch from 4a2156d to 74a472f Compare June 10, 2021 13:30
@ghost ghost requested a review from jbardin June 10, 2021 13:30
@jbardin jbardin merged commit ac563ef into v1.0 Jun 10, 2021
@jbardin jbardin deleted the backport/jbardin/noop-deposed-change/needlessly-concrete-bluejay branch June 10, 2021 13:46
@github-actions
Copy link
Copy Markdown
Contributor

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant