fix: change IAM permission configuration from binding to member to avoid issues with permission granted from other sources #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Type
Bug fix
Description
• Change IAM binding to member for workload identity
• Fix conflicts with multiple role bindings
• Update documentation and changelog
• Prevent permission management issues
Changes walkthrough 📝
main.tf
Replace IAM binding with member resourcemain.tf
• Replace
google_service_account_iam_bindingwithgoogle_service_account_iam_member• Change
membersarray to singlememberparameter• Simplify IAM role assignment structure
CHANGELOG.md
Add changelog entry for IAM fixCHANGELOG.md
• Add version 0.3.1 entry with release date
• Document IAM binding to
member change
• Explain rationale for avoiding multiple binding
conflicts
README.md
Update resource documentation referenceREADME.md
• Update resource reference from
google_service_account_iam_bindingtogoogle_service_account_iam_member