Thanks for this contribution! We can look at it next week. In the meantime, there's a few lint type things noted in the PR. Can you review them?

Thanks for this contribution! We can look at it next week. In the meantime, there's a few lint type things noted in the PR. Can you review them?

Will do when possible, please note that the changes are not final, some tests are missing and some features like list -r are behaving in a weird manner.

Another important note that I think will need some further discussion here is that there's no name and/or uid for such object and I truly don't know how to handle it.

Another important note that I think will need some further discussion here is that there's no name and/or uid for such object and I truly don't know how to handle it.

How did @theSuess handle it for the equivalent Grafana resource? I think the pattern is already there.

How did @theSuess handle it for the equivalent Grafana resource? I think the pattern is already there.

Good point, seems like the implementation is based on having a static name/uid for said object, I could try to align my implementation with theirs.

Another issue I'm currently having is that pkg/mimir/rules_test.go needs changing as I changed the mimir client, is this test even relevant? I see that the rules are being tested as part of the integration tests under integration/mimir/rules_test.go