Implement CosmosDBOptions to allow configuration of the CosmosDB service client via CosmosClientOptions #2514
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.
Issue describing the changes in this PR
resolves #2450
Pull request checklist
release_notes.md
Additional information
Implement CosmosDBOptions for the cosmos extension that will expose
CosmosClientOptions
and allow users to configure the CosmosClient.Breaking Change
Due to the default value for ConnectionMode in CosmosClientOptions being Direct, this change will introduce a breaking change for users who rely on the implicit default connection mode being Gateway. Currently, this extension has defaulted to using Gateway a the connection mode. Now that we are exposing CosmosClientOptions, we cannot differentiate between a user explicitly setting the connection mode to Direct and the SDK's default value of Direct. Therefore, we have to default to the SDK's default value.
If there are alternative approaches to this, please let me know!