feat: Add grafana-dashboard action #14
No reviewers
Labels
No labels
priority/P0
priority/P1
priority/P2
priority/P3
size/L
size/M
size/S
size/XL
size/XS
state/done
state/in-progress
state/in-review
state/needs-refinement
state/ready
type/bug
type/chore
type/feature
type/refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
amtronics/platform-actions!14
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/grafana-dashboard-action"
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?
What
A shared
grafana-dashboardcomposite action: renders an app's standardmonitoring dashboard and pushes it into that app's own Grafana folder via the
API (ensures the folder, overwrites the dashboard).
Why
App dashboards should live with each app, not centralised — but the layout
should be one standard, not N drifting copies. This action holds the single
template; each app calls it with its own params (job, folder, containers) from
its own pipeline. Same model as release@v3 / deploy-vps@v3.
Notes
Only job label + container names are substituted; Grafana
${datasource}and
{{job}}tokens are preserved.grafana-tokenskips the push (an app without monitoring configureddeploys unchanged).
leftover placeholders, bash syntax clean.
v3tag so consumers pinning@v3pick it up.