Adding configurable env names

adobecom · Jul 23, 2024 · 9d9944f · 9d9944f
1 parent bf4c12a
commit 9d9944f
Showing 1 changed file with 9 additions and 3 deletions.
diff --git a/libs/navigation/footer.js b/libs/navigation/footer.js
@@ -4,13 +4,19 @@ const blockConfig = {
   appendType: 'appendChild',
 };
 
+const envMap = {
+  prod: 'https://www.adobe.com',
+  stage: 'https://www.stage.adobe.com/',
+  qa: 'https://feds--milo--adobecom.hlx.page'
+}
+
 export default async function loadBlock(configs = {}) {
-  let miloLibs = configs.miloLibs || 'https://www.adobe.com';
-  const branch = new URLSearchParams(window.location.search).get('branch');
+  const { locale, contentRoot, env = 'prod' } = configs;
+  let miloLibs = envMap[env];
+  const branch = new URLSearchParams(window.location.search).get('navbranch');
   if (branch) {
     miloLibs = `https://${branch}--milo--adobecom.hlx.page`;
   }
-  const { locale, contentRoot } = configs;
 
   // Relative path can't be used, as the script will run on consumer's app
   const { default: bootstrapBlock } = await import(`${miloLibs}/libs/navigation/bootstrapper.js`);