volker.raschekandCopilot
afd4288ebd
The repository mixed both extensions, the molecule scenario used yml while the role itself used yaml. The yml extension is the one ansible-galaxy and molecule generate, so it is applied throughout and across the sibling roles. The include_tasks calls in tasks/main.yml and tasks/create_unix_user.yml name their target explicitly and were adjusted accordingly, otherwise the role would no longer find the included task files. Co-authored-by: Copilot <copilot@github.com>
30 lines
721 B
YAML
30 lines
721 B
YAML
name: Molecule
|
|
|
|
on:
|
|
pull_request:
|
|
types: [ "opened", "reopened", "synchronize" ]
|
|
push:
|
|
branches: [ '**' ]
|
|
tags-ignore: [ '**' ]
|
|
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
molecule:
|
|
name: Molecule
|
|
runs-on: ubuntu-latest-amd64
|
|
steps:
|
|
# The scenario includes the role by its directory name, whose parent is used as roles path.
|
|
- uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
|
|
with:
|
|
path: unix-users
|
|
- name: Install molecule
|
|
run: |
|
|
apt update --yes
|
|
apt install --yes python3-pip
|
|
pip3 install --break-system-packages molecule docker
|
|
- name: Run molecule
|
|
run: molecule test
|
|
working-directory: unix-users
|