cloud_functions: Create <env>-cloudbuild.yaml

Create staging-cloudbuild.yaml for the staging env and
prod-cloudbuild.yaml for the prod env. Update README with new
automatic deployment details

BUG=b:264670075
TEST=gcloud cli

Change-Id: I4ba8fed4199cb38bc70dafe3d2cb387b8608c258
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/build/prebuilts-cloud/+/5066863
Tested-by: GCB User <782851717939@cloudbuild.gserviceaccount.com>
Commit-Queue: Cindy Lin <xcl@google.com>
Reviewed-by: Nikhil Gumidelli <nikhilgm@google.com>
diff --git a/README.md b/README.md
index c111914..196b51f 100644
--- a/README.md
+++ b/README.md
@@ -14,16 +14,16 @@
 ### Deployment
 
 **All changes, once uploaded to Gerrit, are deployed to staging automatically.
-DO NOT deploy to production instances as the production deployment process will be automated later.**
+All changes, once merged, are deployed to production automatically.**
 
-We use Proctor/Cloud Build Integrations ([go/gcb-ggob](https://g3doc.corp.google.com/devtools/proctor/g3doc/user/ggob.md?cl=head)) to automatically deploy changes. A Cloud Build build is triggered whenever a new Gerrit patchset is uploaded in the `prebuilts-cloud` project. See [here](https://pantheon.corp.google.com/cloud-build/triggers?e=-13802955&mods=component_inspector&project=chromeos-prebuilts) for details on the Cloud Build trigger setup through Proctor.
+We use Proctor/Cloud Build Integrations ([go/gcb-ggob](https://g3doc.corp.google.com/devtools/proctor/g3doc/user/ggob.md?cl=head)) to automatically deploy changes. A Cloud Build build is triggered whenever a new Gerrit patchset is uploaded in the `prebuilts-cloud` project for the staging environment. See [here](https://pantheon.corp.google.com/cloud-build/triggers?e=-13802955&mods=component_inspector&project=chromeos-prebuilts) for details on the Cloud Build trigger setup through Proctor.
 
 During a build, a few things happen:
 * A Google Cloud Storage object is created containing the source code. The exact location can be determined by inspecting the build logs. [Example](https://screenshot.googleplex.com/GJ36QD8vhu53xv6).
 * A new version of the specified Cloud Function is deployed with 100% traffic.
 * The GCB User will add the Verified+1 label and a comment to your Gerrit change upon a successful build. [Example](https://screenshot.googleplex.com/tH2VEQZ3h8mZgHW).
 
-A Cloud Build trigger can be run manually by following the steps [here](go/gcb-ggob#running-triggers).
+A Cloud Build trigger can be run manually by following the steps [here](go/gcb-ggob#running-triggers). Once a CL successfully merged, a separate trigger deploys the latest source code to production.
 
 #### Runtime environment variables for the lookup service cloud function:
 
diff --git a/cloud_functions/prod-cloudbuild.yaml b/cloud_functions/prod-cloudbuild.yaml
new file mode 100644
index 0000000..b84beac
--- /dev/null
+++ b/cloud_functions/prod-cloudbuild.yaml
@@ -0,0 +1,40 @@
+steps:
+- name: 'gcr.io/google.com/cloudsdktool/cloud-sdk'
+  dir: 'cloud_functions'
+  args:
+  - gcloud
+  - functions
+  - deploy
+  - prod-lookup-service-binhosts
+  - --gen2
+  - --region=us-central1
+  - --source=.
+  - --trigger-http
+  - --runtime=python38
+  - --entry-point=lookup_service_binhosts
+- name: 'gcr.io/google.com/cloudsdktool/cloud-sdk'
+  dir: 'cloud_functions'
+  args:
+  - gcloud
+  - functions
+  - deploy
+  - prod-update-service-binhost-data
+  - --gen2
+  - --region=us-central1
+  - --source=.
+  - --trigger-topic=prod-update_binhost_data
+  - --runtime=python38
+  - --entry-point=update_service
+- name: 'gcr.io/google.com/cloudsdktool/cloud-sdk'
+  dir: 'cloud_functions'
+  args:
+  - gcloud
+  - functions
+  - deploy
+  - prod-update-service-snapshot-data
+  - --gen2
+  - --region=us-central1
+  - --source=.
+  - --trigger-topic=prod-update_snapshot_data
+  - --runtime=python38
+  - --entry-point=update_service
diff --git a/cloud_functions/cloudbuild.yaml b/cloud_functions/staging-cloudbuild.yaml
similarity index 100%
rename from cloud_functions/cloudbuild.yaml
rename to cloud_functions/staging-cloudbuild.yaml