gardar
gardar
Thanks! Do you know if using `/run/alertmanager.pid` will cause issues on versions older than 239? Wondering if we could just use `/run/` for all versions.
> As far as i know, `/run` directory exists on systemd-based systems from 2011: https://lwn.net/Articles/436012/ Since introduction of `/run`, many distros implemented bind-mounting `/var/run` to `/run` or vice versa for...
Is this still a issue?
I believe this is caused by a known issue with python on mac os, please try the workaround from the ansible docs. https://docs.ansible.com/ansible/latest/reference_appendices/faq.html#running-on-macos-as-a-controller
Obsoleted by #425 Please use `--skip-tags install` or `--skip-tags _install` to skip install
There are reasons why it is downloaded on the provisioner and not directly on the target, it saves you from downloading the binary multiple times and it's not always that...
Hmm, never ran into this issue before. we're testing the roles with the version set to `latest` and it does pass for ansible versions 2.9 - 2.14 as you can...
Did you ever figure this out? Could it be that you have `gather_facts: false` in your playbook? In that case you might be able to use `"{{ inventory_hostname }}"` instead.