I was excited to automate Docker container builds using Google Cloud Build: merge a PR into the main branch, and a few minutes later a container is ready. It was gonna be all cool and CI/CD and stuff.
Following best practices, I created a bot account to avoid saving my personal account's access token into the project's secret manager. So far so good.
But, because the repo is my personal repo, it doesn't show up in the bot's repo list on Cloud Build. You need to make the bot an admin, but that's not possible for repos outside an organization. (Right?)
What to do?
- Just put the repo in an organization? (so I can make the bot an admin)
- Use GitHub actions to trigger a Cloud Build job running as a GCP service account? (and store the login secret in the repo?)
- ...?
Top comments (0)