Migrating to molecule v3 checklist

How to migrate to molecule v3 (3.0a9 or newer)

Only delegated, docker and podman providers are ready, so if you use others, delay till they are updated or preferably give a hand with that.

• remove scenario.name from molecule.yaml, from now on, only folder name determines the scenario name
• remove lint: sections from molecule.yaml or replace them with newer syntax from documentation
• if you use testinfra, add it as a pip dependency, is no longer installed by default
• if you use linters, you need to add them as pip dependencies
• (optional) rename playbook.yml to converge.yml to avoid a deprecation message

Known regressions with v3

• TBH

When not to migrate to v3

If you use one of:

• non-core providers like Azure, EC2, DigitalOcean, GCE, HetznerCloud, Linode, LXD, OpenStack or Vagrant, you probably do want to delay migration until they are updated. Keep in mind that as well as molecule, they are fully community supported, so if nobody steps in to help, they will be affected by bit rot and become unusable.

• you are using goss verifier which was removed. It can still be re-implemented as a plugin, if anyone is willing to help.

[geerlingguy]

Heh, I just started seeing new failures today as Molecule 3.0 arrived and I install via pip install molecule:

ERROR: Failed to pre-validate.

{'lint': ['must be of string type']}

Luckily for this project I already had the updated molecule.yml ready to go, but it looks like I’ll need to quickly get my other projects up to speed to prevent a CI-pocalypse! See fix: https://github.com/ansible-collections/kubernetes/pull/32/files

Note that a quick fix if you don’t want Molecule 3 yet (e.g. wait to migrate your tests to it), change your pip install to:

pip3 install molecule===2.22

[karcaw]

I suggest you spell molecule properly in the tile of the issue? mocule => molecule