Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of don't re-set changes for refreshed outputs into v1.3 #32315

Merged
merged 1 commit into from Nov 30, 2022

Conversation

teamterraform
Copy link
Contributor

Backport

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

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


When output values are updated in the refreshed state, we don't need to re-set the changes which were already set in conjunction with the current state.

This is just a small change pulled for backport from the larger #32251 change set addressing output evaluation overall.
Helps address #32251 by not overwriting the change entry for every single output.

@teamterraform teamterraform force-pushed the backport/jbardin/output-perf/honestly-engaged-tetra branch from 7346342 to 5e9876e Compare November 30, 2022 19:07
@teamterraform teamterraform force-pushed the backport/jbardin/output-perf/honestly-engaged-tetra branch from 714d89e to 9ed5f20 Compare November 30, 2022 19:07
@jbardin jbardin merged commit 23685f7 into v1.3 Nov 30, 2022
@jbardin jbardin deleted the backport/jbardin/output-perf/honestly-engaged-tetra branch November 30, 2022 19:14
@github-actions
Copy link

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

@github-actions
Copy link

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 Dec 31, 2022
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.

None yet

2 participants