volker.raschekandCopilot
a6e8555e13
The scenario now starts its containers with community.docker instead of containers.podman, because docker is the container runtime available on the CI runner. The connection plugin, the login command and the declared collections were adjusted accordingly and the docker SDK for python is installed in the workflow, since the module requires it. Co-authored-by: Copilot <copilot@github.com>
31 lines
805 B
YAML
31 lines
805 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
|
|
steps:
|
|
# The scenario includes the role by its name, so the directory must be named like the role and not like the
|
|
# repository. Its parent is used as roles path.
|
|
- uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
|
|
with:
|
|
path: certificate_authority
|
|
- 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: certificate_authority
|