matrix-docker-ansible-deploy/roles/custom/matrix-bot-matrix-reminder-bot/molecule/default/molecule.yml

# 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: matrix-reminder-bot-${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_bot_matrix_reminder_bot_container_network: matrix-reminder-bot-molecule

        # Unlike the bridges, this bot is not an appservice: it logs in as an ordinary user
        # with a password. The stub answers /_matrix/client/v3/login with an access token,
        # which is all the bot needs to reach its sync loop.
        matrix_bot_matrix_reminder_bot_matrix_homeserver_url: http://matrix.molecule.local:8008

        # Different from the role's default localpart, so verify.yml can tell what the role
        # rendered apart from what it would have rendered anyway.
        matrix_bot_matrix_reminder_bot_matrix_user_id_localpart: molecule.reminder-bot
        matrix_bot_matrix_reminder_bot_matrix_user_password: molecule_bot_password_4f2a91

        # The role has no default here and refuses to run without one. Also different from the
        # bot's own fallback, and it reaches the container twice: the config file and TZ.
        matrix_bot_matrix_reminder_bot_reminders_timezone: Europe/Sofia

        # The role and the bot both default to `!`.
        matrix_bot_matrix_reminder_bot_command_prefix: "%%"

        # Both lists default to off with no entries, so turning them on exercises the
        # `_auto + _custom` composition.
        matrix_bot_matrix_reminder_bot_allowlist_enabled: true
        matrix_bot_matrix_reminder_bot_allowlist_regexes_custom:
          - "@molecule-allowed:molecule.local"
        matrix_bot_matrix_reminder_bot_blocklist_enabled: true
        matrix_bot_matrix_reminder_bot_blocklist_regexes_custom:
          - ".*:blocked.molecule.local"

        # The device name is hardcoded in the role's template, so overriding it is only
        # possible through the extension mechanism - which tests that merge too.
        matrix_bot_matrix_reminder_bot_configuration_extension_yaml: |
          matrix:
            device_name: Molecule Reminder Bot

        # 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. Name and user differ from the role's defaults, so
        # reaching the database proves the role built its connection string out of these.
        matrix_bot_matrix_reminder_bot_database_engine: postgres
        matrix_bot_matrix_reminder_bot_database_hostname: matrix-postgres-molecule
        matrix_bot_matrix_reminder_bot_database_name: molecule_reminder_bot
        matrix_bot_matrix_reminder_bot_database_username: molecule_reminder_bot
        matrix_bot_matrix_reminder_bot_database_password: molecule_pg_password_3c9b02

        # 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_bot_matrix_reminder_bot_base_path: /matrix/matrix-reminder-bot
        matrix_bot_matrix_reminder_bot_config_path: /matrix/matrix-reminder-bot/config
        matrix_bot_matrix_reminder_bot_data_path: /matrix/matrix-reminder-bot/data
        matrix_bot_matrix_reminder_bot_data_store_path: /matrix/matrix-reminder-bot/data/store
  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