ansible/inventory/group_vars/relvalconsumer

# This var should never be set for more than one machine
# this one probably shouldn't either
relvalconsumer_bugzilla_api_key: "{{ prod_relvalconsumer_bugzilla_secret_api_key }}"
relvalconsumer_env_suffix:
relvalconsumer_prod: true
Add a relvalconsumer role, run it on openQA servers for now relvalconsumer is the fedmsg consumer bot that creates Wikitcms release validation test events. Up till now it's just been running on one of my personal boxes; we should really move it to infra. Run it on the openQA servers for now, as there's nowhere more obviously correct, and I have root access there to fix problems. We add new inventory groups because it's really important that there be exactly one (no more, no less) production consumer at any given time. I don't want to just use the 'openqa' group for this because it's vaguely possible it could contain more than one host in future, and we really wouldn't want that to result in there being two production relvalconsumers running. 2016-11-30 13:21:24 -08:00			`# This var should never be set for more than one machine`
relvalconsumer: handle reporting image size bugs to Bugzilla This relies on changes in relvalconsumer itself and relval. Signed-off-by: Adam Williamson <awilliam@redhat.com> 2019-09-19 13:00:09 -07:00			`# this one probably shouldn't either`
			`relvalconsumer_bugzilla_api_key: "{{ prod_relvalconsumer_bugzilla_secret_api_key }}"`
Convert relvalconsumer to fedora-messaging Following the basic scheme I set up for fedora_openqa, hope it's all right... Signed-off-by: Adam Williamson <awilliam@redhat.com> 2019-06-18 16:40:07 -07:00			`relvalconsumer_env_suffix:`
Inventory group/host variables: Sort yaml 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> 2021-11-16 13:27:57 -08:00			`relvalconsumer_prod: true`