Skip to content

chore(deploy): Configure the Sentry GCP deployment - #5

Merged
dcramer merged 1 commit into
mainfrom
deploy/sentry-gcp-config
Oct 10, 2026
Merged

dcramer merged 1 commit into
mainfrom
deploy/sentry-gcp-config

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

Commits the values for Sentry's Roach deployment, so getting it running only needs gcloud auth application-default login, terraform init, and terraform apply -var-file=roach.tfvars.

  • versions.tf now turns on the GCS state backend, using the private bucket roach-511216-tfstate-dc-k4m9v2qx in project roach-511216.
  • roach.tfvars.example is renamed to a committed roach.tfvars, with project roach-511216 and domain roach-proxy.sentry.dev. The allow list and value patterns stay as they were.
  • The file holds no secrets. Terraform creates the CA key and write token and keeps them only in the state bucket. The Sentry DSN comes from TF_VAR_sentry_dsn.

DNS for roach-proxy.sentry.dev still has to point at the ip_address output after the first apply.

via David Cramer.

--

View Junior Session [Sentry]

Commit the Terraform state backend and the tfvars of the Sentry
deployment, so applying needs no local setup beyond gcloud login.

Co-Authored-By: David Cramer <david@sentry.io>
@dcramer
dcramer merged commit 776f138 into main Oct 10, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant