From 25f8ff59519056db2f93e85f789046eb73017d6b Mon Sep 17 00:00:00 2001
From: Phil-NHS <Philip.Tate@nhs.net>
Date: Mon, 8 Dec 2025 15:03:00 +0000
Subject: [PATCH] git actions should look for cfg file

---
 .github/workflows/staging-cicd.yml |  4 ++--
 databricks.yml                     | 10 ++++++----
 2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/.github/workflows/staging-cicd.yml b/.github/workflows/staging-cicd.yml
index ab26a26..54555dc 100644
--- a/.github/workflows/staging-cicd.yml
+++ b/.github/workflows/staging-cicd.yml
@@ -42,11 +42,11 @@ jobs:
 
       - name: Validate Staging Bundle
       # trigger target the staging deploy in databricks.yml
-        run: databricks bundle validate -t staging --profile ""  # forces use of env vars only
+        run: databricks bundle validate -t staging #--profile ""  # forces use of env vars only # didnt work
 
       - name: Deploy Staging Bundle
       # trigger target the staging deploy in databricks.yml
-        run: databricks bundle deploy -t staging --profile ""  # forces use of env vars only #??--auto-approve
+        run: databricks bundle deploy -t staging #--profile ""  # forces use of env vars only #??--auto-approve # didnt work
        # working-directory: .
 
   # testing:
diff --git a/databricks.yml b/databricks.yml
index b9a2ce5..03ccce6 100644
--- a/databricks.yml
+++ b/databricks.yml
@@ -101,7 +101,7 @@ targets:
     default: true
     # This is the the default deployment workspace
     workspace:
-      # profile means in gets set values from [dev] section of databrickscfg
+      # profile means in gets set values from [dev] section of databrickscfg useful on local machine, unneeded in databricks environment 
       profile: dev
       # specify hosts in the databricks.yml not config for clarity
       # dev databricks host
@@ -126,13 +126,14 @@ targets:
       # Devs can see each others stuff
       group_name: dev_env_users
 
-
+#delete this
 
   staging:
     # Staging should purely be for investigation and testing prior to going to prod it runs in production mode so will run and constant updates and should be through github actions and service principle on successful pull request 
     mode: production
     workspace:
-      profile: staging
+      # specify in the databricks validate and deploy in cicd github no profile otherwise will fail to find vars, use profile only for deploying from local machnine
+      # profile: staging #still failing can make the file on the fly but would prefer not to
       # staging databricks host
       host: https://adb-295718430158257.17.azuredatabricks.net
       root_path: /Workspace/.bundle/${bundle.name}/staging
@@ -154,7 +155,8 @@ targets:
     # Automatically deployed to via git actions and service principle minimal testing on deploy as previously run on staging
     mode: production
     workspace:
-      profile: prod
+      # specify in the databricks validate and deploy in cicd github no profile otherwise will fail to find vars, use profile only for deploying from local machnine
+      # profile: prod
       # prod databricks host
       host: https://adb-295718430158257.17.azuredatabricks.net
       root_path: /Workspace/.bundle/${bundle.name}/prod