refactor(templates): rename template files to match rendered resource kinds
changelog / changelog (push) Successful in 19s
check-and-test / check-and-test (push) Successful in 2m59s

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>
This commit is contained in:
2026-09-03 14:20:12 +02:00
co-authored by Copilot
parent bebe2a6009
commit 4884dc0fe0
50 changed files with 96 additions and 95 deletions
+5 -5
View File
@@ -4,10 +4,10 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: fails with multiple replicas and "GIT_GC_REPOS" enabled
template: templates/gitea/deployment.yaml
template: templates/gitea/secret_config.yaml
set:
replicaCount: 2
persistence:
@@ -22,14 +22,14 @@ tests:
- failedTemplate:
errorMessage: "Invoking the garbage collector via CRON is not yet supported when running with multiple replicas. Please set 'gitea.config.cron.GIT_GC_REPOS.enabled = false'."
- it: fails with multiple replicas and RWX file system not set
template: templates/gitea/deployment.yaml
template: templates/gitea/secret_config.yaml
set:
replicaCount: 2
asserts:
- failedTemplate:
errorMessage: "When using multiple replicas, a RWX file system is required and persistence.accessModes[0] must be set to ReadWriteMany."
- it: fails with multiple replicas and bleve issue indexer
template: templates/gitea/deployment.yaml
template: templates/gitea/secret_config.yaml
set:
replicaCount: 2
persistence:
@@ -43,7 +43,7 @@ tests:
- failedTemplate:
errorMessage: "When using multiple replicas, the issue indexer (gitea.config.indexer.ISSUE_INDEXER_TYPE) must be set to a HA-ready provider such as 'meilisearch', 'elasticsearch' or 'db' (if the DB is HA-ready)."
- it: fails with multiple replicas and bleve repo indexer
template: templates/gitea/deployment.yaml
template: templates/gitea/secret_config.yaml
set:
replicaCount: 2
persistence:
+1 -1
View File
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: renders a deployment
template: templates/gitea/deployment.yaml
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: Renders a deployment
template: templates/gitea/deployment.yaml
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: uses direct execution when extraEnvSourceFile is not set
template: templates/gitea/deployment.yaml
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: Render the deployment (default)
asserts:
@@ -7,7 +7,7 @@ chart:
appVersion: 1.19.3
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: default values
template: templates/gitea/deployment.yaml
+1 -1
View File
@@ -3,7 +3,7 @@ release:
name: gitea-unittests
namespace: testing
templates:
- templates/gitea/config.yaml
- templates/gitea/secret_inlineConfig.yaml
tests:
- it: inline config stringData.server using TPL
set:
+1 -1
View File
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: renders openshift-compatible defaults for chart-managed containers
template: templates/gitea/deployment.yaml
+1 -1
View File
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: renders default liveness probe
template: templates/gitea/deployment.yaml
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: supports adding a sidecar container
template: templates/gitea/deployment.yaml
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: skips gpg init container
template: templates/gitea/deployment.yaml
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: adds gpg init container
template: templates/gitea/deployment.yaml
@@ -4,7 +4,7 @@ release:
namespace: testing
templates:
- templates/gitea/deployment.yaml
- templates/gitea/config.yaml
- templates/gitea/secret_config.yaml
tests:
- it: supports defining SSH log level for root based image
template: templates/gitea/deployment.yaml
@@ -7,11 +7,11 @@ release:
namespace: testing
templates:
- templates/gitea/pvc.yaml
- templates/gitea/persistentVolumeClaim.yaml
tests:
- it: should set storageClassName when persistence.storageClass is defined
template: templates/gitea/pvc.yaml
template: templates/gitea/persistentVolumeClaim.yaml
set:
persistence.storageClass: "my-storage-class"
asserts:
@@ -20,7 +20,7 @@ tests:
value: "my-storage-class"
- it: should set global.storageClass when persistence.storageClass is not defined
template: templates/gitea/pvc.yaml
template: templates/gitea/persistentVolumeClaim.yaml
set:
global.storageClass: "default-storage-class"
asserts:
@@ -29,7 +29,7 @@ tests:
value: "default-storage-class"
- it: should set storageClassName when persistence.storageClass is defined and global.storageClass is defined
template: templates/gitea/pvc.yaml
template: templates/gitea/persistentVolumeClaim.yaml
set:
global.storageClass: "default-storage-class"
persistence.storageClass: "my-storage-class"
@@ -3,11 +3,11 @@ release:
name: gitea-unittests
namespace: testing
templates:
- templates/gitea/sshService.yaml
- templates/gitea/httpService.yaml
- templates/gitea/service_ssh.yaml
- templates/gitea/service_http.yaml
tests:
- it: supports adding custom labels to sshService
template: templates/gitea/sshService.yaml
template: templates/gitea/service_ssh.yaml
set:
service:
ssh:
@@ -19,7 +19,7 @@ tests:
value: "testvalue"
- it: keeps existing labels (ssh)
template: templates/gitea/sshService.yaml
template: templates/gitea/service_ssh.yaml
set:
service:
ssh:
@@ -29,7 +29,7 @@ tests:
path: metadata.labels["app"]
- it: supports adding custom labels to httpService
template: templates/gitea/httpService.yaml
template: templates/gitea/service_http.yaml
set:
service:
http:
@@ -41,7 +41,7 @@ tests:
value: "testvalue"
- it: keeps existing labels (http)
template: templates/gitea/httpService.yaml
template: templates/gitea/service_http.yaml
set:
service:
http:
@@ -51,7 +51,7 @@ tests:
path: metadata.labels["app"]
- it: render service.ssh.loadBalancerClass if set and type is LoadBalancer
template: templates/gitea/sshService.yaml
template: templates/gitea/service_ssh.yaml
set:
service:
ssh:
@@ -73,7 +73,7 @@ tests:
value: ["1.2.3.4/32", "5.6.7.8/32"]
- it: does not render when loadbalancer properties are set but type is not loadBalancerClass
template: templates/gitea/httpService.yaml
template: templates/gitea/service_http.yaml
set:
service:
http:
@@ -92,7 +92,7 @@ tests:
path: spec.loadBalancerSourceRanges
- it: does not render loadBalancerClass by default even when type is LoadBalancer
template: templates/gitea/httpService.yaml
template: templates/gitea/service_http.yaml
set:
service:
http:
@@ -107,8 +107,8 @@ tests:
- it: both ssh and http services exist
templates:
- templates/gitea/sshService.yaml
- templates/gitea/httpService.yaml
- templates/gitea/service_ssh.yaml
- templates/gitea/service_http.yaml
asserts:
- matchRegex:
path: metadata.name