Skip to content

Cosmos DB container updates for conversation history feature#423

Open
mateoperezrivera wants to merge 2 commits intoAzure:mainfrom
mateoperezrivera:main
Open

Cosmos DB container updates for conversation history feature#423
mateoperezrivera wants to merge 2 commits intoAzure:mainfrom
mateoperezrivera:main

Conversation

@mateoperezrivera
Copy link
Contributor

This pull request updates the CosmosDB container configuration and parameters to support custom partition keys and indexing policies, improving data organization and query performance. The changes also add a new database container for users and enhance role assignments for resource access.

CosmosDB container configuration improvements:

  • Updated the cosmosDBAccount module in infra/main.bicep to use custom partition keys from the container definitions, and to optionally apply custom indexing policies if provided.

Parameter enhancements for database containers:

  • Modified infra/main.parameters.json to specify partition keys for each container, including new keys for conversations, datasources, prompts, mcp, and a new chainlit_users container.
  • Added composite indexing policies for the conversations container to optimize queries by isDeleted, _ts, and name fields.

Access control updates:

  • Added the CosmosDBBuiltInDataContributor role to resource role assignments, enabling enhanced access to CosmosDB data.

mateoperezrivera and others added 2 commits February 27, 2026 15:49
Refactor Cosmos DB container configurations to include partition keys and indexing policies
…ctor

Cosmos DB containers optimized for conversation history
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant