This message was deleted.
# azures
sparse-intern-71089
08/30/2021, 3:40 AMThis message was deleted.
k
kind-mechanic-53546
08/30/2021, 3:42 AMDue to the interconnected nature of pulumi's components, it makes it somewhat difficult as there's no supported way to inject new secrets if we override it in the console (or via cli)
kind-mechanic-53546
08/30/2021, 3:42 AMMy current thoughts are I'll just have to introduce a new secret and then use that if set as an override
kind-mechanic-53546
08/30/2021, 3:42 AMWould love a better way
b
brave-winter-60074
08/30/2021, 5:53 AMWe have dont it and are using pulumi
brave-winter-60074
08/30/2021, 5:54 AMBut maybe our setup differes, we regnerated the keys and ran our pipelies where pulumi up is run, in our pulumi code we get the connectionstring from the cosmosdb account and uses that in our function app. So when the value have changed (pulumi getting the key) it was automatically updated
k
kind-mechanic-53546
08/30/2021, 7:15 AMhuh, that's great news, thank you, I'll have to try it later on
b
brave-winter-60074
08/30/2021, 10:55 AMregenerated through the azure portal console and just ran our pulumi again
t
tall-librarian-49374
08/31/2021, 7:08 AMIndeed, I’d expect it to be 1. regenerate the keys manually (portal, CLI, etc) 2. pulumi refresh 3. pulumi up
3 Views