From 085aa730b60d0c6ae7dfa18f09a3da0306493986 Mon Sep 17 00:00:00 2001 From: Alex <8507196+Fructokinase@users.noreply.github.com> Date: Fri, 16 Dec 2022 13:30:53 -0800 Subject: [PATCH] Stanford Staging: Do not inherit Stanford prod config (#1898) It is easy to make mistakes if the staging config is inherited from prod config. For example, the staging instance is currently trying to read the prod GCS bucket because the GCS bucket is not set explicitly in config. ![image](https://user-images.githubusercontent.com/8507196/208184003-d817889a-f604-4b58-a009-812d3c63a2ff.png) Co-authored-by: Alex Chen --- server/configmodule.py | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/server/configmodule.py b/server/configmodule.py index 71feaa0d8a..0cb3cd6f9b 100644 --- a/server/configmodule.py +++ b/server/configmodule.py @@ -83,8 +83,12 @@ class StanfordConfig(CustomConfig): GCS_BUCKET = 'datcom-stanford-resources' -class StanfordStagingConfig(StanfordConfig): +class StanfordStagingConfig(CustomConfig): NAME = "Google Stanford Data Commons (Staging)" + ENV_NAME = 'STANFORD' + ENABLE_BLOCKLIST = True + BASE_HTML_PATH = 'custom_dc/stanford/base.html' + GCS_BUCKET = 'datcom-stanford-staging-resources' API_PROJECT = 'datcom-mixer-statvar' SECRET_PROJECT = 'datcom-stanford-staging'