mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-09-23 08:10:10 +00:00
Slavi PantaleevandClaude Opus 5
c447e1528b
They were hard-wrapped at 80 characters, broke mid-parenthesis, and spent lines restating what the code below them does. Rewrapped at natural boundaries instead, with the narration dropped and only the reasons, gotchas and surprises kept. Section dividers stay - they delineate long plays rather than narrate them. Comments only; no scenario behaviour changes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SEH3vxYSQ5SV4N5z61eyGT
98 lines
4.5 KiB
YAML
98 lines
4.5 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: mautrix-meta-messenger-${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_mautrix_meta_messenger_container_network: mautrix-meta-messenger-molecule
|
|
|
|
# The stub prepare.yml stands up. Not a real homeserver, and nothing is asserted
|
|
# about it.
|
|
matrix_bridge_mautrix_meta_messenger_homeserver_address: http://matrix.molecule.local:8008
|
|
matrix_bridge_mautrix_meta_messenger_homeserver_domain: molecule.local
|
|
|
|
# sqlite keeps the scenario to one container. Which database engine the bridge can
|
|
# talk to is not what this proves.
|
|
matrix_bridge_mautrix_meta_messenger_database_engine: sqlite3-fk-wal
|
|
|
|
# The URI the role derives is deliberately NOT overridden here. It used to build
|
|
# `sqlite:///` + the in-container path, which go-sqlite3 takes as a plain filename
|
|
# rather than parsing as a URL, so the bridge died at startup. This scenario caught
|
|
# that, and leaving the role's own value in place is what keeps it caught.
|
|
|
|
# Here these only have to reach the rendered configuration and the registration.
|
|
matrix_bridge_mautrix_meta_messenger_appservice_token: molecule_meta_as_token_5c81de
|
|
matrix_bridge_mautrix_meta_messenger_homeserver_token: molecule_meta_hs_token_a70f24
|
|
|
|
# What makes this role family unusual: one upstream codebase serves several Meta
|
|
# networks, and this variable picks which. It reaches the rendered configuration in
|
|
# four places at once - appservice id, ghost username prefix, bot displayname and the
|
|
# bridge's `tor` switch - so a value other than the role's default is what tells
|
|
# verify.yml the role propagated the choice rather than everything agreeing by accident.
|
|
#
|
|
# `facebook-tor` is used because it is the only mode that also flips a boolean.
|
|
# Nothing logs in during the scenario, so the bridge never connects to Meta.
|
|
matrix_bridge_mautrix_meta_messenger_meta_mode: facebook-tor
|
|
|
|
# Different from the role's defaults and from what the bridge would pick on its own,
|
|
# so verify.yml can tell what the role rendered apart from a coincidence.
|
|
matrix_bridge_mautrix_meta_messenger_appservice_username: molecule-metabot
|
|
matrix_bridge_mautrix_meta_messenger_bridge_command_prefix: "!molecule-meta"
|
|
matrix_bridge_mautrix_meta_messenger_bridge_displayname_suffix: "(Molecule)"
|
|
matrix_bridge_mautrix_meta_messenger_logging_min_level: debug
|
|
|
|
# Traefik is not deployed here, so nothing routes to it. What is tested is that the
|
|
# role turns these three variables into both the container's Traefik labels and the
|
|
# `appservice.public_address` the bridge itself reads.
|
|
matrix_bridge_mautrix_meta_messenger_exposure_enabled: true
|
|
matrix_bridge_mautrix_meta_messenger_exposure_hostname: bridges.molecule.local
|
|
matrix_bridge_mautrix_meta_messenger_exposure_path_prefix: /bridges/meta-messenger
|
|
matrix_bridge_mautrix_meta_messenger_scheme: https
|
|
|
|
# verify.yml runs as its own play, where the role's defaults are out of scope,
|
|
# so the paths it reads are pinned here to match what the role derives.
|
|
matrix_bridge_mautrix_meta_messenger_base_path: /matrix/mautrix-meta-messenger
|
|
matrix_bridge_mautrix_meta_messenger_config_path: /matrix/mautrix-meta-messenger/config
|
|
matrix_bridge_mautrix_meta_messenger_data_path: /matrix/mautrix-meta-messenger/data
|
|
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
|