gofrolist/Ansible Molecule

Run Ansible Molecule

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
molecule_options	Options: --debug / --no-debug Enable or disable debug mode. Default is disabled. -v, --verbose Increase Ansible verbosity level. Default is 0. -c, --base-config TEXT Path to a base config (can be specified multiple times). If provided, Molecule will first load and deep merge the configurations in the specified order, and deep merge each scenario's molecule.yml on top. By default Molecule is looking for '.config/molecule/config.yml' in current VCS repository, in collections at 'extensions/molecule/config.yml', and if not found it will look in user home. (None). -e, --env-file TEXT The file to read variables from when rendering molecule.yml. (.env.yml) --version Show version information and exit. -h, --help Show this message and exit.	no	—
molecule_command	Commands: check Use the provisioner to perform a Dry-Run (destroy, dependency, create, prepare, converge). cleanup Use the provisioner to cleanup any changes made to external systems during the stages of testing. converge Use the provisioner to configure instances (dependency, create, prepare converge). create Use the provisioner to start the instances. dependency Manage the role's dependencies. destroy Use the provisioner to destroy the instances. drivers List drivers. idempotence Use the provisioner to configure the instances. init Initialize a new scenario. list List status of instances. login Log in to one instance. matrix List matrix of steps used to test instances. prepare Use the provisioner to prepare the instances into a particular starting state. reset Reset molecule temporary folders. side-effect Use the provisioner to perform side effects to the role. syntax Use the provisioner to syntax check the role. test Test (dependency, cleanup, destroy, syntax, create, prepare, converge, idempotence, side_effect, verify, cleanup, destroy). verify Run automated tests against instances.	yes	test
molecule_args	Arguments: -s, --scenario-name TEXT Name of the scenario to target. May be specified multiple times. (default: default) -d, --driver-name [containers\|podman\|openstack\|gce\|ec2\|docker\|vagrant\|default\|azure] Name of driver to use. --all / --no-all Target all scenarios. Overrides scenario-name. (default: disabled) --destroy [always\|never] The destroy strategy used at the conclusion of a Molecule run. (default: always) --parallel / --no-parallel DEPRECATED: Use --workers instead. Enable or disable parallel isolation mode. (default: disabled)	no	—
molecule_working_dir	Path to another directory in the repository, where molecule command will be issued from. Useful in those cases where Ansible roles are not in git repository root.	no	${{ github.repository }}

Outputs

no outputs