{"push_id":3811536557,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"f542c901006883efe395c3b8067b0edc81996b7e","before":"1fcb1d8f6a839339167ea64cbd22038b391b7015","commits":[{"sha":"9e1d7946c43a4a382090588ff41dc604f29eee72","author":{"name":"Joel Diaz","email":"677858055ae38e55732e784e4f8018a1699a6f55@redhat.com"},"message":"implement GCP passthrough mode (and add service API checks)\n\n- [x] handle the case when the root creds are in passthrough mode.\n- [x] add checks for passthrough and mint mode where we check that the service APIs are enabled/available before proceeding to process the CredentialsRequest.\n\nNote that passthrough mode is handled differently than in AWS. In AWS we work with a static list of permissions that are needed for the cluster to run with. For GCP passthrough mode, the decision on whether we can satisfy a CredentialsRequest is dynamic. All we absolutely need for passthrough mode is the ability to list service APIs (to determine whether any particular service API is enabled), the ability to get the details for a specific role (so we can determine whether the role exists and the permissions attached to that role), and the ability to get the details of a project (so we can get the project number for a given project name). All the other permissions attached to the root creds in passthrough mode would pass/fail a permissions check during the TestIamPermissions() call.","distinct":false,"url":"https://api.github.com/repos/joelddiaz/cloud-credential-operator/commits/9e1d7946c43a4a382090588ff41dc604f29eee72"},{"sha":"f542c901006883efe395c3b8067b0edc81996b7e","author":{"name":"OpenShift Merge Robot","email":"dd8cc73a9fcbc4f2f987fe818c87bd17f8347a2c@users.noreply.github.com"},"message":"Merge pull request #86 from joelddiaz/gcp-passthrough\n\nimplement GCP passthrough mode (and add service API checks)","distinct":true,"url":"https://api.github.com/repos/joelddiaz/cloud-credential-operator/commits/f542c901006883efe395c3b8067b0edc81996b7e"}]}
{"actor":{"display_login":"joelddiaz"}}