Description
The current PR workflow does not validate next-gen Grafana dashboard generation when a JSON file under metrics/grafana is modified.
make generate-next-gen-grafana is currently executed through make check, but the PR workflow excludes *.json changes from triggering that job. As a result, changes to files such as metrics/grafana/ticdc_new_arch.json can bypass the generation check, and stale generated dashboards under metrics/nextgengrafana may slip through CI.
Expected Behavior
When a JSON file under metrics/grafana is changed, CI should run the next-gen Grafana generation check and fail if the generated files are not updated.
Changes outside metrics/grafana should not trigger this check.
Proposed Solution
Split the next-gen Grafana generation check out of the general make check target and add a dedicated GitHub Actions workflow that runs only for metrics/grafana/*.json changes.
Description
The current PR workflow does not validate next-gen Grafana dashboard generation when a JSON file under
metrics/grafanais modified.make generate-next-gen-grafanais currently executed throughmake check, but the PR workflow excludes*.jsonchanges from triggering that job. As a result, changes to files such asmetrics/grafana/ticdc_new_arch.jsoncan bypass the generation check, and stale generated dashboards undermetrics/nextgengrafanamay slip through CI.Expected Behavior
When a JSON file under
metrics/grafanais changed, CI should run the next-gen Grafana generation check and fail if the generated files are not updated.Changes outside
metrics/grafanashould not trigger this check.Proposed Solution
Split the next-gen Grafana generation check out of the general
make checktarget and add a dedicated GitHub Actions workflow that runs only formetrics/grafana/*.jsonchanges.