gardar

Turns out there is already a way to get json/yaml by wrapping the `to_json` and `to_yaml` macros around the data returned from the vault plugin. Few examples: Using the `vault_secret`...

Using docker/podman images with systemd in molecule is quite common actually so that shouldn't be an issue. But actually you don't even need to define your own platform as they...

There are different reasons I've seen that happen, do you have the molecule docker driver installed? and are the containers running?

@ohdearaugustin can you please rebase?

@floerica could you open a PR?

Thanks for the PR. Has that setting been deprecated in grafana? Or are you suggesting that this should be removed since it's not referenced anywhere directly in the ansible role?

Quoting to reply to the question from ansible-community/molecule-podman#142 @ssbarnea https://github.com/ansible-community/molecule-podman/pull/142#issuecomment-1286163775 > I can answer this one. Podman collection was not really actively maintained and that gave more flexibility. Things change,...

Having the plugins/drivers as ansible collections sounds like an excellent idea, as it would make it feel more closely integrated in ansible. With that it would also perhaps make sense...

My suggestion for now would be to group the architectures and then have different tasks in the playbook targeting the different groups.

@prakyathraj please post the variable you are attempting to use. Btw, you can take a look at the alternative molecule scenario for more examples of a working config https://github.com/prometheus-community/ansible/blob/f3514a9e97dfc3d64f02aefd299487efd99e779f/roles/process_exporter/molecule/alternative/molecule.yml#L18-L29