Closed aureq closed 1 month ago
Hi @aureq, to follow up my comment on https://github.com/pulumi/pulumi-azure-native/issues/3521#issuecomment-2296618682 - this is expected behaviour of the Pulumi engine. This is due to Pulumi not running the user program during a refresh or destroy operation - and it's the user's program which defines how stack outputs get their values.
This is being tracked and worked on in https://github.com/pulumi/pulumi/issues/16600
What happened?
This issue is related to #3521
When I deploy the Pulumi app below, everything works as expected during the 1st deployment and the stack output outboundIpAddresses shows the same value as the Azure portal ✔.
However as explained in #3521, changing the
sku
of theAppServicePlan
causes theWebApp
outbound IP addresses to change but not having the new value shown in the stack output ❌.So, I tried to run a
refresh
to force the resource state to be updated with the latest details present in the Azure Portal but no changes were displayed ❌ despite the operation completing correctly.Only running an
up
after therefresh
, and despite no code changes, forced the stack output to be updated with the new outbound IP addresses.Example
Steps to reproduce:
p up --yes --skip-preview --logtostderr --verbose=9 2> pulumi-up-1.log
✔sku
in the AppServicePlan resourcep up --yes --skip-preview --logtostderr --verbose=9 2> pulumi-up-2.log
✔p up --yes --skip-preview --logtostderr --verbose=9 2> pulumi-up-3.log
(with no code changes) ✔p refresh --yes --skip-preview --logtostderr --verbose=9 2> pulumi-refresh-4.log
✔p up --yes --skip-preview --logtostderr --verbose=9 2> pulumi-up-5.log
(with no code changes) ✔Output of
pulumi about
Additional context
The verbose logs are in this logs.tar.gz archive.
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).