Open hqva opened 1 year ago
Looks like this is expected behaviour, as the cosmos client with RBAC is only to read/write data and not for resource provisioning - including database or container creation
I think we're gonna have to fart about with azure.mgmt.cosmosdb.CosmosDBManagementClient to actually create containers and databases 🤔 ?like this
@jedheaj314 Have I completely lost the plot?
Is it then simplest to make it part of the terraform/ initial provisioning process when the seedlings are initially made? Give app developers a single prescribed database and container that is then used for all state storage?
New containers or databases cannot be created with the cosmos client despite the user having permissions to do so.
This is the case both
DefaultAzureCredential()
for a user that has permissions to create a container via the azure portalCOSMOSDB_KEY
This bug can be reproduced with the following code: