-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Make relation_name optional in lib, improve alert dir resolution #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pattern evolved a bit, check out the latest Grafana and Prometheus libs. Also, check the content of the Grafana docu, I like that a lot in terms of which info we provide.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Should use ops.charm.RelationRole
.
@Abuelodelanada please clarify what addition to the metadata.yaml must take place in the charm that wants to use the library. See https://github.com/canonical/grafana-operator/blob/7f731fd7c8af6e9fff78230d014d412b8fcab7e0/lib/charms/grafana_k8s/v0/grafana_dashboard.py#L294 |
Fixing merge conflics in @mmanciop #17, lint and static analysis.
Align behavior of the Loki library to that of Prometheus, see canonical/prometheus-k8s-operator#135