瀏覽代碼

Properly serialize some ma1sd configuration values

We've had a report of the `connection` value getting cut off,
supposedly because it contains something that breaks off the string.

Using `|to_json` takes care of it.
pull/745/head
Slavi Pantaleev 5 年之前
父節點
當前提交
7372480e95
共有 1 個檔案被更改,包括 4 行新增4 行删除
  1. +4
    -4
      roles/matrix-ma1sd/templates/ma1sd.yaml.j2

+ 4
- 4
roles/matrix-ma1sd/templates/ma1sd.yaml.j2 查看文件

@@ -73,10 +73,10 @@ hashing:
- none # the same as v1 bulk lookup - none # the same as v1 bulk lookup
- sha256 # hash the 3PID and pepper. - sha256 # hash the 3PID and pepper.
delay: 2m # how often hashes will be updated if rotation policy = per_seconds (default is 10s) delay: 2m # how often hashes will be updated if rotation policy = per_seconds (default is 10s)
requests: 10
requests: 10
{% endif %} {% endif %}


synapseSql: synapseSql:
enabled: {{ matrix_ma1sd_synapsesql_enabled }}
type: {{ matrix_ma1sd_synapsesql_type }}
connection: {{ matrix_ma1sd_synapsesql_connection }}
enabled: {{ matrix_ma1sd_synapsesql_enabled|to_json }}
type: {{ matrix_ma1sd_synapsesql_type|to_json }}
connection: {{ matrix_ma1sd_synapsesql_connection|to_json }}

Loading…
取消
儲存