Closed Pton closed 6 years ago
It looks like you are using ansible 2.3 or lower, which is no longer supported.
In that case the error makes sense. Would it be possible to add that information to the release notes of version 3.0.0? This information might be helpful to others.
it is showing up in Ansible galaxy, in the meta.yml file, in our twitter account and in the commit message
El jue., 11 oct. 2018 a las 11:39, Peter Ton (notifications@github.com) escribió:
In that case the error makes sense. Would it be possible to add that information to the release notes of version 3.0.0? This information might be helpful to others.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ansistrano/deploy/issues/316#issuecomment-428889947, or mute the thread https://github.com/notifications/unsubscribe-auth/AAldXZjFa_yKEiY3SOnr03PkKHFgXz39ks5ujxHXgaJpZM4XXFzz .
Not specifying optional steps like
ansistrano_before_setup_tasks_file
will result in the following error:ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
Probably caused by the switch from
include
toinclude_tasks
in https://github.com/ansistrano/deploy/commit/6a7a825cc03bf27ab59dd3804ba561dbedb46650.