mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-09-06 07:53:14 +00:00
Slavi PantaleevandClaude Opus 5
705f561777
Scenarios install their Galaxy dependencies with `force: true`, so two roles running at once re-extract the same collections and roles into ~/.ansible and pull them out from under each other mid-play. It surfaces as a collection that was working moments earlier going missing: the connection plugin 'community.docker.docker' was not found Found while running five scenarios in parallel, where it cost a run. ANSIBLE_HOME relocates both `collections/` and `roles/`, so one variable covers both halves; the scenarios' ANSIBLE_ROLES_PATH workaround now follows it rather than hardcoding ~/.ansible/roles. Left alone if already set, and unset in CI, where each role runs in its own job and has nothing to collide with. Verified by removing var/molecule-ansible-home entirely and running matrix-alertmanager-receiver from cold: green through idempotence, with the collections and roles landing under the per-role directory - which also shows nothing was quietly relying on the shared ~/.ansible being populated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SEH3vxYSQ5SV4N5z61eyGT
76 lines
2.6 KiB
YAML
76 lines
2.6 KiB
YAML
# SPDX-FileCopyrightText: 2026 Slavi Pantaleev
|
|
#
|
|
# SPDX-License-Identifier: AGPL-3.0-or-later
|
|
|
|
---
|
|
dependency:
|
|
name: galaxy
|
|
options:
|
|
requirements-file: requirements.yml
|
|
force: true
|
|
driver:
|
|
name: docker
|
|
platforms:
|
|
- name: heisenbridge-${MOLECULE_DISTRO:-ubuntu2604}-default
|
|
image: "geerlingguy/docker-${MOLECULE_DISTRO:-ubuntu2604}-ansible:latest"
|
|
command: ${MOLECULE_DOCKER_COMMAND:-""}
|
|
volumes:
|
|
- /sys/fs/cgroup:/sys/fs/cgroup:rw
|
|
cgroupns_mode: host
|
|
privileged: true
|
|
pre_build_image: true
|
|
provisioner:
|
|
name: ansible
|
|
config_options:
|
|
defaults:
|
|
callback_result_format: yaml
|
|
inventory:
|
|
group_vars:
|
|
all:
|
|
matrix_bridge_heisenbridge_container_network: heisenbridge-molecule
|
|
|
|
# The stub prepare.yml stands up. Heisenbridge talks to it while
|
|
# starting; it is not a real homeserver and nothing is asserted about it.
|
|
matrix_bridge_heisenbridge_homeserver_url: http://matrix.molecule.local:8008
|
|
|
|
matrix_bridge_heisenbridge_appservice_token: molecule_as_token_4f2a91
|
|
|
|
# Heisenbridge refuses to start without an owner - it is the Matrix user
|
|
# allowed to administer the bridge.
|
|
matrix_bridge_heisenbridge_owner: "@molecule-admin:molecule.local"
|
|
|
|
# Deliberately different from the role's defaults, so verify.yml can tell
|
|
# what the role rendered apart from what heisenbridge would have chosen.
|
|
matrix_bridge_heisenbridge_path_prefix: /molecule-heisenbridge
|
|
|
|
# identd binds host port 113, which would collide with anything else on
|
|
# the machine and is not what this scenario is proving.
|
|
matrix_bridge_heisenbridge_identd_enabled: false
|
|
|
|
# Traefik is not deployed here, so the labels the role would render for
|
|
# it are switched off and their absence is asserted instead.
|
|
matrix_bridge_heisenbridge_container_labels_traefik_enabled: false
|
|
|
|
# verify.yml runs as its own play, where role defaults are out of scope.
|
|
# Unlike the mautrix bridges, heisenbridge keeps everything directly
|
|
# under its base path rather than in config/ and data/ subdirectories.
|
|
matrix_bridge_heisenbridge_base_path: /matrix/heisenbridge
|
|
env:
|
|
# Workaround for https://github.com/ansible/molecule/issues/4391
|
|
ANSIBLE_ROLES_PATH: ${MOLECULE_PROJECT_DIRECTORY}/../..:/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:${ANSIBLE_HOME:-~/.ansible}/roles
|
|
scenario:
|
|
test_sequence:
|
|
- dependency
|
|
- cleanup
|
|
- destroy
|
|
- syntax
|
|
- create
|
|
- prepare
|
|
- converge
|
|
- idempotence
|
|
- verify
|
|
- cleanup
|
|
- destroy
|
|
verifier:
|
|
name: ansible
|