Feature: Add test for adding extra configs in 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
We should add a test for setting extra Nextcloud values via nextcloud.configs. We should set something via an inline php file using the helm parameter, and then verify it got set with occ config:system:get on the pod after the ct install is done.
Benefits
It's really common for users to need to add extra configuration config.php files, so this would ensure it's working.
Possible drawbacks
none that I can think of, but always open to feedback :)
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
Locate the existing CI tests and chart-install entry point used with ct install; start by reviewing how current Helm values are passed into test installations. Add coverage for an inline PHP file supplied through nextcloud.configs, then verify on the pod with occ config:system:get that the extra value was set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, php
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100