feat(cosmosdb_sql_container): including indexing_policy
setting for CosmosDB SQL Container
#402
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.
This PR contains an improvement on CosmosDB container's TF resource: as defined in official documentation, there is an option that permits to explicitly define a policy about indexing strategy. In particular, there is the possibility to define complex indexes that includes multiple fields into a single index (like compound indexes defined for MongoDB).
This could be useful in most cases where more intensive query are required to be executed.
These updates are made in order to not cause regression from the currently defined structure and are backward compatible with previous versions of the resource
cosmosdb_sql_container
.List of changes
indexing_policy
object incosmosdb_sql_container
componentMotivation and context
These changes are required in order to permits the definition of custom complex indexes on CosmosDB SQL containers
Type of changes
Does this introduce a breaking change?
Other information
Run checks
Useful commands to run checks on local machine
bash .utils/terraform_run_all.sh init local pre-commit run -a