fix: Don't log config deployments

[SuperQ]

Avoid logging on some config files may contain secrets.

Fixes: #72

[laurent-indermuehle]

Because the variable is used in a template, arguments_spec won't work?

Because to me, it would be better to have the no_log on the variable instead of the whole task.
You wouldn't need to check the __testing vars and in case of issue on production the task will output the error instead of the "no_log" warning.

[gardar]

Rather than using our own variables I would prefer to use variables that are already present, some of these:

• no_log: "{{ molecule_no_log }}"
• no_log: "{{ (lookup('env', 'MOLECULE_DEBUG')) }}"
• no_log: "{{ (lookup('env', 'CI')) }}" (comes from github ci)
• etc.

[gardar]

Because the variable is used in a template, arguments_spec won't work?

Because to me, it would be better to have the no_log on the variable instead of the whole task. You wouldn't need to check the __testing vars and in case of issue on production the task will output the error instead of the "no_log" warning.

Ansible doesn't support no_log for individual parameters of tasks, so you either hide the logging of the whole task or not at all.
Ansible modules however can define individual parameters as no log, but that's unfortunately no help here.

[SuperQ]

Verified with a local verbose molecule test:

TASK [prometheus.prometheus.alertmanager : Copy alertmanager config] ***********
changed: [debian-11] => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": true
}