[FAST] Fix IAM bindings to impersonate resman CICD SAs at bootstrap stage #2411
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.
Resolved an issue that appeared when applying FAST's bootstrap stage where merging blocks with conflicting key names were utilised to apply IAM bindings for service account impersonation between service accounts involved in CICD workload authorisation. This conflict resulted in only the final IAM binding from the merge block being applied, leading to incomplete and therefore incorrect IAM configurations that manifested itself during deployments using GitHub Actions.
Checklist
I applicable, I acknowledge that I have:
terraform fmt
on all modified filestools/tfdoc.py