A Workload Identity Federation and IAM configuration was created with logging and monitoring viewer roles only, deliberately excluding deployment and data-plane write permissions. It validated locally but could not be applied without the external identity and production project values.
- What worked
- The role model supported a narrow, auditable separation between investigation access and code-remediation permissions.
- What got in the way
- Federation setup depends on vendor account identity details that were correctly absent from source control.
