Skip to content
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

Closed
raphaelauv opened this issue Feb 17, 2022 · 6 comments
Labels
kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced

Comments

@raphaelauv
Copy link

raphaelauv commented Feb 17, 2022

Hello!

  • 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)

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

    ~ 291 to update
    46 unchanged

Steps to reproduce

gcp.projects.IAMMember("[email protected]",
                       member="user:[email protected]",
                       project=PROJECT,
                       role="roles/bigquery.admin",
                       opts=pulumi.ResourceOptions(parent=ALL_RESOURCE, protect=True))
                          

in the "details" of pulumi refresh it show me

~ gcp:projects/iAMMember:IAMMember: (update) 🔒
    [id=XXXXXXXXXXX/roles/bigquery.admin/user:[email protected]]
    [urn=urn:pulumi:XXXXXX-prod::XXXXX::gcp:component:all_resource$gcp:projects/iAMMember:IAMMember::[email protected]]
    [provider=urn:pulumi:XXXXXXXXX-prod::XXXXX::pulumi:providers:gcp::default_gcp::XXX-XXXXXX-XXXXXX-XXXXX]
    --outputs:--
  ~ etag     : "BwXXqDCxmSw=" => "BwXYJjvSbgA="

If I enter YES then

Resources:
    ~ 291 updated
    46 unchanged

Duration: 1m47s
@raphaelauv raphaelauv added the kind/bug Some behavior is incorrect or out of spec label Feb 17, 2022
@raphaelauv raphaelauv changed the title Pulumi refresh : gcp:projects:IAMMember -> update [diff: ~etag] Pulumi refresh : gcp:projects:IAMMember -> update [diff: ~etag] | ALL resource Feb 17, 2022
@danielrbradley
Copy link
Member

Hi, thanks for writing this up.

What's the impact of accepting the updated etag apart from the resources in the stack being updated?

  • Does this cause all resources to be updated on the next deployment?
  • Is there a knock on impact in your process if you detect resources being changed?

@didlawowo
Copy link

should be usefull to manage this etag update cause it take a lot of time when you manage a lot of iam role.

@mjeffryes
Copy link
Member

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?

@mjeffryes mjeffryes added the awaiting-feedback Blocked on input from the author label Sep 25, 2024
@raphaelauv
Copy link
Author

I'm no longer using gcp and pulumi so I don't know but my example was reproductible

@pulumi-bot pulumi-bot added needs-triage Needs attention from the triage team and removed awaiting-feedback Blocked on input from the author labels Sep 27, 2024
@mjeffryes
Copy link
Member

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.

@VenelinMartinov VenelinMartinov added resolution/no-repro This issue wasn't able to be reproduced and removed needs-triage Needs attention from the triage team labels Sep 30, 2024
@VenelinMartinov
Copy link
Contributor

VenelinMartinov commented Sep 30, 2024

This no longer reproes on the latest pulumi-gcp. Please open a new issue if anyone is still having problems with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced
Projects
None yet
Development

No branches or pull requests

6 participants