setup-keys: add bridge node to "bastion" group

This puts the dynamically added bridge node in the "bastion" group.
This way the production jobs can refer to the generic group name, and
be abstracted from the actual hostname.

Change-Id: Ie35f3f003f21472be2ca87ab962141d17fc2a7b6
This commit is contained in:
Ian Wienand 2022-10-12 14:09:48 +11:00
parent accdc49eef
commit 94857d2f38
No known key found for this signature in database
1 changed files with 5 additions and 0 deletions

View File

@ -12,6 +12,11 @@
ansible_port: 22
# Port 19885 is firewalled
zuul_console_disabled: true
# Note this is the only host in the bastion group. The playbooks
# are written to refer to "bastion[0]" rather than the hostname
# directly, so we can swap the hostname more easily.
groups:
- bastion
- name: Add bridge.o.o hostkey to known hosts
known_hosts: