# Bare Grafana dashboard JSON files are kept here as a CONVENIENCE source
# for the file-provisioning path on noc1 (per
# feedback_grafana_dashboard_shape_depends_on_noc1_delivery_path and
# feedback_monitoring_k8s_target_vs_live_podman). They are NOT K8s
# manifests — they have no `apiVersion` / `kind` / `metadata`. ArgoCD's
# kubernetesIngress provider tries to unmarshal every file in the
# directory and chokes on raw dashboard JSON with "Object 'Kind' is
# missing", which then poisons manifest generation for the whole
# infra-monitoring Application.
#
# When a dashboard needs to be K8s-deployed (i.e. file-provisioned via
# Grafana sidecar in noc-monitoring.yaml), wrap the JSON in a ConfigMap
# YAML next to it (see grafana-dashboard-remotedesktop.yaml as the
# canonical pattern).
*.json