mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-09-10 18:03:14 +00:00
Slavi PantaleevandClaude Opus 5
f320bfc93b
The second scenario, chosen to be a bridge rather than another HTTP component: bridges are roughly 40 of the 70 roles here, and validating the shape on role two is cheaper than discovering it on role forty. It found two things the first role could not. Bridges read a whole family of variables from outside themselves - matrix_bridges_relay_enabled, _encryption_enabled, _encryption_default, _msc4190_enabled, _self_sign_enabled, plus matrix_admin - all defined in matrix-base. Since every bridge reads them, they belong in shared context rather than in each bridge's scenario: molecule-shared/playbook-context.yml now carries them along with the identity and path variables the first scenario had inline. Note it is loaded through vars_files, which outranks inventory group_vars, so it is authoritative; a scenario that wants to prove one of these reaches the rendered configuration should say so explicitly. Appservices call /whoami while starting and refuse to run if the id returned is not the bot user they were configured as - mautrix-whatsapp exits 17 with "Unexpected user ID in whoami call". The shared stub now takes the id it should claim to be. Expect every bridge and bot to need this. What the scenario proves: the bridge starts and stays up, opens its appservice port, its rendered config and appservice registration carry the scenario's tokens and bot user, it created its sqlite database under the role's data path as the role's uid, and it runs the version the role pins. It does not bridge anything and never will. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
82 lines
3.1 KiB
YAML
82 lines
3.1 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-whatsapp-${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_whatsapp_container_network: mautrix-whatsapp-molecule
|
|
|
|
# The homeserver stub prepare.yml stands up. The bridge contacts it
|
|
# while starting; it is not a real homeserver and nothing is asserted
|
|
# about it.
|
|
matrix_bridge_mautrix_whatsapp_homeserver_address: http://matrix.molecule.local:8008
|
|
|
|
# sqlite keeps the scenario to one container. The role only requires a
|
|
# database hostname when the engine is postgres, and testing which
|
|
# database engine the bridge can talk to is not what this proves.
|
|
matrix_bridge_mautrix_whatsapp_database_engine: sqlite
|
|
|
|
# Appservice tokens. These are what the bridge and homeserver would
|
|
# authenticate to each other with; here they only have to reach the
|
|
# rendered configuration and the registration file.
|
|
matrix_bridge_mautrix_whatsapp_appservice_token: molecule_as_token_4f2a91
|
|
matrix_bridge_mautrix_whatsapp_homeserver_token: molecule_hs_token_9b3e77
|
|
|
|
# Deliberately different from the role's defaults, so verify.yml can
|
|
# tell what the role rendered apart from what the bridge would have
|
|
# defaulted to on its own.
|
|
matrix_bridge_mautrix_whatsapp_appservice_bot_username: molecule-whatsappbot
|
|
matrix_bridge_mautrix_whatsapp_homeserver_domain: molecule.local
|
|
|
|
# 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_mautrix_whatsapp_container_labels_traefik_enabled: false
|
|
|
|
# verify.yml runs as its own play, where role defaults are out of scope,
|
|
# so the paths it reads are pinned here as literals matching what the
|
|
# role derives from matrix_base_data_path.
|
|
matrix_bridge_mautrix_whatsapp_base_path: /matrix/mautrix-whatsapp
|
|
matrix_bridge_mautrix_whatsapp_config_path: /matrix/mautrix-whatsapp/config
|
|
matrix_bridge_mautrix_whatsapp_data_path: /matrix/mautrix-whatsapp/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/roles
|
|
scenario:
|
|
test_sequence:
|
|
- dependency
|
|
- cleanup
|
|
- destroy
|
|
- syntax
|
|
- create
|
|
- prepare
|
|
- converge
|
|
- idempotence
|
|
- verify
|
|
- cleanup
|
|
- destroy
|
|
verifier:
|
|
name: ansible
|