infra/kforge
2
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases 1 Wiki Activity

update validation
Publish Action Image / build (push) Successful in 33s
Details
Publish Action Image / publish (push) Successful in 28s
Details

Browse Source
This commit is contained in:
Nate
2026-06-29 16:58:52 +10:00
parent 1881ea2e99
commit 565a91e235
2 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cmd/validate.go
+2 -3
View File
@@ -141,9 +141,8 @@ type requiredSecret struct {
// kforge.yml requires, based on what's enabled. // kforge.yml requires, based on what's enabled.
func buildRequiredSecrets(cfg *config.KforgeConfig) []requiredSecret { func buildRequiredSecrets(cfg *config.KforgeConfig) []requiredSecret {
secrets := []requiredSecret{ secrets := []requiredSecret{
// Always required — org level // kforge only needs these — DOCKER_USERNAME/PASSWORD are used by
{Name: "DOCKER_USERNAME", Location: "Gitea org secret", Required: true}, // docker/login-action and docker/build-push-action, not by kforge itself.
{Name: "DOCKER_PASSWORD", Location: "Gitea org secret", Required: true},
{Name: "KFORGE_NODE_IP", Location: "Gitea org secret", Description: "Node IP written as the external-dns annotation target"}, {Name: "KFORGE_NODE_IP", Location: "Gitea org secret", Description: "Node IP written as the external-dns annotation target"},
// Always required — repo level // Always required — repo level
readme.md
+7 -5
View File
@@ -637,11 +637,13 @@ kforge works with three categories of secrets, each living in the right place fo
Set once at the organisation level; available to every repo automatically. Set once at the organisation level; available to every repo automatically.
| Secret | Purpose | | Secret | Used by | Purpose |
|---|---| |---|---|---|
| `DOCKER_USERNAME` | Registry authentication | | `DOCKER_USERNAME` | `docker/login-action` | Registry authentication for image push |
| `DOCKER_PASSWORD` | Registry authentication | | `DOCKER_PASSWORD` | `docker/login-action` | Registry authentication for image push |
| `KFORGE_NODE_IP` | Cluster node IP — written as the external-dns target annotation | | `KFORGE_NODE_IP` | kforge | Cluster node IP — written as the external-dns target annotation |
`DOCKER_USERNAME` and `DOCKER_PASSWORD` are consumed by the Docker build steps in the generated workflow, not by kforge itself. `kforge validate` does not check for them.
### Category B — Gitea repo secrets ### Category B — Gitea repo secrets