From 94857d2f380789fa8fe7d5bbca503efad739d03e Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Wed, 12 Oct 2022 14:09:48 +1100 Subject: [PATCH] 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 --- playbooks/infra-prod/setup-keys.yaml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/playbooks/infra-prod/setup-keys.yaml b/playbooks/infra-prod/setup-keys.yaml index 23f53eb..f2cc21f 100644 --- a/playbooks/infra-prod/setup-keys.yaml +++ b/playbooks/infra-prod/setup-keys.yaml @@ -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: