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_cosmosdb_sql_container: fix issue about removing analytical_storage_ttl needs to force replacement #16229

Merged
merged 1 commit into from
Apr 6, 2022

Conversation

sinbai
Copy link
Contributor

@sinbai sinbai commented Apr 2, 2022

The purpose of this PR:

Since the analytical_storage_ttl could not be changed back once enabled on an existing container, so it needs to force replacement in this case.

Fix issue #16183 .

TestResult:

PASS: TestAccCosmosDbSqlContainer_analyticalStorageTTL (1306.66s)

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.

Thanks @sinbai - LGTM 🦀

@katbyte katbyte merged commit 3026d2a into hashicorp:main Apr 6, 2022
@github-actions github-actions bot added this to the v3.1.0 milestone Apr 6, 2022
katbyte added a commit that referenced this pull request Apr 6, 2022
@sinbai sinbai deleted the cosmos/fix_issue_16183 branch April 6, 2022 02:11
@github-actions
Copy link

github-actions bot commented Apr 8, 2022

This functionality has been released in v3.1.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

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 10, 2022
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.

2 participants