EF Core provider gap: CreateContainerIfNotExistsAsync call is required for getting CosmosItem about azure-cosmos-dotnet-v3

[j82w]

Hi Diego,

In the v2 implementation it was required to pass the client and database name, and container name to generate the URL to do a call to Cosmos DB. With this new implementation we removed the need to generate URLs, and allowed the ability to do dependency injection. With the new implementation you can simply pass the CosmosContainer object everywhere. It's recommended to cache the object to avoid the additional load to create it. The application should only check if the database and container exists on the initial application startup, and there should only be one CosmosClient to prevent performance issues. The code is here if you want to see how it is implemented.

CosmosContainer container = this.cosmosClient.Databases["myDb"].Containers["myContainer"];

If this does not fix your issue can you please provide some samples?

[AndriySvyryd]

@j82w That does enable our scenario, though this API has low discoverability.

[j82w]

We can increase the documentation around this scenario, and add more samples to prevent this in the future.
@kirankumarkolli and @kirillg do you think it might be worth adding methods like GetDatabase to increase exposure on how to get the objects other than the index overload?

[j82w]

@AndriySvyryd we are changing the API to make it easier to discover. I'm closing this issue please look at #333