Prerequisites
Before starting, ensure you have the following:1. Google Cloud Setup
- gcloud CLI installed: Install the gcloud CLI
- Authenticated with Google Cloud: Run
gcloud auth login
to authenticate - Project ID configured: Set your project with
gcloud config set project YOUR_PROJECT_ID
- Billing enabled: Ensure billing is enabled for your GCP project
2. Docker
- Docker daemon running: Ensure Docker is installed and running on your machine
- Docker authenticated: You’ll need to authenticate with both Docker Hub and Google Artifact Registry
3. AWS Resources
- S3 bucket created: Create an S3 bucket for storing Terraform state and artifacts
- AWS credentials: Have your AWS Access Key ID and Secret Access Key ready
- IAM permissions: Ensure your AWS credentials have permissions to read/write to the S3 bucket
4. Auth0 Setup
- Auth0 application: Create an Auth0 application and note your domain, client ID, and client secret. You should follow the guide in Configure SSO, you won’t have the server url until the server is up but you don’t need to set that right away.
Configuration
For GCP, you’ll need to set up environment variables and then deploy to Cloud Run. First, create acloud-run.env.yaml
file with your configuration:
[GCP URL]/oauth/oidc-callback
.
Mine looks like this: https://statesman-1234567890.us-central1.run.app/oauth/oidc-callback

taco login
. If you have not setup taco before it will prompt you for a server url. If you have run taco login before, you can do taco setup
to configure the server url. In either case you would set the cloud run url as the server url.
When the CLI asked me to enter my OpenTaco server url I pasted in: https://statesman-1234567890.us-central1.run.app