From ced60c6dee25021856eb8696e61bd46de128ce3e Mon Sep 17 00:00:00 2001 From: Robby Date: Sat, 24 Oct 2020 07:30:57 +0800 Subject: [PATCH] Fix cloud build readme (#193) * Fix readme * Update readme * Fix grammar Co-authored-by: Averi Kitsch --- example-workflows/cloud-build/README.md | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-) diff --git a/example-workflows/cloud-build/README.md b/example-workflows/cloud-build/README.md index a4bf66d7..52246ea8 100644 --- a/example-workflows/cloud-build/README.md +++ b/example-workflows/cloud-build/README.md @@ -46,21 +46,9 @@ For pushes to the `master` branch, this workflow will: 1. Add the the following [Cloud IAM roles][roles] to your service account: - - `Cloud Build Admin` - allows for the creation of new services - - - `Cloud Build Editor` - allows for deploying cloud builds - - - `Cloud Build Service Account` - allows for deploying cloud builds - - - `Viewer` - allows for viewing the project - - - `Service Account User` - required to deploy services to Cloud Build - - Note: These permissions are overly broad to favor a quick start. They do not - represent best practices around the Principle of Least Privledge. To - properly restrict access, you should create a custom IAM role with the most - restrictive permissions. + - [`Cloud Build Service Account`](https://cloud.google.com/cloud-build/docs/cloud-build-service-account) - allows for execution of builds on your behalf + - `Viewer` - allows for Cloud Build log storage 1. [Create a JSON service account key][create-key] for the service account.