google_bigquery_dataset_iam_member doesn't handle deleted members

[ralbertazzi]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Description

Opening again the issue described in #7896. Please reference that issue for all information. As I've written there, it seems that the provider fails parsing deleted: entities and Google's guidelines explicitly say that configuration-as-code tools should be updated to recognize the new prefix.

References

• google_bigquery_dataset_iam_member doesn't handle deleted members #7896

[slevenick]

Looks like this comment correctly identifies the problem code. This should only impact bigquery_dataset_iam resources due to the unique handling there.

Should be fixable with similar logic to https://github.com/GoogleCloudPlatform/magic-modules/blob/master/third_party/terraform/utils/iam.go.erb#L237

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!