matrix-docker-ansible-deploy/roles/custom/matrix-appservice-draupnir-for-all/tasks/validate_config.yml

---

- name: Fail if required matrix-bot-draupnir variables are undefined
  ansible.builtin.fail:
    msg: "The `{{ item }}` variable must be defined and have a non-null value."
  with_items:
    - "matrix_appservice_draupnir_for_all_master_control_room_alias"
    - "matrix_bot_draupnir_container_network"
  when: "vars[item] == '' or vars[item] is none"
Add support for D4A/Draupnir For All to the playbook. (#3204) * Draupnir for all Role * Draupnir for all Documentation * Pin D4A to Develop until D4A patches are in a release. * Update D4A Docs to mention pros and cons of D4A mode compared to normal * Change Documentation to mention a fixed simpler provisioning flow. Use of /plain allows us to bypass the bugs encountered during the development of this role with clients attempting to escape our wildcards causing the grief that led to using curl. This reworded commit does still explain you can automatically inject stuff into the room if you wanted to. * Emphasise the State of D4A mode * Link to Draupnir-for-all docs and tweak the docs some * Link to Draupnir-for-all from Draupnir documentation page * Announce Draupnir-for-all --------- Co-authored-by: Slavi Pantaleev <slavi@devture.com> 2024-03-05 14:09:52 +00:00			`---`

			`- name: Fail if required matrix-bot-draupnir variables are undefined`
			`ansible.builtin.fail:`
			msg: "The `{{ item }}` variable must be defined and have a non-null value."
			`with_items:`
			`- "matrix_appservice_draupnir_for_all_master_control_room_alias"`
			`- "matrix_bot_draupnir_container_network"`
			`when: "vars[item] == '' or vars[item] is none"`