-
Notifications
You must be signed in to change notification settings - Fork 664
New issue
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
Removal of molecule filters #2872
Comments
Removes molecule ansible filters. Related: ansible/molecule#2872
Removes molecule ansible filters. Related: ansible/molecule#2872
Molecule filters are now moved to their own project: https://galaxy.ansible.com/community/molecule Fixes: #2872
@decentral1se @sshnaidm @cloudnull @geerlingguy @greg-hellings Please comment on this move as I want to minimize disruptions for current users and to assure that they have an easy migration path. My concerns is that this will initially break most drivers, but I will assure a release is not made before I update most of them. |
Molecule filters are now moved to their own project: https://galaxy.ansible.com/community/molecule Fixes: #2872
Molecule filters are now moved to their own project: https://galaxy.ansible.com/community/molecule Fixes: #2872
Removes molecule ansible filters. Related: ansible/molecule#2872
Hey, missed this one but aware of it now, when the 3.1 release comes out, I'll let you know how it goes. Thanks. |
I am still fixing bugs caused by move of docker and podman out of core. It could prove very useful o have someone brave enough to run molecule and main plugins from master branches. |
Molecule ansible filters are not available by default anymore. Related: ansible/molecule#2872
#19) * Use loop instead of with_items Convert the usage of with_items to loops based on docs: https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html#with-items * Remove molecule filters Molecule ansible filters are not available by default anymore. Related: ansible/molecule#2872
Molecule also needs to be bumped to support Ansible 2.10 lint: section changed in Molecule 3.x - adapted. molecule-docker added do test-reqs because it code has moved to it from molecule core pytest-testinfra and pytest-molecule needed for testinfra tests to work [1]: ansible/molecule#2872 Change-Id: I0299f5126ebd080f3912a76294b0013abe7747a0
* Update kayobe from branch 'master' to 0e2efc09ecea8f87209dd1bf0456f313af83610e - Merge "Bump max Ansible version to 2.10" - Bump max Ansible version to 2.10 Molecule also needs to be bumped to support Ansible 2.10 lint: section changed in Molecule 3.x - adapted. molecule-docker added do test-reqs because it code has moved to it from molecule core pytest-testinfra and pytest-molecule needed for testinfra tests to work [1]: ansible/molecule#2872 Change-Id: I0299f5126ebd080f3912a76294b0013abe7747a0
Molecule ansible filters are moved are now moved to a standalone collection https://galaxy.ansible.com/community/molecule and we encourage plugin authors and test writers to either one of:
molecule_to_yaml
andmolecule_from_yaml
with their native ansible counterparts.community.molecule.from_yaml
. Remember to addcommunity.molecule
collection to yourrequirements.yaml
and to install it.As these filters were also present in user managed playbooks like
create.yml
anddestroy.yml
, we aim to make transition easier.Because this is breaking change, it will only be included in
3.1.0
.Reasoning
The main reason behind this move is to finalize decoupling of molecule tool from ansible internals and removing the need to install Ansible python packages in the same python environment as molecule.
If done right, at the end molecule should only be a command line that calls ansible and that the testing playbooks could be run even without molecule itself.
The text was updated successfully, but these errors were encountered: