perfectra1nandperfectra1n
4631d42156
The inline-config Secret used `stringData`. The API server stores it as `data`, so a section removed from `gitea.config` was never pruned from the live Secret, and the init container kept writing it into `app.ini` on every start. With Gitea 28, a leftover `[webhook] ALLOWED_HOST_LIST` overrides `[security]`'s, which breaks webhooks to private hosts. This renders the Secret as base64 `data` instead. - `templates/secret_inlineConfig.yaml`: `stringData` → `data` (`b64enc`). - Unit tests read `data.*` with `decodeBase64: true`; adds a regression test asserting there is no `stringData`. Note: keys that are already stale from the `stringData` era survive the first upgrade to this version, because Helm's three-way merge never recorded them under `data`. Every removal after that is pruned. `make unittests-helm`: 261 passed. `helm lint` and `yamllint` are clean. Co-authored-by: perfectra1n <jonfuller2012@gmail.com> Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/1110 Co-authored-by: perfectra1n <49838+perfectra1n@noreply.gitea.com>
26 lines
671 B
YAML
26 lines
671 B
YAML
suite: config template | actions config
|
|
release:
|
|
name: gitea-unittests
|
|
namespace: testing
|
|
templates:
|
|
- templates/secret_inlineConfig.yaml
|
|
tests:
|
|
- it: "actions are enabled by default (based on vanilla Gitea behavior)"
|
|
template: templates/secret_inlineConfig.yaml
|
|
asserts:
|
|
- documentIndex: 0
|
|
notExists:
|
|
path: data.actions
|
|
|
|
- it: "actions can be disabled via inline config"
|
|
template: templates/secret_inlineConfig.yaml
|
|
set:
|
|
gitea.config.actions.ENABLED: false
|
|
asserts:
|
|
- documentIndex: 0
|
|
equal:
|
|
path: data.actions
|
|
decodeBase64: true
|
|
value: |-
|
|
ENABLED=false
|