I’ve been trying to get my playbooks to play out cleanly during a dry run with the --check switch. I’ve ran into a problem where one of my tasks using the file module fails because a user does not exist yet. The user is added prior to this task running so when not using the --check switch it plays out fine. Has anyone ran into this and have a valid work around to get --check to play out cleanly? I also cannot use ignore_errors parameter as if this actually fails during the deployment I want it to do the default action and stop. Thanks ahead for anyone’s help or response.
Thanks,
Chris