From 795639ec8e518819d74bbe37b750ab48537fd147 Mon Sep 17 00:00:00 2001 From: Marc LeBlanc <7050295+marcleblanc2@users.noreply.github.com> Date: Wed, 21 Oct 2026 15:04:06 -0600 Subject: [PATCH] Add migrator to the outbound HTTP proxy example migrator's drift, upgrade, and downgrade commands call releaseregistry.sourcegraph.com and storage.googleapis.com before touching the databases. Route them through the proxy alongside frontend and worker. --- .../outbound-http-proxy/docker-compose.override.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docker-compose/examples/outbound-http-proxy/docker-compose.override.yaml b/docker-compose/examples/outbound-http-proxy/docker-compose.override.yaml index f44001812..3045b3ed3 100644 --- a/docker-compose/examples/outbound-http-proxy/docker-compose.override.yaml +++ b/docker-compose/examples/outbound-http-proxy/docker-compose.override.yaml @@ -60,6 +60,13 @@ services: # environment: # <<: *proxy-env-vars + # The default `up` command makes no outbound connections + # `drift`, `upgrade`, and `downgrade` check releaseregistry.sourcegraph.com for a newer migrator version, + # and storage.googleapis.com for schema descriptions + migrator: + environment: + <<: *proxy-env-vars + worker: environment: <<: *proxy-env-vars