This message was deleted.
# general
s
This message was deleted.
b
Just note that we figured out what's going on here, and will need to republish our v0.14.0 build. THANK YOU so much for finding and reporting this before we go broader!
@bitter-oil-46081 Is the brains here, so hoping he can provide an update soon.
Just got word that Matt is republishing, so we should be back in business shortly!
b
@flaky-continent-74538 Can you please try again? Things should be working now. If it exists, you should remove the
~/.pulumi/plugins/resource-azure-v0.14.0
directory and then force a reinstall by running
pulumi plugin install resource azure 0.14.0
To close the loop. I ran through an azure example on my Windows machine a few moments ago and the plugin was correctly downloaded and worked as expected. Thanks so much for the heads up @flaky-continent-74538 and let me know if you run into other problems.
f
Ah sorry! I got it working on my machine too! I got distracted by building out my app haha
b
That’s what we want! 😃
f
I am running into a minor problem actually
I'm messing around with an Azure
AppService
, and I tweaked its
appSettings
property. It seems that Pulumi doesn't detect changes when I move a value from a string to an Output<string>
I went from:
Copy code
appSettings: {
  "Hello": "World"
}
To:
Copy code
appSettings: {
  "Hello": all([output1, output2]).apply(([a, b]) => `${a} ${b}`)
}
Pulumi doesn't seem to catch the difference here. I was able to get around this by adding another fake setting
b
Hrm. That is interesting, I’ll need to take a more in-depth look tomorrow. It shouldn’t be anything specific to Azure, unless for some reason the provider itself doesn’t believe there’s a change (and hence actually doesn’t do an update itself). Do you mind opening an issue in pulumi-azure on GitHub so we don’t lose track?
f
Sure
Actually, scratch my last statement. When I go ahead and perform the update, I get an error. I'll make an issue with all this. Thanks!