Feature: Add test for enabling redis to ci
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Description of the change
I'd like to add an isolated redis test to our CI to ensure this chart works properly with redis. It would go somewhere in here:
https://github.com/nextcloud/helm/blob/bf6cc4a9df0b3bffd3915dc940ddbec71976429e/.github/workflows/lint-test.yaml#L69-L83
Benefits
Ensure this chart works properly with redis, and will also make sure we catch breaking changes in the bitnami chart, if they happen.
Possible drawbacks
Another test to maintain. 😅
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/lint-test.yaml around lines 69-83 and review the existing chart tests and CI steps there. Add an isolated Redis test to the CI workflow; done means the workflow verifies that the chart works properly with Redis and catches breaking changes in the Bitnami chart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, redis
- Domain
- ci-cd, databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100