Donovan Jones
Donovan Jones
It would be great if there was a flag to toggle this behaviour. I just ran beautysh on a large infrastructure codebase that makes use of shellcheck, 95% of the...
This is the same issue as #122. I hit it when moving to 2.1 or 2.2. I don't know of a good way to support all versions.
I tried a couple of things that did not work: ``` #!/usr/bin/env ansible-playbook --- - name: Test always run / check_mode hosts: localhost tasks: - name: Test false 1 command:...
Should be OK yes, people who have already moved to 2.2 can do what I did and patch their local copy if they want to get rid of the warnings.
@Tanbouz suggestion works for me.
Can confirm this issue occurs on Ubuntu 18.04 LTS with v0.2.1.
I tried reverting to v0.2.0 to avoid the issue but its still there unfortunately.
I am working around this issue by adding StandardOutput=null in the [Service] of my unit file /lib/systemd/system/journald-cloudwatch-logs.service
@RichardHightower @MammatusPlatypus ping