coop-cloud/monitoring-ng
1
0
Fork 2
Code Issues 4 Pull Requests 8 Packages Projects Releases Wiki Activity

Secret names too long #12

New Issue
Open
opened 2026-03-11 16:26:49 +00:00 by dannygroenewegen · 1 comment
dannygroenewegen commented 2026-03-11 16:26:49 +00:00
Copy Link

While deploying monitoring-ng, I encountered a secret name that was too long (>64 characters). According to R015, secret names should not be longer than 12 characters, but e.g. grafana_oidc_client_secret is longer.

I've tried using the domain m.gathering.org instead of monitoring.gathering.org. This shortens the secret name enough for deployment, but some dashboards hard-code the monitoring part of the domain name.

Can we shorten the longest secret names?

While deploying monitoring-ng, I encountered a secret name that was too long (>64 characters). According to [R015](https://docs.coopcloud.tech/maintainers/handbook/#r015-long-secret-names), secret names should not be longer than 12 characters, but e.g. grafana_oidc_client_secret is longer. I've tried using the domain m.gathering.org instead of monitoring.gathering.org. This shortens the secret name enough for deployment, but some [dashboards](https://git.coopcloud.tech/coop-cloud/monitoring-ng/src/commit/83461e2e76b3c860b9e50c268d3a253bf655e499/grafana-stacks-dashboard.json#L113) hard-code the monitoring part of the domain name. Can we shorten the longest secret names?
dannygroenewegen commented 2026-03-11 19:33:45 +00:00
Author
Copy Link

Tried leaving out the long secret with -C, but also some of the config names end up being too long: ${STACK_NAME}g_traefik_dashboard_json${GRAFANA_TRAEFIK_DASHBOARD_JSON_VERSION}

Would it manually setting STACK_NAME to something shorter be an option, or is that too much integrated everywhere?

Tried leaving out the long secret with -C, but also some of the config names end up being too long: ${STACK_NAME}_g_traefik_dashboard_json_${GRAFANA_TRAEFIK_DASHBOARD_JSON_VERSION} Would it manually setting STACK_NAME to something shorter be an option, or is that too much integrated everywhere?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud cyrnel decentral1se devydave fauno flancian Frando iexos jade javielico jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie marlon mayel mirsal moritz nicksellen notplants p4u1 pau pharaohgraphy renovate-bot ripclap rix rscmbbng sef simon sixsmith stevensting tobias trav val vaznasty virtualboys wolcen wykwit xynosis yksflip
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/monitoring-ng#12
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?