Files
matrix-docker-ansible-deploy/roles/custom/matrix-bridge-mautrix-bluesky/molecule/default/molecule.yml
T

96 lines
4.3 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-bluesky-${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_bluesky_container_network: mautrix-bluesky-molecule
# The stub is not a real homeserver, and the scenario carries no Bluesky account or
# credentials. An idle, logged-out bridge is the intended third-party boundary.
matrix_bridge_mautrix_bluesky_homeserver_address: http://matrix.molecule.local:8008
matrix_bridge_mautrix_bluesky_homeserver_domain: molecule.local
# Postgres is this role's only database engine. The non-default identity makes schema
# creation evidence that the role composed and delivered the scenario connection URI.
matrix_bridge_mautrix_bluesky_database_hostname: matrix-postgres-molecule
matrix_bridge_mautrix_bluesky_database_name: molecule_bluesky
matrix_bridge_mautrix_bluesky_database_username: molecule_bluesky
matrix_bridge_mautrix_bluesky_database_password: molecule_pg_password_74b0e2
# Test-only fixtures which must reach config.yaml and registration.yaml.
matrix_bridge_mautrix_bluesky_appservice_token: molecule_bluesky_as_token_1f27ac
matrix_bridge_mautrix_bluesky_homeserver_token: molecule_bluesky_hs_token_91c0d8
# Each value differs from the role default, allowing parsed checks to prove rendering.
matrix_bridge_mautrix_bluesky_appservice_bot_username: molecule-blueskybot
matrix_bridge_mautrix_bluesky_appservice_bot_displayname: Molecule Bluesky Bot
matrix_bridge_mautrix_bluesky_appservice_bot_avatar: mxc://molecule.local/blueskyAvatarFixture
matrix_bridge_mautrix_bluesky_network_displayname_template: "{% raw %}{{ .Username }}{% endraw %} via Molecule"
matrix_bridge_mautrix_bluesky_bridge_command_prefix: "!molecule-bluesky"
matrix_bridge_mautrix_bluesky_bridge_permissions:
"*": relay
molecule.local: admin
matrix_bridge_mautrix_bluesky_matrix_federate_rooms: false
matrix_bridge_mautrix_bluesky_backfill_enabled: false
matrix_bridge_mautrix_bluesky_backfill_max_initial_messages: 23
matrix_bridge_mautrix_bluesky_backfill_max_catchup_messages: 37
matrix_bridge_mautrix_bluesky_provisioning_shared_secret: molecule_provisioning_secret_2f018a
matrix_bridge_mautrix_bluesky_logging_level: info
# Traefik is not started. These settings exercise the public address consumed by the
# bridge and the route labels consumed by Docker.
matrix_bridge_mautrix_bluesky_exposure_enabled: true
matrix_bridge_mautrix_bluesky_exposure_hostname: bluesky-api.molecule.local
matrix_bridge_mautrix_bluesky_exposure_path_prefix: /bridges/bluesky-api
matrix_bridge_mautrix_bluesky_scheme: http
matrix_bridge_mautrix_bluesky_container_labels_traefik_entrypoints: web
matrix_bridge_mautrix_bluesky_container_labels_additional_labels: |
molecule.bluesky.coverage=enabled
# verify.yml is a separate play, where role defaults are out of scope.
matrix_bridge_mautrix_bluesky_base_path: /matrix/mautrix-bluesky
matrix_bridge_mautrix_bluesky_config_path: /matrix/mautrix-bluesky/config
matrix_bridge_mautrix_bluesky_data_path: /matrix/mautrix-bluesky/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