Missing ec2 driver defaults in scenario

[gamblar13]

As i started using Molecule 6.0.2 with the newest ec2-driver, "molecule init..." command doesn't provide the correct file contents matching the drivers ec2. For example the create.yml has not the values from

src/molecule_plugins/ec2/cookiecutter/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}

Instead the values are from ...molecule/data/templates/scenario/create.yml.j2

Installation method

• Python venv
• pip3 install molecule 'molecule-plugins[ec2]'

Version Information: molecule 6.0.2 using python 3.10 ansible:2.15.3 azure:23.5.0 from molecule_plugins containers:23.5.0 from molecule_plugins requiring collections: ansible.posix>=1.3.0 community.docker>=1.9.1 containers.podman>=1.8.1 default:6.0.2 from molecule docker:23.5.0 from molecule_plugins requiring collections: community.docker>=3.0.2 ansible.posix>=1.4.0 ec2:23.5.0 from molecule_plugins gce:23.5.0 from molecule_plugins requiring collections: google.cloud>=1.0.2 community.crypto>=1.8.0 podman:23.5.0 from molecule_plugins requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0 vagrant:23.5.0 from molecule_plugins

Thanks

[apatard]

Not really a plugin issue. It's probably a "side effect" of https://github.com/ansible/molecule/commit/21dcd2bb7e8e9002be8bbc19de3e66ec3ce586f1. Anyway the plan of the molecule maintainers is to kill the plugins even if currently, there's nothing providing equivalent of the plugin repo. I'm afraid you'll have to write your own playbooks.

[gamblar13]

Thanks for your answer. I see. This is really disappointing. The templates were a great help.

[theko2fi]

Killing the plugins is a bad idea. Why break something that's working well? It's really disappointing.