No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi, I encountered an error trying to update non-cmk CosmosDB with CMK. I get this error
``` ~  azure-native:cosmosdb:DatabaseAccount &lt;cosmos name&gt; updating (1s) [diff: +keyVaultKeyUri]; 
error: Status=400 Code=\"BadRequest\" Message=\"{\"code\":\"BadRequest\",\"message\":\"Cannot Update Customer Managed Key Settings And Other Properties at the same time.\\r\```
Could you advise how to handle that? Manual change + refresh, while possible, is not desired, as we use pulumi automation to handle cosmoses as a platform and there are thousands of them :sweat_smile:

Thanks, Grzesiek

Hmmm this sounds tricky. I haven't worked with these keys directly, but it sounds like azure enforces only changing settings or properties of keys one at a time?

Is updating all the key properties at the same time going to be a typical operation, or do you think this is a one time thing?

That `keyVaultKeyUri` is single string property with keyvault key URI. I guess the issue is with pulumi or ARM API limitation that update's more than what's listed here. When I create new cosmos with CMK key being set, it works nice, but upgrade non-cmk to cmk fails ;c