fix: dashboard repo variable refresh on tier change #433
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-platform!433
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/dora-dashboard-nits"
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?
Summary
Change repo variable refresh from
2(on time range change) to1(on dashboard load) so the repo dropdown re-queries when the tier variable changes.Changes
terraform/dashboards/dora-dashboard.json: Changedrefresh: 2torefresh: 1on therepotemplate variableRationale
The repo variable query is
label_values(dora_pr_merges_total{tier=~"$tier"}, repo)-- it references$tier. Withrefresh: 2, it only re-executes on time range changes, not on tier variable changes. Withrefresh: 1(on dashboard load), Grafana cascades re-queries to dependent variables when the upstream variable changes, which is the standard pattern for chained variables.Test Plan
Related
🤖 Generated with Claude Code
PR #433 Review
DOMAIN REVIEW
Stack: Grafana dashboard JSON managed via Terraform.
The change is correct. The
repotemplate variable's query references$tiervialabel_values(dora_pr_merges_total{tier=~"$tier"}, repo), making it a dependent/chained variable. Grafana'srefreshfield semantics:With
refresh: 2, changing thetierdropdown did not trigger a re-query of therepodropdown -- users would see stale repo options until the time range changed. Withrefresh: 1, Grafana correctly cascades re-queries to dependent variables when$tierchanges. This is the standard Grafana pattern for chained template variables.No Terraform state risk -- dashboard JSON is a declarative resource definition. Applying this change simply updates the dashboard in-place.
BLOCKERS
None.
NITS
None.
SOP COMPLIANCE
fix: dashboard repo variable refresh on tier change)PROCESS OBSERVATIONS
Clean nit-to-fix cycle: post-merge review of PR #432 identified the issue, this PR addresses it in isolation. Low change failure risk -- the fix aligns with documented Grafana behavior for chained variables.
VERDICT: APPROVED