Ketesa v1.2.0 <https://github.com/etkecc/ketesa/releases/tag/v1.2.0>

roles/custom/matrix-ketesa/defaults/main.yml

@@ -27,7 +27,7 @@ matrix_ketesa_container_image_self_build: false
 matrix_ketesa_container_image_self_build_repo: "https://github.com/etkecc/ketesa.git"
 
 # renovate: datasource=docker depName=ghcr.io/etkecc/ketesa
-matrix_ketesa_version: v1.1.0
+matrix_ketesa_version: v1.2.0
 matrix_ketesa_container_image: "{{ matrix_ketesa_container_image_registry_prefix }}etkecc/ketesa:{{ matrix_ketesa_version }}"
 matrix_ketesa_container_image_registry_prefix: "{{ 'localhost/' if matrix_ketesa_container_image_self_build else matrix_ketesa_container_image_registry_prefix_upstream }}"
 matrix_ketesa_container_image_registry_prefix_upstream: "{{ matrix_ketesa_container_image_registry_prefix_upstream_default }}"
@@ -164,6 +164,7 @@ matrix_ketesa_path_prefix: /synapse-admin
 matrix_ketesa_configuration_default:
   restrictBaseUrl: "{{ matrix_ketesa_config_restrictBaseUrl }}"
   externalAuthProvider: "{{ matrix_ketesa_config_externalAuthProvider }}"
+  wellKnownDiscovery: "{{ matrix_ketesa_config_wellKnownDiscovery }}"
   corsCredentials: "{{ matrix_ketesa_config_corsCredentials }}"
   asManagedUsers: "{{ matrix_ketesa_config_asManagedUsers }}"
   menu: "{{ matrix_ketesa_config_menu }}"
@@ -202,6 +203,12 @@ matrix_ketesa_config_restrictBaseUrl: "{{ matrix_homeserver_url }}"  # noqa var-
 # enables a special compatibility mode that works better for external auth providers like LDAP, MAS, etc.
 matrix_ketesa_config_externalAuthProvider: false  # noqa var-naming
 
+# Control automatic URL canonicalization via /.well-known/matrix/client
+# Default: true (discovery enabled, per Matrix spec).
+# Set to false when the /_synapse/admin API is hosted on a separate domain not advertised in well-known (e.g. a VPN-only admin endpoint).
+# When disabled, MXID-based URL auto-fill uses the domain portion of the MXID directly without a well-known lookup.
+matrix_ketesa_config_wellKnownDiscovery: true  # noqa var-naming
+
 # Controls the corsCredentials configuration setting, which, if defined,
 # allows including credentials (cookies, authorization headers, or TLS client certificates) in requests
 # ref: https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch#including_credentials