VoidQuark

Is there anyone working on this issue?

I think it would be good to rename the variable `grafana_alerting` to `grafana_unified_alerting`.

I can confirm that `restart_sec` works for me to keep it idempotent. Example: ```yaml #Part of the play - name: Create example container containers.podman.podman_container: name: "example" image: "yourImage" state: "created"...

If you're seeking inspiration, perhaps aligning your PR with the `Loki/Promtail` approach. They already support Debian/RHEL systems with SELinux out of the box.

> @voidquark can you link me please? [Promtail role](https://github.com/grafana/grafana-ansible-collection/tree/main/roles/promtail) and [Loki role](https://github.com/grafana/grafana-ansible-collection/tree/main/roles/loki)

Hello @panfantastic, It would be great if you utilize `validate` in a manner similar to Loki validation. - Loki example: ``` - name: Template Loki config - /etc/loki/config.yml ansible.builtin.template: ........

Regarding validation, I don't have the place to test it at the moment, but I believe you can simply follow the steps outlined in [this documentation](https://grafana.com/docs/mimir/latest/configure/about-configurations/#validate-a-configuration). Just make sure you're...

> The alternative view is that you shouldn't leave the system in a broken state such that you can't restart the service - so a change that alters a config...

In my opinion, the last thing that needs to be addressed is the modification of the validation line. ```yaml validate: "mimir -modules --config.file=%s" ``` I removed the `-print.config` part, considering...

I think it can be merged now.