gardar
gardar
Can you please rebase and fix the conflicts with the main branch?
> > Do you mind rebasing this again? I just did some significant refactoring of the roles in #425 > > While I hopefully solved these merge conflicts one last...
ping @SuperQ
All set on my end. @SuperQ Any final thoughts before we merge this?
As you correctly assumed this is to avoid leaking credentials to the logs. Unfortunately it is the only way I can think of to be absolutely sure that Ansible won't...
Any task that fails may print the variables passed to it, depending on the verbosity and callback plugin settings. Even if we separate the validation into two tasks—one for the...
I don't think that would work because if you are using `no_log` on that task then you can't see why it's failing and it's essentially the same thing as we...
Is there any reason why you need to apply `become` to the whole playbook? When you apply the become to the playbook you are overwriting the individual `become` configuration of...
> Are there any workarounds so far? Yes - don't run the whole playbook with `become`, the role does it when needed
Are you deploying from mac os? In that case you are probably missing gnu-tar as documented here: https://github.com/prometheus-community/ansible/tree/main/roles/node_exporter#requirements