fix: group a component with its dashboard, and drop the checksum pins #64

Merged
ivuorinen merged 1 commit from ivuorinen/fix/group-component-with-its-dashboard into main 2026-09-27 09:58:20 +00:00 AGit
Owner

The gatus PR bumped the dashboard to 5.37.0 and left the deployment on
5.36.0, failing tests/version-sync.bats. The two halves are named
differently by the managers that find them — TwiN/gatus from the dashboard
URL, ghcr.io/twin/gatus from the image — and matchDepNames listed only the
first, so the group held the dashboard alone.

Listing both spellings, as adguard-exporter already did, does not fix it:
groupName rendered the raw depName, so each spelling produced its own group
and its own branch. Both halves are now matched on their last path segment
and groupName strips the prefix, so either spelling yields one group.
redis_exporter only ever worked because its GitHub path and its image path
are the same string.

The sha256 beside each pin is gone. It was a second record of a fact the
committed ConfigMap already carries, Renovate could not recompute it, and
holding the two halves in step cost a --refresh flag, a self-rewriting pass
and two defects. Regeneration is still required on every bump, so
postUpgradeTasks stays — now a bare command with no arguments.

Removing it changes no dashboard: the only difference in all 22 regenerated
ConfigMaps is the dropped "# sha256:" comment.

The gatus PR bumped the dashboard to 5.37.0 and left the deployment on 5.36.0, failing tests/version-sync.bats. The two halves are named differently by the managers that find them — TwiN/gatus from the dashboard URL, ghcr.io/twin/gatus from the image — and matchDepNames listed only the first, so the group held the dashboard alone. Listing both spellings, as adguard-exporter already did, does not fix it: groupName rendered the raw depName, so each spelling produced its own group and its own branch. Both halves are now matched on their last path segment and groupName strips the prefix, so either spelling yields one group. redis_exporter only ever worked because its GitHub path and its image path are the same string. The sha256 beside each pin is gone. It was a second record of a fact the committed ConfigMap already carries, Renovate could not recompute it, and holding the two halves in step cost a --refresh flag, a self-rewriting pass and two defects. Regeneration is still required on every bump, so postUpgradeTasks stays — now a bare command with no arguments. Removing it changes no dashboard: the only difference in all 22 regenerated ConfigMaps is the dropped "# sha256:" comment.
fix: group a component with its dashboard, and drop the checksum pins
All checks were successful
validate / render (pull_request) Successful in 1m36s
validate / hooks (pull_request) Successful in 2m36s
825e3f54ef
The gatus PR bumped the dashboard to 5.37.0 and left the deployment on
5.36.0, failing tests/version-sync.bats. The two halves are named
differently by the managers that find them — TwiN/gatus from the dashboard
URL, ghcr.io/twin/gatus from the image — and matchDepNames listed only the
first, so the group held the dashboard alone.

Listing both spellings, as adguard-exporter already did, does not fix it:
groupName rendered the raw depName, so each spelling produced its own group
and its own branch. Both halves are now matched on their last path segment
and groupName strips the prefix, so either spelling yields one group.
redis_exporter only ever worked because its GitHub path and its image path
are the same string.

The sha256 beside each pin is gone. It was a second record of a fact the
committed ConfigMap already carries, Renovate could not recompute it, and
holding the two halves in step cost a --refresh flag, a self-rewriting pass
and two defects. Regeneration is still required on every bump, so
postUpgradeTasks stays — now a bare command with no arguments.

Removing it changes no dashboard: the only difference in all 22 regenerated
ConfigMaps is the dropped "# sha256:" comment.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ivuorinen/turingpi-cluster!64
No description provided.