show error message in GrafanaDashboard CR when json in CR is invalid

[czchen]

Is your feature request related to a problem? Please describe.

When json in GrafanaDashboard CR is invalid, the error message is only available in grafana-operator, but not CR itself. The GrafanaDashboard CR has no indicator that the json is invalid, and user does not know what's wrong until checking grafana-operator log.

(If applicable)If your feature request solves a bug please provide a link to the community issue
N/A

Describe the solution you'd like

When json in GrafanaDashboard CR is invalid, the error message shall be available in GrafanaDashboard CR itself so that user knows there is problem in json.

Describe alternatives you've considered
N/A

Additional context
N/A

Existing solutions
N/A

[bukovjanmic]

The same is valid for other CRs as well.

For example, one of our users defined a GrafanaDatasource with a reference to a Secret, but with a key in Secret missing.

The error is logged in operator logs, where users do not have access. The CR itself was left intact, with no change in status field, so from users perspective it seems the GrafanaDatasource is just ignored by the operator.

What should happen is that the error message that is logged in operator logs should also appear in the status section of the CR as well.

[theSuess]

We recently introduced status conditions for the dashboard resource and are tracking conditions implementation in #1450.

Keeping this open to make sure the specific use case of invalid json is correctly reported.

Now that status.conditions is implemented for the dashboard resource, this would be a good first contribution to the project