Open iwahbe opened 2 weeks ago
Which bit does not work here?
Also is this different with storage Bucket? If so, then this might be a duplicate of https://github.com/pulumi/pulumi-gcp/issues/1959
When we run the normal cycle, we see that pulumi refresh --yes
doesn't generate any diff. When the refresh runs (--yes
), no changes are shown but the next pulumi up
will add the missing unmanaged labels to effectiveLabels
.
This is primarily about the refresh behavior, so it is not a duplicate of https://github.com/pulumi/pulumi-gcp/issues/1959.
Does that happen without the refresh? AFAIK up
actually does an implicit Read of the labels on the cloud resource
Either way, this doesn't seem like a huge issue to me - effectiveLabels
is meant to represent the actual labels on the resource, so it is expected to change when unmanaged labels change.
Does that happen without the refresh? AFAIK
up
actually does an implicit Read of the labels on the cloud resource
Only with refresh.
Either way, this doesn't seem like a huge issue to me - effectiveLabels is meant to represent the actual labels on the resource, so it is expected to change when unmanaged labels change.
pulumi up --yes && pulumi refresh --yes && pulumi preview --expect-no-changes
should always succeed. In the case of the above, the refresh should show a diff (but doesn't) and the second update shouldn't have a diff (but it has the diff that refresh should have had).
The final result is correct, but the order is very wrong.
Describe what happened
I expect that
refresh
works well with unmanaged labels.We should be able to run for the sample program
pulumi up --yes && pulumi refresh --yes && pulumi preview --expect-no-changes
.Sample program
Log output
NA
Affected Resource(s)
No response
Output of
pulumi about
NA
Additional context
No response
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).