TSJR-181 - fetch config files from s3 at build time

.circleci/config.yml

@@ -25,11 +25,20 @@ save_cache_settings: &save_cache_settings
   paths:
     - node_modules
 
+build_configuration_fetch: &build_configuration_fetch
+    name: "configuring environment"
+    command: |
+        ./awsconfiguration.sh $DEPLOY_ENV
+        ./buildenv.sh -e $DEPLOY_ENV -b ${LOGICAL_ENV}-${APPNAME}-buildvar
+        aws s3 cp s3://tc-platform-${LOGICAL_ENV}/securitymanager/micro-frontends-config-${LOGICAL_ENV}.json ./config/micro-frontends-config-${LOGICAL_ENV}.json
+        aws s3 cp s3://tc-platform-${LOGICAL_ENV}/securitymanager/micro-frontends-routes-${LOGICAL_ENV}.txt ./config/micro-frontends-routes-${LOGICAL_ENV}.txt
+
 builddeploy_steps: &builddeploy_steps
   - checkout
   - setup_remote_docker
   - run: *install_dependency
   - run: *install_deploysuite
+  - run: *build_configuration_fetch
   - restore_cache: *restore_cache_settings_for_build
   - run: 
       command: |

config/docs/adr-02.md

@@ -0,0 +1,6 @@
+# ADR-02 2023-10-25
+
+We're going to do a mix of s3 and locally hosted configuration files.
+We're going to host the configuration files locally on the repository for versioning purposes,
+But at the build time we're going to fetch the specific configuration files based on the build env and overwrite the local version with what we have in s3.
+This will allow us to enable/disable MFE apps by updating the s3 files and triggering a new build via the CircleCI.