-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pulumi refresh : gcp:projects:IAMMember -> update [diff: ~etag] | ALL resource #751
Comments
Hi, thanks for writing this up. What's the impact of accepting the updated etag apart from the resources in the stack being updated?
|
should be usefull to manage this etag update cause it take a lot of time when you manage a lot of iam role. |
Unfortunately, it looks like this issue hasn't seen any updates in a while. If you're still encountering this problem, could you leave a quick comment to let us know so we can prioritize it? |
I'm no longer using gcp and pulumi so I don't know but my example was reproductible |
I suspect we would have heard a lot more complaints by now if it was still a problem, but we'll take a moment to try to repro on latest. |
This no longer reproes on the latest pulumi-gcp. Please open a new issue if anyone is still having problems with this. |
Hello!
Issue details
running
pulumi refresh
on a stack without any change always update ALL my IAMMember ( I have 291 IAMMember in my stack )because the etag "changed"
So every pulumi refresh show me
Steps to reproduce
in the "details" of pulumi refresh it show me
If I enter YES then
The text was updated successfully, but these errors were encountered: