Open KaoruDev opened 2 years ago
Thanks for the report. Yes it sounds like some unexpected behaviour. We'll add this to our backlog to investigate and try to reproduce.
For others who have encountered this, adding fingerprint
to ignoreChanges
option will work.
I encountered a similar error and I "fixed" it by adding this code:
{ ignoreChanges: ["fingerprint", "privateIpGoogleAccess", "secondaryIpRanges"] }
Hello!
Issue details
When I run
pulumi refresh
on a stack with a Subnet with a GKE cluster in it, I'm asked to update the outputs with afingerprint
property.Steps to reproduce
pulumi refresh
, prompt should ask you to update outputs of subnet with fingerprintpulumi up
notice that there will be an update request, the diff explains a newfingerprint
as aninput
.Expected: Refresh to work and subsequent update to not fail. Actual: Received this error:
I had to manually remove
fingerprint
Inputs from the stack json to fix the issue.