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>
22 lines
524 B
YAML
22 lines
524 B
YAML
name: Release Ansible Role
|
|
|
|
on:
|
|
push:
|
|
tags:
|
|
- '**'
|
|
workflow_dispatch: {}
|
|
|
|
jobs:
|
|
release:
|
|
name: Release Ansible Role
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Install Ansible Galaxy
|
|
run: |
|
|
apt update --yes
|
|
apt install --yes ansible
|
|
- env:
|
|
ANSIBLE_GALAXY_TOKEN: ${{ secrets.ANSIBLE_GALAXY_TOKEN }}
|
|
name: Update Ansible Role in Ansible Galaxy
|
|
run: |
|
|
ansible-galaxy role import --token=${ANSIBLE_GALAXY_TOKEN} volker-raschek ${GITHUB_REPOSITORY#*/} |