From 3b1fa0a77ff528c8ef50b248ad62e40a4dc1e5f4 Mon Sep 17 00:00:00 2001 From: James Rasell Date: Tue, 7 Nov 2017 09:05:06 +0000 Subject: [PATCH] Update securing-nomad.html.md address flag example The `nomad node-status` command incorrectly used the `-addr` flag; whereas the correct flag key is `-address`. --- website/source/guides/securing-nomad.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/guides/securing-nomad.html.md b/website/source/guides/securing-nomad.html.md index 95c1508f8..84b8fa5b9 100644 --- a/website/source/guides/securing-nomad.html.md +++ b/website/source/guides/securing-nomad.html.md @@ -299,7 +299,7 @@ HTTPS. We can configure the local Nomad client to connect using TLS and specify our custom keys and certificates using the command line: ```shell -$ nomad node-status -ca-cert=nomad-ca.pem -client-cert=cli.pem -client-key=cli-key.pem -addr=https://127.0.0.1:4646 +$ nomad node-status -ca-cert=nomad-ca.pem -client-cert=cli.pem -client-key=cli-key.pem -address=https://127.0.0.1:4646 ``` This process can be cumbersome to type each time, so the Nomad CLI also