Open akauppi opened 2 years ago
Maybe not create the project. Just populate it with the right settings, which really is the repetitive part.
This should be in the ci
folder, a script similar to the first/deploy.sh
.
Provides the deployment project's @cloudbuild
service account with the rights it needs, to its own resources. Identify as the human Owner
of the project, so we can grant such rights (Cloud Build wouldn't be able to, since it's the one needing them..).
Also otherwise, try to reduce the amount of documentation, and manual steps, needed for setting up a new project.
This is something to be done after the developer already has worked on their first project, and set up CI/CD.
At that stage, they have
gcloud
set up. We'll use it and maybefirebase-tools
(as infirst
).Consider implementing as a Cloud Build script - like CI are.