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_communication_service - add forceNew for data_location #20711

Merged
merged 1 commit into from
Mar 1, 2023

Conversation

neil-yechenwei
Copy link
Contributor

Recently I found the test case about communication is failed. After investigated, I found it would fail while changing data_location. Then I checked with service team. They confirmed that API doesn't support to in-place to update data_location. So we have to add forceNew for data_location.

--- PASS: TestAccCommunicationService_update (644.41s)
--- PASS: TestAccCommunicationService_basic (442.16s)
--- PASS: TestAccCommunicationService_complete (436.83s)
--- PASS: TestAccCommunicationService_requiresImport (488.58s)

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 95009ff into hashicorp:main Mar 1, 2023
@github-actions github-actions bot added this to the v3.46.0 milestone Mar 1, 2023
katbyte added a commit that referenced this pull request Mar 1, 2023
@github-actions
Copy link

github-actions bot commented Mar 6, 2023

This functionality has been released in v3.46.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

github-actions bot commented Apr 6, 2023

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 Apr 6, 2023
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.

None yet

2 participants