From 226eb6cb05cc918a3ce222fffd11deb6585fedc4 Mon Sep 17 00:00:00 2001 From: Ian Fijolek Date: Tue, 30 Aug 2022 15:15:10 -0700 Subject: [PATCH] Have nomad talk to vault over loopback --- setup-cluster.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/setup-cluster.yml b/setup-cluster.yml index 1d34cc4..b9b07ac 100644 --- a/setup-cluster.yml +++ b/setup-cluster.yml @@ -377,7 +377,9 @@ # until Nomad has started. Could maybe figure out if ACLs have been set up and leave # these out until the later play, maybe just bootstrap the nomad-cluster role in Vault # befor Nomad is set up - nomad_vault_address: "http://vault.service.consul:8200" + # nomad_vault_address: "http://vault.service.consul:8200" + # Only talk to local Vault for now because it doesn't have HTTPS + nomad_vault_address: "http://127.0.0.1:8200" nomad_vault_create_from_role: "nomad-cluster" # TODO: Probably want to restict this to a narrower scoped token nomad_vault_enabled: "{{ root_token is defined }}"