Skip to content

git actions should look for cfg file #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Phil-NHS merged 1 commit into from
Dec 8, 2025
Merged

git actions should look for cfg file #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/staging-cicd.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
10 changes: 6 additions & 4 deletions databricks.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand All @@ -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
Expand Down