Made User Agent configurable post Cosmos client creation #32325
+32
−3
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.
Packages impacted by this PR
@azure/cosmos
Issues associated with this PR
#32191
Describe the problem that is addressed by this PR
Currently there is no way to change user agent once CosmosClient has been created.But with addition of CosmosDB Integrations with AI libraries like Langchain and LlamaIndex, we want to track the adoption. Users can pass the CosmosClient instance itself during initialization of different stores (eg. vectorStore) which leads to default value of user-agent getting used and does not help in tracking adoption of these AI libraries. Also, if connectionString is passed, there is no way to set other CosmosClientOptions.
After merging this PR we will be able to :