3 Commits

Include renames

Author	SHA1	Message	Date
volker.raschekandCopilot	bb3b59f1ee	test: normalize the titles of the helm unit tests ... The contributor guidelines require that the title of a unit test is "a short sentence starting with a capital letter and ending without a period". Only 30 of the 269 titles followed that rule. The remaining ones were lowercase verb phrases ("renders a deployment"), which made the test output read inconsistently depending on which suite was running, and made it impossible to tell a convention violation from an intentional style. All titles are now imperative, capitalized and unquoted-safe: renders a deployment -> Render a Deployment should not render when gatewayAPI.enabled is false -> Skip rendering when gatewayAPI.enabled is false skips gpg volume spec -> Skip the gpg volume spec The bracketed prefixes of the dependency checks and of the server section suite are kept, because they group the tests by the chart they assert on. Only the sentence behind the prefix was rewritten. Beyond the pure capitalization three classes of titles needed real rewording: - The titles in image-configuration.yaml named a subject instead of a scenario ("default values", "tag override", "digest and global registry"). They now describe what is rendered. - init_directory_structure.sh-rootless.yaml carried "it does not chown /data ...", which rendered as "it it does not chown" in the test output. - The "should" prefix in the Gateway API and route suites added no information once the title is a sentence. The title of the GIT_GC_REPOS test lost its embedded double quotes. The title was previously an unquoted YAML scalar, so the quotes were literal characters; quoting the title turned them into a parse error. The value is unambiguous without them. Three byte-identical tests asserting pgpool.adminPassword existed in customization-integrity-postgresql-ha.yaml - same template, same assertion, same expected value. They were a copy-paste artifact and shared one title, so two of them are removed. No coverage is lost, which is why the test count drops from 269 to 267. No snapshot files are tracked and no suite uses matchSnapshot, so retitling cannot invalidate stored snapshots. Co-authored-by: Copilot <copilot@github.com>	2026-10-03 21:17:18 +02:00
volker.raschekandCopilot	552fe8c56e	refactor(templates): move the templates out of the gitea subdirectory ... The `templates/gitea` subdirectory did not group anything meaningful, since every template of this chart belongs to Gitea. It only duplicated the chart name in every path and forced the unit tests to spell out `templates/gitea/<name>.yaml`, while `_helpers.tpl` and `NOTES.txt` already lived directly in `templates`. All templates now live in `templates`, which matches the layout of the bundled sub-charts and the Helm defaults. The checksum helper in `templates/_secrets.tpl` built its include path from `$root.Template.BasePath` and therefore carried the subdirectory in a `printf` format string instead of a literal path. Without adjusting it the chart failed to render with "no template gitea/templates/gitea/secret_config.yaml associated with template gotpl". Co-authored-by: Copilot <copilot@github.com>	2026-09-14 20:28:17 +02:00
Todd Marimon	7747a001f7	feat: add Gateway API support (#1073) ... Add full Gateway API support for exposing Gitea via HTTPRoute, TCPRoute, BackendTLSPolicy, and ClientSettingsPolicy resources. New templates: - `httpRoute.yaml` — renders an HTTPRoute with configurable parentRefs, hostnames, and rules (defaults to PathPrefix `/`) - `tcpRoute.yaml` — renders a TCPRoute for SSH traffic - `backendTLSPolicy.yaml` — renders a BackendTLSPolicy for encrypted backend connections with required validation config - `clientSettingsPolicy.yaml` — renders an NGINX Gateway Fabric ClientSettingsPolicy to raise the request body size limit Infrastructure: - `gatewayAPI.enabled` global toggle gates all resources - Resources grouped under `gatewayAPI.core.*` and `gatewayAPI.nginx.*` - Helper templates extracted into dedicated `_*.tpl` files - Service name helpers (`gitea.service.http.name`, `gitea.service.ssh.name`) extracted into `_services.tpl`; service templates renamed to camelCase - `ROOT_URL`, `DOMAIN`, and `SSH_DOMAIN` auto-resolve from `httpRoute.hostnames[0]`; `httpRoute.tls` switches to `https` Documentation: - New `docs/gateway-api.md` with topology examples, BackendTLSPolicy setup, sectionName guidance, SSH considerations, and NGINX body size limit configuration - `.github/copilot-instructions.md` with project conventions - README parameter table auto-generated via `make readme` Tests: - Helm unit tests for all four new resource templates - Config tests for hostname/TLS resolution from Gateway API values Co-authored-by: Todd Marimon <toddmarimon@gmail.com>	2026-07-19 16:25:28 +00:00