Files
matrix-docker-ansible-deploy/roles/custom/matrix-bridge-heisenbridge/molecule/default/molecule.yml
T
Slavi PantaleevandClaude Opus 5 8cd6ea1eef Add a Molecule scenario for heisenbridge, and the hostname family to the shared context
The third shape: a non-mautrix bridge. It confirms the scaffolding is not
mautrix-specific, and it is laid out differently enough to be worth having -
everything sits directly under the base path rather than in config/ and
data/ subdirectories, the owner and homeserver URL are passed on the command
line rather than through a config file, so the unit is where they can be
checked, and identd optionally binds host port 113.

matrix-base's matrix_server_fqn_* family moved into the shared context;
18 of the roles here read one of them.

Three roles now, three shapes - HTTP receiver, mautrix bridge, non-mautrix
bridge - and the scaffolding took no per-shape special-casing beyond each
role's own variables.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-27 18:02:53 +03:00

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/roles
scenario:
test_sequence:
- dependency
- cleanup
- destroy
- syntax
- create
- prepare
- converge
- idempotence
- verify
- cleanup
- destroy
verifier:
name: ansible