Skip to content

molecule init scenario ignores the -d flag #4448

@danielpodwysocki

Description

@danielpodwysocki

Prerequisites

  • This was not already reported in the past (duplicate check)
  • It does reproduce it with code from main branch (latest unreleased version)
  • I include a minimal example for reproducing the bug
  • The bug is not trivial, as for those a direct pull-request is preferred
  • Running pip check does not report any conflicts
  • I was able to reproduce the issue on a different machine
  • The issue is not specific to any driver other than 'default' one

Environment

(venv) (devbox) ➜  juno_k3s_private git:(tooling-setup) ✗ pip freeze  | grep -E "molecule|molecule-plugin"                                                                                                                                                                 (⎈|N/A:default) 
molecule @ git+https://github.com/ansible/molecule@8fd4ee7b552c349f50c6c1249024bc35a7e2069d
molecule-plugins==23.7.0

(venv) (devbox) ➜  juno_k3s_private git:(tooling-setup) ✗ molecule --version                                                                                                                                                                                               (⎈|N/A:default) 
molecule 25.4.1.dev20 using python 3.13 
    ansible:2.18.6
    gce:23.7.0 from molecule_plugins requiring collections: google.cloud>=1.0.2 community.crypto>=1.8.0
    containers:23.7.0 from molecule_plugins requiring collections: ansible.posix>=1.3.0 community.docker>=1.9.1 containers.podman>=1.8.1
    ec2:23.7.0 from molecule_plugins
    openstack:23.7.0 from molecule_plugins requiring collections: openstack.cloud>=2.1.0
    docker:23.7.0 from molecule_plugins requiring collections: community.docker>=3.10.2 ansible.posix>=1.4.0
    azure:23.7.0 from molecule_plugins
    vagrant:23.7.0 from molecule_plugins
    podman:23.7.0 from molecule_plugins requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0
    default:25.4.1.dev20 from molecule

What happened

When running molecule init scenario --driver-name ec2 debian12, the plugin from https://github.com/ansible-community/molecule-plugins does not get populated correctly.

Instead the default driver gets written in.

This is very unfriendly to new users to molecule, since they might not be familiar with how to build this out from scratch - or substitute in the templates from molecule-plugins.

Reproducing example

molecule init scenario --driver-name ec2 myscenario
cat molecule/myscenario/create.yml

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions