4 Commits

Include renames

Author	SHA1	Message	Date
volker.raschekandCopilot	4884dc0fe0	refactor(templates): rename template files to match rendered resource kinds ... The files in templates/gitea/ used a mix of naming styles: lowercase concatenations (poddisruptionbudget.yaml, serviceaccount.yaml, servicemonitor.yaml, pvc.yaml), camelCase (httpService.yaml, sshService.yaml) and kind-suffixed names (gpg-secret.yaml, metrics-secret.yaml). It was therefore not obvious from a file name which Kubernetes resource it renders, and the naming contradicted the camelCase convention the Gateway API templates already follow. Files are now named after the kind they render, with a lowercase suffix distinguishing several resources of the same kind: config.yaml -> secret_config.yaml + secret_inlineConfig.yaml gpg-secret.yaml -> secret_gpg.yaml init.yaml -> secret_init.yaml metrics-secret.yaml -> secret_metrics.yaml httpService.yaml -> service_http.yaml sshService.yaml -> service_ssh.yaml poddisruptionbudget.yaml -> podDisruptionBudget.yaml pvc.yaml -> persistentVolumeClaim.yaml serviceaccount.yaml -> serviceAccount.yaml servicemonitor.yaml -> serviceMonitor.yaml config.yaml rendered two Secrets from a single file, which forced every unit test to address them via documentIndex. It is split so that each file renders exactly one resource. The rendered manifests are unchanged; only file names and the references to them were touched. This includes the checksum/config annotation in deployment.yaml and all helm unit test suites. The HA guard assertions had to move from deployment.yaml to secret_config.yaml: Helm sorts templates in reverse alphabetical order, so secret_config.yaml is now rendered before deployment.yaml and the fail() is reported for that file directly instead of bubbling up through the include chain of the Deployment. Users relying on the template paths (e.g. `helm template --show-only` or post-renderers) have to adjust to the new file names. Co-authored-by: Copilot <copilot@github.com>	2026-09-03 14:20:12 +02:00
developerguy	a7035ca4e5	feat: make it configurable of the initContainers volume mount path for scripts (#848) ... ### Description of the change Makes it configurable volume mount path for initContainers for init scripts ### Benefits Configurable initContainers volumeMount path for init scripts ### Possible drawbacks I don't think that there will be any drawbacks ### Applicable issues - Fixes #847 Signed-off-by: Batuhan Apaydin <batuhan.apaydin@chainguard.dev> Reviewed-on: https://gitea.com/gitea/helm-gitea/pulls/848 Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.com> Co-authored-by: developerguy <developerguy@noreply.gitea.com> Co-committed-by: developerguy <developerguy@noreply.gitea.com>	2025-04-03 18:03:13 +00:00
justusbunsi	a79fd31f7e	Increase testability of shell scripts (#752) ... This is a preparation for #724 (bash script testing) which would be too complex to review if done there. Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/752 Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com> Co-committed-by: justusbunsi <sk.bunsenbrenner@gmail.com>	2024-12-19 12:04:00 +00:00
justusbunsi	4691b63f7a	Move Helm unittests into subfolder (#750) ... Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/750 Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com> Co-committed-by: justusbunsi <sk.bunsenbrenner@gmail.com>	2024-12-18 12:04:15 +00:00