580cd252c5
This was done using yq ( https://mikefarah.gitbook.io/yq/operators/sort-keys ) Doing things this way makes it much easier to see if a variable is set in a file or if two hosts differ in what variables they set. Hopefully we can keep things sorted moving forward. Basically this means just sort a-z anything you add to any host or group vaiable and it will be in the right place. Additionally, this enforces 'normal' intent rules for all the variable files which we should also try and obey. 2 spaces for first level, 3 for next, etc. When in doubt you can run yq on it. This should cause NO actual vairable changes, it's all just readability fixing for humans, ansible parses it exactly the same. Signed-off-by: Kevin Fenzi <kevin@scrye.com>
15 lines
974 B
Text
15 lines
974 B
Text
# we need this for our fedora-messaging consumer as it is not allowed
|
|
# to create queues on the infra AMQP broker, by broker config
|
|
fedora_nightlies_amqp_cacert: /etc/fedora-messaging/cacert.pem
|
|
fedora_nightlies_amqp_cert: /etc/pki/fedora-messaging/openqa-cert.pem
|
|
fedora_nightlies_amqp_data_file: /usr/share/openqa/public/nightlies.json
|
|
fedora_nightlies_amqp_html_file: /usr/share/openqa/public/nightlies.html
|
|
fedora_nightlies_amqp_key: /etc/pki/fedora-messaging/openqa-key.pem
|
|
# fedora-messaging email error reporting settings
|
|
fedora_nightlies_amqp_mailto: ["adamwill@fedoraproject.org"]
|
|
fedora_nightlies_amqp_passive: true
|
|
fedora_nightlies_amqp_queue: "openqa_fedora_nightlies"
|
|
fedora_nightlies_amqp_routing_keys: ["org.fedoraproject.prod.openqa.job.done", "org.fedoraproject.prod.pungi.compose.status.change"]
|
|
fedora_nightlies_amqp_smtp: bastion
|
|
# fedora-messaging job scheduler settings
|
|
fedora_nightlies_amqp_url: "amqps://openqa:@rabbitmq.fedoraproject.org/%2Fpubsub"
|