The molecule documentation doesn't provide any examples of how to use third party drivers AFAIK. Could you provide some here?

The current status of this driver is unmaintained and I am looking forward to handle its maintenance to someone that wants to assure molecule can use this driver.

Unless we find a maintainer this driver will be removed from molecule all-in-one container.

I will support with CI/CD guidance and help.

Looking into how to install molecule-digitalocean, I ended up looking through driver.py since I couldn't find any other documentation.

There it says:

$ pip install 'molecule[digitalocean]'

However, this doesn't seem to work anymore:

WARNING: molecule 3.1.0 does not provide the extra 'digitalocean'

The instructions should probably be updated.

ISSUE

Following filters are missing

• molecule_header
• molecule_from_yaml

Description

• molecule create deploys the droplet, but fails to write the config to filesystem with the error filter molecule_header missing. so molecule doesn't know about the droplet that's actually created.
• molecule destroy This command does not destroy the droplet, as the config was not written to filesystem by create method in the first place. One has to manually cleanup/destroy the droplet on digitalocean.

Steps to reproduce

molecule init role -d digitalocean <rolename>
cd <rolename>

modify molecule.yaml eg:

---
dependency:
  name: galaxy
driver:
  name: digitalocean
platforms:
  - name: instance
    region: tor1
    size: s-1vcpu-2gb
    image: ubuntu-18-04-x64
provisioner:
  name: ansible
  log: yes
verifier:
  name: ansible

$ molecule create 

PLAY [Create]

TASK [Dump instance config] ************************************************************************************************************************************************************************************
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 }}"}

$ molecule destroy

PLAY [Destroy] *************************************************************************************************************************************************************************************************

TASK [Populate instance config] ********************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"msg": "template error while templating string: no filter named 'molecule_from_yaml'. String: {{ lookup('file', molecule_instance_config) | molecule_from_yaml }}"}

Expected Behavior

• molecule create should create the droplet and write the config.
• molecule list should list the instances
• molecule destroy should destroy the instances.

REASON

As of molecule v3, ansible molecule filters have been removed.

• ansible/molecule#2869
• https://github.com/ansible-community/molecule/releases/tag/3.1.1

SOLUTION

• Remove those 2 filters from the generated code works. But this approach would require modifying every molecule generated role manually.
• A better approach would be to modify the cookiecutter template.

The default branch should be renamed to main.