810bbec590
In order to verify that molecule requirements are satisfied we add a noop molecule scenario that installs requirements and run a noop task. We can expand the scenario in the futute or add new ones, though for now goal is to ensure that updating requirements is not breaking other roles having valid scenarios around. Change-Id: Id0abc217d404af4a08532707e60d738613c9a7ed
29 lines
551 B
YAML
29 lines
551 B
YAML
---
|
|
dependency:
|
|
name: galaxy
|
|
options:
|
|
requirements-file: ansible-collection-requirements.yml
|
|
force: true
|
|
|
|
driver:
|
|
name: docker
|
|
|
|
platforms:
|
|
- name: "integrated-${MOLECULE_SCENARIO_NAME}"
|
|
image: "${DOCKER_REGISTRY:-quay.io/gotmax23}/${DOCKER_IMAGE_TAG:-debian-systemd:bookworm}"
|
|
command: ${DOCKER_COMMAND:-""}
|
|
pre_build_image: true
|
|
privileged: true
|
|
systemd: true
|
|
|
|
provisioner:
|
|
name: ansible
|
|
lint:
|
|
name: ansible-lint
|
|
config_options:
|
|
defaults:
|
|
inject_facts_as_vars: false
|
|
|
|
scenario:
|
|
name: default
|