Release Registry infrastructure operations
This document describes operational guidance for Release Registry infrastructure. This service is operated on the Managed Services Platform (MSP).
If you need assistance with MSP infrastructure, reach out to the Core Services team in #discuss-core-services.
Service overview
| PROPERTY | DETAILS |
|---|---|
| Service ID | releaseregistry |
| Owners | dev-experience |
| Service kind | Cloud Run service |
| Environments | prod, dev |
| Docker image | us.gcr.io/sourcegraph-dev/releaseregistry |
| Source code | github.com/sourcegraph/releaseregistry - . |
Environments
prod
| PROPERTY | DETAILS |
|---|---|
| Project ID | releaseregistry-prod-5421 |
| Category | test |
| Resources | prod PostgreSQL instance |
| Alerts | GCP monitoring |
| Sentry | releaseregistry-prod |
| Domain | releaseregistry.sourcegraph.com |
| Cloudflare WAF | ✅ |
MSP infrastructure access needs to be requested using Entitle for time-bound privileges. Test environments may have less stringent requirements.
| ACCESS | ENTITLE REQUEST TEMPLATE |
|---|---|
| GCP project read access | Entitle request for the ‘Engineering Projects’ folder |
| GCP project write access | Entitle request for the ‘Engineering Projects’ folder |
For Terraform Cloud access, see prod Terraform Cloud.
prod Cloud Run
The Release Registry prod service implementation is deployed on Google Cloud Run.
| PROPERTY | DETAILS |
|---|---|
| Console | Cloud Run service |
| Service logs | GCP logging |
You can also use sg msp to quickly open a link to your service logs:
sg msp logs releaseregistry prod
prod PostgreSQL instance
| PROPERTY | DETAILS |
|---|---|
| Console | Cloud SQL instances |
| Databases | releaseregistry |
To connect to the PostgreSQL instance in this environment, use sg msp in the sourcegraph/managed-services repository:
# For read-only access
sg msp pg connect releaseregistry prod
# For write access - use with caution!
sg msp pg connect -write-access releaseregistry prod
prod Terraform Cloud
This service’s configuration is defined in sourcegraph/managed-services/services/releaseregistry/service.yaml, and sg msp generate releaseregistry prod generates the required infrastructure configuration for this environment in Terraform.
Terraform Cloud (TFC) workspaces specific to each service then provisions the required infrastructure from this configuration.
You may want to check your service environment’s TFC workspaces if a Terraform apply fails (reported via GitHub commit status checks in the sourcegraph/managed-services repository, or in #alerts-msp-tfc).
To access this environment’s Terraform Cloud workspaces, you will need to log in to Terraform Cloud and then request Entitle access to membership in the “Managed Services Platform Operator” TFC team. The “Managed Services Platform Operator” team has access to all MSP TFC workspaces.
The Terraform Cloud workspaces for this service environment are grouped under the msp-releaseregistry-prod tag, or you can use:
sg msp tfc view releaseregistry prod
dev
| PROPERTY | DETAILS |
|---|---|
| Project ID | releaseregistry-dev-6bac |
| Category | test |
| Resources | dev PostgreSQL instance |
| Alerts | GCP monitoring |
| Sentry | releaseregistry-dev |
| Domain | releaseregistry.sgdev.org |
| Cloudflare WAF | ✅ |
MSP infrastructure access needs to be requested using Entitle for time-bound privileges. Test environments may have less stringent requirements.
| ACCESS | ENTITLE REQUEST TEMPLATE |
|---|---|
| GCP project read access | Entitle request for the ‘Engineering Projects’ folder |
| GCP project write access | Entitle request for the ‘Engineering Projects’ folder |
For Terraform Cloud access, see dev Terraform Cloud.
dev Cloud Run
The Release Registry dev service implementation is deployed on Google Cloud Run.
| PROPERTY | DETAILS |
|---|---|
| Console | Cloud Run service |
| Service logs | GCP logging |
You can also use sg msp to quickly open a link to your service logs:
sg msp logs releaseregistry dev
dev PostgreSQL instance
| PROPERTY | DETAILS |
|---|---|
| Console | Cloud SQL instances |
| Databases | releaseregistry |
To connect to the PostgreSQL instance in this environment, use sg msp in the sourcegraph/managed-services repository:
# For read-only access
sg msp pg connect releaseregistry dev
# For write access - use with caution!
sg msp pg connect -write-access releaseregistry dev
dev Terraform Cloud
This service’s configuration is defined in sourcegraph/managed-services/services/releaseregistry/service.yaml, and sg msp generate releaseregistry dev generates the required infrastructure configuration for this environment in Terraform.
Terraform Cloud (TFC) workspaces specific to each service then provisions the required infrastructure from this configuration.
You may want to check your service environment’s TFC workspaces if a Terraform apply fails (reported via GitHub commit status checks in the sourcegraph/managed-services repository, or in #alerts-msp-tfc).
To access this environment’s Terraform Cloud workspaces, you will need to log in to Terraform Cloud and then request Entitle access to membership in the “Managed Services Platform Operator” TFC team. The “Managed Services Platform Operator” team has access to all MSP TFC workspaces.
The Terraform Cloud workspaces for this service environment are grouped under the msp-releaseregistry-dev tag, or you can use:
sg msp tfc view releaseregistry dev