A vim plugin for syntax highlighting Ansible's common filetypes
Full Changelog: https://github.com/pearofducks/ansible-vim/compare/3.2...3.3
ansible_with_keywords_highlight
is soft-deprecated (there is backwards compatibility in place for now), and is replaced with ansible_loop_keywords_highlight
which aligns better with modern Ansible keywords for loopsThanks to @pescobar the snippet-generation script now supports fully qualified collection names when used against Ansible 2.10 or greater.
https://docs.ansible.com/ansible/latest/user_guide/collections_using.html
Breaking: Drops Python 2 support in UltiSnip generation
Change: Makes the UltiSnip snippets generation reproducible
Add highlighting for the loop
keyword, which has been available since Ansible 2.5.
https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html
Notable changes:
generate.py
, as well as Mac Homebrew supportregexpengine
workaround was removed that was breaking some setupsOtherwise there were minor fixes included in this changeset.
yaml.ansible
.yaml.jinja2.ansible
, if there are strong opinions on this please open an issue.{ 'for': 'ansible' }
in vim-plug. Otherwise this change should not break anything.g:ansible_extra_syntaxes
is deprecated in favor of g:ansible_template_syntaxes
— which will use conditional compound filetypes, instead of sourcing all filetypes listed and hiding them under ansible_template
.ruby.jinja2
instead of ansible_template
One non-breaking change is also added, this plugin gains additional compatibility with stephpy/vim-yaml — syntax highlights will be improved when using this plugin.
DEPRECATED
This is the last version using ansible
as the filetype for Ansible playbooks. This tag is created as a convenience for anyone to branch from or keep as their plugin target.
Changes:
hosts
files are now highlighted with our own rules, rather than use dosini
rules. This allows for much better treatment of variables and Ansible's special categories (e.g. [foo:vars]).