azurerm_cosmosdb_sql_container
- add force new condition for partition_key_version
property
#27692
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Note
Description
After verifying the Azure API behavior, I found that if
partition_key_version
is not specified when creatingazurerm_cosmosdb_sql_container
, the Azure API allows updatingpartition_key_version
to1
, but not to2
.Given the above API behavior, I submitted this PR to allow
partition_key_version
to be updated1
when it was not specified before to fix the situation where resource should not be recreated.PR Checklist
For example: “
resource_name_here
- description of change e.g. adding propertynew_property_name_here
”Changes to existing Resource / Data Source
Testing
PASS: TestAccCosmosDbSqlContainer_update (1376.44s)
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_cosmosdb_sql_container
- add force new condition forpartition_key_version
propertyThis is a (please select all that apply):