Specifying Grafana dashboards/objects in pure Go is lovely, but unless there's a straightforward way to send those to a Grafana instance, the user is still stuck. We need to integrate a client.
This does end up getting tangled with questions we're resolving in grafana/grafana around exactly how core kind schemas get written, and the availability of the new k8s api. Still, it's hard to imagine a scenario where we don't make clients for both existing API (which should be generated from swagger) and k8s API (client-go or a derivation) usable for both.
It's plausible that grok's other lang targets will build on top of this client, and maybe the Go target more broadly - like, the terraform provider very likely will
Specifying Grafana dashboards/objects in pure Go is lovely, but unless there's a straightforward way to send those to a Grafana instance, the user is still stuck. We need to integrate a client.
This does end up getting tangled with questions we're resolving in grafana/grafana around exactly how core kind schemas get written, and the availability of the new k8s api. Still, it's hard to imagine a scenario where we don't make clients for both existing API (which should be generated from swagger) and k8s API (client-go or a derivation) usable for both.
It's plausible that grok's other lang targets will build on top of this client, and maybe the Go target more broadly - like, the terraform provider very likely will