We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No description provided.
The text was updated successfully, but these errors were encountered:
I think the rescue feature of ansible 2 will do the job
Sorry, something went wrong.
I think we can register results and check them later before bailing out, i.e.
- name: update current symlink register: symlink_result ... - name: cleanup failed release when: symlink_result|failed and ansistrano_cleanup_after_failure ...
see http://docs.ansible.com/ansible/playbooks_filters.html#filters-often-used-with-conditionals
Uh, no, I'm wrong. Like @FlxPeters said, we will be able to solve this in a clean manner after Ansistrano v2.0 is released.
Do you have any plans about the 2.x branch? I think it would be great to start this. Ansible 2.x is there for quiet a time now.
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: