Update how the analysis data is fetched

Vizzuality · Oct 8, 2024 · d5ce305 · d5ce305
1 parent 4d2b660
commit d5ce305
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 10 deletions.
diff --git a/frontend/.env.default b/frontend/.env.default
@@ -6,8 +6,7 @@ HUBSPOT_TOKEN=
 
 LOCALAZY_CDN=
 
-NEXT_PUBLIC_ANALYSIS_CF_MARINE_URL=
-NEXT_PUBLIC_ANALYSIS_CF_TERRESTRIAL_URL=
+NEXT_PUBLIC_ANALYSIS_CF_URL=
 NEXT_PUBLIC_FEATURE_FLAG_ANALYSIS=
 
 HTTP_AUTH_USERNAME=

diff --git a/frontend/src/containers/map/content/map/modelling/index.tsx b/frontend/src/containers/map/content/map/modelling/index.tsx
@@ -10,12 +10,10 @@ import { useSyncMapContentSettings } from '@/containers/map/sync-settings';
 import { ModellingData } from '@/types/modelling';
 
 const fetchModelling = async (tab: string, feature: Feature) => {
-  const url =
-    tab === 'marine'
-      ? process.env.NEXT_PUBLIC_ANALYSIS_CF_MARINE_URL
-      : process.env.NEXT_PUBLIC_ANALYSIS_CF_TERRESTRIAL_URL;
-
-  return axios.post<ModellingData>(url, feature);
+  return axios.post<ModellingData>(process.env.NEXT_PUBLIC_ANALYSIS_CF_URL, {
+    environment: tab,
+    feature,
+  });
 };
 
 const Modelling = () => {

diff --git a/infrastructure/README.md b/infrastructure/README.md
@@ -120,8 +120,7 @@ Deployment to the CloudRun instances is accomplished by building Docker images a
   - the following secrets set by terraform in STAGING_CLIENT_ENV_TF_MANAGED (in the format of an .env file):
     - NEXT_PUBLIC_URL
     - NEXT_PUBLIC_API_URL
-    - NEXT_PUBLIC_ANALYSIS_CF_MARINE_URL
-    - NEXT_PUBLIC_ANALYSIS_CF_TERRESTRIAL_URL
+    - NEXT_PUBLIC_ANALYSIS_CF_URL
     - NEXT_PUBLIC_ENVIRONMENT
     - LOG_LEVEL
   - additional secrets set manually in STAGING_CLIENT_ENV (copy to be managed in LastPass)