No filter named 'molecule_header' or 'molecule_to_yaml'

[ekbfh]

Issue Type

• Bug report

Molecule and Ansible details

ansible==2.9.14 , molecule==3.1.5

Molecule installation method (one of):

• pip3

Ansible installation method (one of):

• pip3

Desired Behavior

When i set up molecule 3.0.4 for example with ansible 2.9.14 it worked as it supposed, i have all filters.

Actual Behaviour

    - name: Dump instance config
      copy:
        content: "{{ instance_conf | to_json | from_json | molecule_to_yaml | molecule_header }}"
        dest: "{{ molecule_instance_config }}"

  TASK [Dump instance config] ****************************************************
    Monday 02 November 2020  13:09:51 +0000 (0:00:00.046)       0:00:28.665 *******
fatal: [localhost]: FAILED! => {}
MSG:
template error while templating string: no filter named 'molecule_header'. String: {{ instance_conf | to_json | from_json | molecule_to_yaml | molecule_header }}

[pablofelix]

I have the same problem and I had to downgrade molecule version to 3.0.8 and Ansible 2.10.1 python 3.8. In previous version using a linux grep command you can find this filter (molecule_header) in molecule/provisioner/ansible/plugins/filter/molecule_core.py but in the newer version using grep command you can't find this filter. As the error says doesn't exist.
I have look a little bit the library and I've deleted molecule_to_yaml and molecule_header filter and look like than everything is working well without the filters.

• name: Dump instance config
  copy:
  content: "{{ instance_conf | to_json | from_json }}"
  dest: "{{ molecule_instance_config }}"

So looks like that these filters are not needed anymore and molecule is managing internally the json in delegated drivers. But I'm not sure if there is another solution or if I'm right with my suppositions

Anyway if there are another solution I'm really interested to know it.

[noor47-pixel]

i have the same error to with molecule version 3.2.0 and ansible 2.9.10 while i try molecule test where do you delete filter molecule_to_yaml

[greg-hellings]

Do you have a customized create.yml attached to your scenario? In older versions of Molecule it was necessary to have an embedded create/destroy file. Since v3, these are now embedded in the drivers themselves by default. Unless you have customizations to your provisioning or teardown steps, you should remove the create and destroy playbooks from those scenarios where it is possible, in order to reduce maintenance burden.

If you have need of customized provision and teardown, you'll need to use different modules or filters. The to/from_yaml now exist in core Ansible. molecule_header just inserts a comment and can be either ignored or replaced with the comment filter and your own header text. If you really need the support of the exact original versions, you can now get them from this collection: https://galaxy.ansible.com/community/molecule. community.molecule.<filter>. It contains to_yaml, from_yaml, header, and get_docker_networks.

If neither of these avenues are open to you, we'll need to look more closely into what you're facing.

[dogfish182]

I have a customized create file attached, we use aws_ssm to connect to our instances so ssh is 'not a thing' I want open. As such it seems I need to modify the create.yaml.

I'm puzzled how to correct this issue.

How can I use that collection? I followed the instructions in the molecule docs and added that collection

dependency: name: galaxy options: requirements-file: collections.yml

and in that file

`collections:

• community.molecule`

Installing 'community.molecule:0.1.0' to '/Users/ghawker/.cache/molecule/domain_join/default/collections/ansible_collections/community/molecule' Downloading https://galaxy.ansible.com/download/community-molecule-0.1.0.tar.gz to /Users/me/.ansible/tmp/ansible-local-1274wjrzope8/tmpkz5sdqmm community.molecule (0.1.0) was installed successfully INFO Dependency completed successfully.

and the error still throws

"msg": "template error while templating string: no filter named 'molecule_to_yaml'

i had a look and that collection has 'to_yaml' and 'from_yaml'
but nothing about 'molecule_from_yaml' or 'molecule_to_yaml'

I am using the ec2 provisioner, so is there a mismatch here that this provider is using filters no longer supported (I'm using both latest molecule and latest provisioner).

looks like the removal happened here
https://github.com/ansible-community/molecule/pull/2869/files

but the ec2 provisioner still expects them to be there.

[ekbfh]

Yes, i have own delegated create/destroy playbooks with terraform.

According docs, Create/destroy embedded only in docker provisioner, but i'm using ansible.

Main question is: when internal filters was deleted and why?

[felipefrocha]

Also can't find it. there is no clear description in release change notes about it.

[ssbarnea]

Just remove the custom molecule_header and replace molecule_to_yaml with ansible native filters. They were both removed. Read @greg-hellings comments and you should be fine.

[ssbarnea]

I would start by watching https://github.com/ansible-community/molecule/releases

[carranzaa7672]

Thanks for pointing the release notes out! I am able to manually workaround the issue for now.

I am curious to know why we are still using molecule filters when we use molecule to initialize a role. To recreate the issue I ran molecule init role azure_role -d azure then immediately ran molecule test on a fresh molecule installation.

Versions:

molecule 3.2.0 using python 3.6
    ansible:2.10.3
    azure:0.5.0 from molecule_azure
    delegated:3.2.0 from molecule
    docker:0.3.3 from molecule_docker