### Description of the change This PR adds support for gpg key setup. It allows to pass the gpg private key content inline inside `values.yaml` or refer to an existing secret containing the key content data. ### Benefits Administrators don't need to manually setup the gpg environment from inside a running container. It also eliminates the breaking change of Gitea 1.17 regarding `[git].HOME` as the `GNUPGHOME` environment variable is used consistently to relocate the `.gnupg` directory to its former location. ### Applicable issues - fixes #107 ### Additional information This PR add the first unit tests to this Helm Chart, ensuring templating integrity for signing related configuration. ### Checklist - [x] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm) Co-authored-by: justusbunsi <[email protected]> Co-authored-by: pat-s <[email protected]> Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/343 Reviewed-by: luhahn <[email protected]> Reviewed-by: techknowlogick <[email protected]> Co-authored-by: justusbunsi <[email protected]> Co-committed-by: justusbunsi <[email protected]>
13 lines
244 B
Makefile
13 lines
244 B
Makefile
.PHONY: prepare-environment
|
|
prepare-environment:
|
|
npm install
|
|
|
|
.PHONY: readme
|
|
readme: prepare-environment
|
|
npm run readme:parameters
|
|
npm run readme:lint
|
|
|
|
.PHONY: unittests
|
|
unittests:
|
|
helm unittest --helm3 --strict -f 'unittests/**/*.yaml' ./
|