Add more checking, change params.

Author: jadudm

dev-local/README.md

@@ -35,7 +35,13 @@ favorites:
     access_type: cli
 ```
 
-If you already have some aliases, you can just add this one to the list. The account number and cloud access role can be obtained from the Cloudtamer dashboard. The alias **must** be named `BB2-NON-PROD` for these tools to work.
+If you already have some aliases, you can just add this one to the list. The account number and cloud access role can be obtained from the Cloudtamer dashboard. This is not strictly necessary, as the tooling cannot automate a `kion` call *and* then continue, as `kion` opens a new shell. However, it is much easier (and, for this documentation, the preferred method) to invoke
+
+```
+kion f BB2-NON-PROD
+```
+
+than to navigate a menu structure. You may ultimately choose a shorter alias, e.g. `kion f bnp`.
 
 ## to start
 
@@ -61,23 +67,43 @@ The first step is to build the local containers. From the root of the tree, or f
 make build-local
 ```
 
-This should build the image `bb-local:latest`.
+This should build the container image for `bb-local:latest`, the Selenium image, and the MSLS image.
 
-Building the image is only necessary when the `requirements/requirements.txt` or `requirements/requirements.dev.txt` files change. Those requirements get baked into the image; changes to application code should be picked up via dynamic reload during normal development.
+Building the images is only necessary when the `requirements/requirements.txt` or `requirements/requirements.dev.txt` files change. Those requirements get baked into the image; changes to application code should be picked up via dynamic reload during normal development.
 
 ## running the local image
 
 Next, run the stack.
 
-### running locally / mocking MSLS
+### running the stack
 
-To run the stack locally,
+There are four possible ways to run the stack.
 
 ```
-make run-local ENV=local
+make run-local bfd=<bfd-option> auth=<auth-option>
 ```
 
-This will launch the stack with no connection to live environments, and it will use the mocked MSLS tooling.
+For example, to run against `test` with a live SLSX exchange:
+
+```
+make run-local bfd=test auth=live
+```
+
+Each combination has different implications. Only some make sense at this time (Nov '25):
+
+| bfd / auth | mock | live |
+| --- | --- | --- |
+| local | local unit tests | testing SLSX sequences |
+| test | ⛔ | Full-up against `test` | 
+| sbx | ⛔ | Full-up against `sbx` | 
+
+* `local/mock`: This makes sense for running unit tests; only local tests will run in this configuration.
+* `local/live`: Manual testing of SLSX sequences should be able to be performed with this combination (TBD)
+* `test/mock`: Not a valid condition; a mock authentication will not work with a live server.
+* `test/live`: Live SLSX exchanges with medicare.gov and calls against the `test` BFD environment.
+* `sbx/mock`: Not a valid condition.
+* `sbx/live`: Live SLSX exchanges and calls against the `sbx` BFD environment.
+
 
 ### running against `test`
 

dev-local/check-pre-post.bash

@@ -14,34 +14,29 @@ services:
   # A small Flask app for testing.
   msls:
     image: msls-local:latest
-    command: python app.py
+    platform: linux/amd64
+    command: /code/start-local.sh
     ports:
       - "8080:8080"
     volumes:
       - ../msls-local:/code
-    profiles:
-      - mocksls
-      - slsx
   ####################
   # Blue Button
   web:
     image: bb-local:latest
-    command: /start-local.sh
+    platform: linux/amd64
+    command: /code/dev-local/start-local.sh
     env_file:
       - .env.container
     volumes:
       - ..:/code
       - ~/.bb2/certstore:/certstore
-      - ./start-local.sh:/start-local.sh
     ports:
       - "8000:8000"
       - "5678:5678"
     depends_on:
       - db
       - msls
-    profiles:
-      - slsx
-    platform: linux/amd64
 
   # web_msls:
   #   build: .

dev-local/docker-compose-local.yaml

@@ -1,35 +1,34 @@
 #!/usr/bin/env bash
-source ./check-pre-post.bash
-source ./retrieve-certs-and-salt.bash
+source ./utility-functions.bash
 
 # this says to "export all variables."
 set -a
 # exit on error.
 set -e
 
+# bfd = local | test | sbx
+# auth = mock | live
 
-######################################################################
 # let's make sure we have a valid ENV var before proceeding
 check_valid_env
 
-######################################################################
 # source the baseline environment variables
 # these set the stage for all further environment manipulation for 
 # launching the app.
+clear_canary_variables
 source ./.env.local
 
 # add another check or two after we source the env file.
 check_env_after_source
 
-######################################################################
 # let's make sure the .env.local sourced in correctly.
 check_env_preconditions
 
 # set the FHIR_URL and FHIR_URL_V3
-set_fhir_urls
+set_bfd_urls
 
 # set the profile for docker compose
-set_profile
+set_auth_profile
 
 # retrieve the certs and store them in $HOME/.bb2/certstore
 retrieve_certs
@@ -38,33 +37,20 @@ set_salt
 
 echo "🚀 Launching the stack for '${ENV}'."
 
-echo "FHIR_URLs are:"
-echo "  * ${FHIR_URL}"
-echo "  * ${FHIR_URL_V3}"
-
-DOCKER_PS=$(docker ps -q)
-echo $DOCKER_PS
-
-TAKE_IT_DOWN="NO"
-for id in $DOCKER_PS; do
-    NAME=$(docker inspect --format '{{.Config.Image}}' $id)
-    if [[ "${NAME}" =~ "postgres" ]]; then
-        echo "🤔 I think things are still running. Bringing the stack down."
-        TAKE_IT_DOWN="YES"
-    fi
-done
-
-if [ "${TAKE_IT_DOWN}" = "YES" ]; then
-    for id in $DOCKER_PS; do
-        echo "🛑 Stopping container $id"
-        docker stop $id
-    done
+if [[ "${bfd}" == "local" ]]; then
+    echo "🥶 FHIR_URLs are not set when running locally."
+    echo "   BFD calls will fail."
+else
+    echo "FHIR_URLs are:"
+    echo "  * ${FHIR_URL}"
+    echo "  * ${FHIR_URL_V3}"
 fi
 
+cleanup_docker_stack
+
 echo "📊 Vernier start."
 echo
 
 docker compose \
-    --profile "${PROFILE}" \
     -f docker-compose-local.yaml \
     up

dev-local/run-appropriate-stack.bash

@@ -4,7 +4,7 @@ set -a
 
 if [ "${DB_MIGRATIONS}" = "true" ]
 then
-    echo "🆗 running migrations"
+    echo "🔵 running migrations"
     python manage.py migrate
 
     # We will recrate this with every launch.
@@ -13,21 +13,29 @@ then
     # Only create the root user if it doesn't exist.
     result=$(echo "from django.contrib.auth.models import User; print(1) if User.objects.filter(username='${SUPER_USER_NAME}').exists() else print(0)" | python manage.py shell)
     if [[ "$result" == "0" ]]; then
-        echo "🆗 creating ${} user."
         echo "from django.contrib.auth.models import User; User.objects.create_superuser('${SUPER_USER_NAME}', '${SUPER_USER_EMAIL}', '${SUPER_USER_PASSWORD}')" | python manage.py shell
+        echo "🆗 created ${SUPER_USER_NAME} user."
     else
         echo "🆗 ${SUPER_USER_NAME} already exists."
     fi
 
     python manage.py create_admin_groups
-    echo "🆗 loading scopes.json"
+    echo "🆗 create_admin_groups"
+    
     python manage.py loaddata scopes.json
+    echo "🆗 loaddata scopes.json"
 
     python manage.py create_blue_button_scopes
+    echo "🆗 create_blue_button_scopes"
+
     python manage.py create_test_user_and_application
+    echo "🆗 create_test_user_and_application"
+
     python manage.py create_user_identification_label_selection
-    echo "creating feature switches......"
+    echo "🆗 create_user_identification_label_selection"
+
     python manage.py create_test_feature_switches
+    echo "🆗 create_test_feature_switches"
 else
     echo "restarting blue button server, no db image migration and models initialization will run here, you might need to manually run DB image migrations."
 fi