Bridgeman-Accessible/services.bridgemanaccessible.ca-helm
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A Helm chart for deploying Bridgeman Accessible's Services Dashboard
32 commits 1 branch 0 tags 155 KiB
Find a file
Alan Bridgeman bfb8f8ef23
All checks were successful
Deploy the Helm Chart / build (push) Successful in 15s
Details
Replaced part of backup sidecar template with template function from subchart (specifically 
osql.envvars) which should mean variable naming mismatch shouldn't happen there anymore
2025-12-25 13:21:15 -06:00
.forgejo/workflows Major change that brought the chart in line with others. Mainly by more heavily relyng on subcharts and *.tpl files for code modularity and reusability (and consistency) 2025-12-24 19:07:22 -06:00
templates Replaced part of backup sidecar template with template function from subchart (specifically 2025-12-25 13:21:15 -06:00
.gitignore Major change that brought the chart in line with others. Mainly by more heavily relyng on subcharts and *.tpl files for code modularity and reusability (and consistency) 2025-12-24 19:07:22 -06:00
.helmignore Major change that brought the chart in line with others. Mainly by more heavily relyng on subcharts and *.tpl files for code modularity and reusability (and consistency) 2025-12-24 19:07:22 -06:00
Chart.lock Updated dependency to attempt to resolve issue 2025-12-24 21:11:53 -06:00
Chart.yaml [Forgejo Actions] Update Helm chart version to 2.0.5 2025-12-25 19:03:57 +00:00
LICENSE Initial commit 2025-05-12 08:22:27 -05:00
README.md Mostly just small vanity updates to the README to re-trigger the automation 2025-06-23 08:06:57 -05:00
values.yaml Updated alues.yaml so that it meets schema and helm lint passes 2025-12-24 21:17:56 -06:00

README.md

Services Dashboard (Subscription/Payment Management Backend) Helm Chart

A Helm chart for deploying Bridgeman Accessible's Services Dashboard

Automation (Forgejo Actions)

This repository is setup with CI/CD automation that allows for easy deployment when new code is pushed to the repository.

This workflow can be broken down into a few key actions:

  1. Build a new version of the Helm Chart
  2. If already deployed, backup old data
  3. Redeploy the Helm Chart (by deleting and then re-creating)
  4. Restore the data using the created backup, if applicable

New Version

If the Chart version matches a version already in the remote registry/repository the patch number will be automatically incremented.

Creating backup of current status

Note, there is an inherent assumption that the pod is currently up and running (stable)

Restoring data from backup

Can fail if redeployment doesn't go smoothly though tries to accommodate for common issues.