infrastructure/ansible
2
0
Fork 0
Code Pull requests 7 Activity Actions
ansible/inventory/group_vars/checkcompose_stg

6 lines
221 B
Text
Raw Normal View History

check-compose: convert to fedora-messaging Following the patterns from openQA and relvalconsumer. Just one to go after this! Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-06-19 15:44:46 -07:00
checkcompose_env: staging
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
checkcompose_env_suffix: .stg
check-compose: convert to fedora-messaging Following the patterns from openQA and relvalconsumer. Just one to go after this! Signed-off-by: Adam Williamson <awilliam@redhat.com>
2019-06-19 15:44:46 -07:00
checkcompose_greenwaveurl: https://greenwave-web-greenwave.app.os.stg.fedoraproject.org
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
checkcompose_prod: false
checkcompose_url: "https://{{ external_hostname }}"
Copy permalink