Skip to content

Latest commit

 

History

History

serverless-scheduler-proxy

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
.gitignore
.gitignore
 
 
Dockerfile
Dockerfile
 
 
README.md
README.md
 
 
cloudbuild-test.yaml
cloudbuild-test.yaml
 
 
cloudbuild.yaml
cloudbuild.yaml
 
 
go.mod
go.mod
 
 
go.sum
go.sum
 
 
main.go
main.go
 
 

README.md

serverless-scheduler-proxy

This application acts as a springboard to the bots running in Cloud Functions from Cloud Scheduler

Pre Reqs

By default, Cloud Run instances are deployed within your Project's VPC, and service accounts in the project must be given the run.invoker role in order to actually hit the endpoint. If they are not, Cloud IAM will prevent the request from hitting the application.

  1. A Google Cloud Service Account that can invoke Cloud Run
gcloud iam service-accounts create serverless-proxy-cron \
   --display-name "Serverless Scheduler Proxy Cron"
  1. A role or binding to the Service Account
gcloud beta run services add-iam-policy-binding serverless-scheduler-proxy \
   --region=REGION
   --member=serviceAccount:[email protected] \
   --role=roles/run.invoker
  1. An AppEngine app to host the scheduler in.
gcloud app create --region=REGION
  1. Enable your project to create Cloud Pub/Sub authentication tokens.
gcloud projects add-iam-policy-binding PROJECT-ID \
     --member=serviceAccount:[email protected] \
     --role=roles/iam.serviceAccountTokenCreator

Create a PubSub Subscription

To use a PubSub Topic/Subscription with this proxy, it must be made with the proper Service Account

gcloud beta pubsub subscriptions create cloudRunSubscription --topic TOPICNAME \
   --push-endpoint=SERVICE-URL/v0/pubsub \
   --push-auth-service-account=serverless-proxy-cron@PROJECT-ID.iam.gserviceaccount.com