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

fix: activate_api_identities throwing error that email can't be null #840

Conversation

abhikaddy
Copy link
Contributor

Attempting to fix #751

@abhikaddy abhikaddy requested a review from a team as a code owner October 3, 2023 09:08
@abhikaddy
Copy link
Contributor Author

HI @bharathkkb @morgante @apeabody - Good Day!
Can I get a review?

@apeabody
Copy link
Contributor

apeabody commented Oct 5, 2023

/gcbrun

@apeabody
Copy link
Contributor

apeabody commented Oct 6, 2023

/gcbrun

@apeabody
Copy link
Contributor

apeabody commented Oct 6, 2023

Hi @abhikaddy - From the INT test

Error: Invalid for_each argument

  on ../../../modules/project_services/main.tf line 80, in resource "google_project_iam_member" "project_service_identity_roles":
  80:   for_each = {
  81:     for k, v in local.add_service_roles : k => v if v.email != null
  82:   }
    ├────────────────
    │ local.add_service_roles is object with 2 attributes

The "for_each" map includes keys derived from resource attributes that cannot
be determined until apply, and so Terraform cannot determine the full set of
keys that will identify the instances of this resource.

@abhikaddy
Copy link
Contributor Author

Looks like this scenario was already taken care by some other commit. Closing the pull request.

@abhikaddy abhikaddy closed this Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"activate_api_identities"throwing error that email can't be null
2 participants