mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-09-13 19:33:13 +00:00
Slavi PantaleevandClaude Opus 5
85f80a3c7e
`group_vars/matrix_servers` selects postgres whenever postgres is enabled, which is the default, so postgres is what essentially every deployment runs. The scenarios were testing sqlite - a path almost nobody is on. How little that path is used is not a guess: the mautrix-meta bridges could not start at all under sqlite, and nobody reported it. Testing the engine users are actually on is worth more than keeping coverage of the one they are not, so no scenario is left behind on sqlite. Four of the eight scenarios have a database and are converted; the other four have none and are untouched. molecule-shared/tasks/postgres.yml stands Postgres up on the scenario's network, with the data directory on a tmpfs since it is thrown away with the container. The image is pinned at the major the postgres role deploys to new installations and left to Renovate: when a new major lands, the PR bumping that pin runs every scenario against it, which is the earliest warning we get that a component does not cope. Each scenario gives its database and user names that differ from the role's defaults, so the component reaching the database proves the role built its connection string out of them. The assertions moved from "a file appeared at the path we configured" to "these tables exist", which is strictly stronger: tables can only appear once the component has resolved the hostname, authenticated with the credentials the role rendered, and run its migrations to completion. Costs about 10 seconds per affected scenario (115s to 125s locally for mautrix-whatsapp), on jobs that run in parallel. Gotcha worth recording: since Postgres 18 the image puts PGDATA in a versioned subdirectory and refuses to start if it finds a mount at the old /var/lib/postgresql/data, so the tmpfs is mounted at /var/lib/postgresql. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SEH3vxYSQ5SV4N5z61eyGT
85 lines
3.5 KiB
YAML
85 lines
3.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-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 stub prepare.yml stands up. Not a real homeserver, and nothing is asserted
|
|
# about it.
|
|
matrix_bridge_mautrix_whatsapp_homeserver_address: http://matrix.molecule.local:8008
|
|
|
|
# Postgres, because that is what `group_vars/matrix_servers` selects whenever postgres
|
|
# is enabled - which is the default, so it is what essentially every real deployment
|
|
# runs. prepare.yml stands one up. The password differs from the role's default, so
|
|
# reaching the database at all means the role's connection string was built from these.
|
|
# Database name and user differ from the role's defaults, so the bridge reaching the
|
|
# database at all proves the role built its connection string out of these rather
|
|
# than out of anything it would have picked on its own. prepare.yml creates them.
|
|
matrix_bridge_mautrix_whatsapp_database_engine: postgres
|
|
matrix_bridge_mautrix_whatsapp_database_hostname: matrix-postgres-molecule
|
|
matrix_bridge_mautrix_whatsapp_database_name: molecule_whatsapp
|
|
matrix_bridge_mautrix_whatsapp_database_username: molecule_whatsapp
|
|
matrix_bridge_mautrix_whatsapp_database_password: molecule_pg_password_5e8c21
|
|
|
|
# Here these only have to reach the rendered configuration and the registration.
|
|
matrix_bridge_mautrix_whatsapp_appservice_token: molecule_as_token_4f2a91
|
|
matrix_bridge_mautrix_whatsapp_homeserver_token: molecule_hs_token_9b3e77
|
|
|
|
# Different from the role's defaults, so verify.yml can tell what the role rendered
|
|
# apart from what the bridge would have chosen.
|
|
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 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_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_HOME:-~/.ansible}/roles
|
|
scenario:
|
|
test_sequence:
|
|
- dependency
|
|
- cleanup
|
|
- destroy
|
|
- syntax
|
|
- create
|
|
- prepare
|
|
- converge
|
|
- idempotence
|
|
- verify
|
|
- cleanup
|
|
- destroy
|
|
verifier:
|
|
name: ansible
|