this adds a proposal for a GrafanaLibraryPanel CRD, which would enable the operator to manage Library Panels similar to other assets. the Library Panel behaves similar as a Dashboard; it has a JSON model and can optionally be associated to a Folder.
full disclosure: we actually have a patch that we are using in production that implements the proposal documented here. We don't have chainsaw tests for it though; I think that would be one possible next step. still, open to discussion about the approach. we opted to implement this with high parity with how Dashboards worked because we reasoned folks might want to manage the JSON models for both in similar ways, be that as config maps, or nested on the CR itself, or external URL.
this adds a proposal for a GrafanaLibraryPanel CRD, which would enable the operator to manage Library Panels similar to other assets. the Library Panel behaves similar as a Dashboard; it has a JSON model and can optionally be associated to a Folder.
full disclosure: we actually have a patch that we are using in production that implements the proposal documented here. We don't have chainsaw tests for it though; I think that would be one possible next step. still, open to discussion about the approach. we opted to implement this with high parity with how Dashboards worked because we reasoned folks might want to manage the JSON models for both in similar ways, be that as config maps, or nested on the CR itself, or external URL.