How do I set up the GCP project for Applane?
Every option enables the five APIs, grants roles/aiplatform.user to the builders group, and optionally creates a budget alert. Review the planned additions before applying them. Choose the option that fits your team’s infrastructure ownership and change process.
| Option | Pick it when | Needs |
|---|---|---|
| Open in Cloud Shell | You want a one-off by hand with nothing installed. A guided panel in your browser. | A browser and project rights. |
| Infrastructure Manager | The project should be Terraform-managed but nobody wants to run Terraform from a laptop. Google runs it and keeps the state. | gcloud, roles/config.admin. |
| Terraform | The project’s APIs and IAM already live in your own Terraform. You want these resources tracked alongside the rest of your configuration. | Terraform 1.15+, provider hashicorp/google 6.x. |
| Script | gcloud is already signed in with API enablement and project IAM permissions. Prints every command before running it; --dry-run first. |
gcloud 400+, bash 3.2+. |
Two steps stay manual whatever you pick, because Google has no API for them: the OAuth consent screen and the OAuth client. They take five minutes in the Cloud console, and every option prints the instructions when it finishes.
Before you start, have these values ready:
| Value | Where it comes from |
|---|---|
<GCP_PROJECT_ID> |
The project. See Prerequisites. |
applane-builders@<YOUR_DOMAIN> |
The builders group. The Workspace admin creates it: Accounts and groups. |
<BILLING_ACCOUNT_ID> |
Optional, for the budget alert. gcloud billing projects describe <GCP_PROJECT_ID> --format='value(billingAccountName)' |
For AI agents: llms.txt, llms-full.txt, or any page with a .md suffix.