Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/sgibson91/helm-upgrade-decision-logic
Testing logic to decide which clusters/hubs to perform helm upgrade for based on changed filepaths
https://github.com/sgibson91/helm-upgrade-decision-logic
Last synced: about 1 month ago
JSON representation
Testing logic to decide which clusters/hubs to perform helm upgrade for based on changed filepaths
- Host: GitHub
- URL: https://github.com/sgibson91/helm-upgrade-decision-logic
- Owner: sgibson91
- License: mit
- Created: 2022-03-07T10:44:49.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2022-04-01T12:34:32.000Z (over 2 years ago)
- Last Synced: 2024-10-12T15:08:31.522Z (3 months ago)
- Language: Python
- Size: 232 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Testing decision logic for helm upgrade
This repository is a sandbox for testing the logic required for deciding which hubs on which clusters should have a helm upgrade based on changed filepaths.
**What it contains:**
- `mymodule/helm_upgrade_decision_logic.py`: A Python package (script) that analyses a list of filenames and decides which clusters/hubs need a helm upgrade, for their hub helm chart and the support helm chart. It adds a list of dictionaries to the GitHub Actions environment that can be used to configure matrix jobs in a later job. There is also a `--pretty-print` option that prints a human-readable table of jobs that will be run using the `rich` package.
- `.github/workflows/helm-upgrade-decision-logic.yaml`: A GitHub Action workflow that uses [`jitterbit/get-changed-files`](https://github.com/jitterbit/get-changed-files) to establish which files have been changed and pass this list to the Python script.There is a `config/clusters` folder and `helm-charts` folder as we would see in the `2i2c-org/infrastructure repo`.
The `tests/` folder contains testing infrastructure for this logic and this is triggered by the `test-deployer.yaml` workflow file.
Please make as many Pull Requests as you like to test the workflow!