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

azurerm_site_recovery_replication_recovery_plan: keep the order of pre_action post_action properties #22019

Merged
merged 1 commit into from
Jun 9, 2023

Conversation

ziyeqf
Copy link
Contributor

@ziyeqf ziyeqf commented Jun 2, 2023

fix #21963

Screenshot 2023-06-02 at 15 46 05

Signed-off-by: ziyeqf <51212351+ziyeqf@users.noreply.github.com>
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🖥️

@katbyte katbyte merged commit 49fe110 into hashicorp:main Jun 9, 2023
@katbyte katbyte changed the title azurerm_site_recovery_replication_recovery_plan: keep the order of actions azurerm_site_recovery_replication_recovery_plan: keep the order of pre_action post_action properties Jun 9, 2023
@github-actions github-actions bot added this to the v3.60.0 milestone Jun 9, 2023
katbyte added a commit that referenced this pull request Jun 9, 2023
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 May 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

azurerm_site_recovery_replication_recovery_plan does not keep order of pre/post_actions
2 participants