From d21351f2456cfb0c999301b5070b3e4a61539dde Mon Sep 17 00:00:00 2001 From: hc-github-team-secure-vault-core <82990506+hc-github-team-secure-vault-core@users.noreply.github.com> Date: Fri, 30 Jun 2023 13:48:20 -0400 Subject: [PATCH] backport of commit 325233ea7dba833e987909b21af547d0933751e3 (#21519) Co-authored-by: Christophe Deliens --- changelog/21466.txt | 3 +++ command/agent_generate_config.go | 4 ++-- 2 files changed, 5 insertions(+), 2 deletions(-) create mode 100644 changelog/21466.txt diff --git a/changelog/21466.txt b/changelog/21466.txt new file mode 100644 index 000000000..94d0af99a --- /dev/null +++ b/changelog/21466.txt @@ -0,0 +1,3 @@ +```release-note:bug +agent: Fix "generate-config" command documentation URL +``` diff --git a/command/agent_generate_config.go b/command/agent_generate_config.go index 4c25b443d..9fa660af3 100644 --- a/command/agent_generate_config.go +++ b/command/agent_generate_config.go @@ -61,8 +61,8 @@ Usage: vault agent generate-config [options] [path/to/config.hcl] In addition to env_template entries, the command generates an 'auto_auth' section with 'token_file' authentication method. While this method is very convenient for local testing, it should NOT be used in production. Please - see https://developer.hashicorp.com/vault/docs/agentandproxy/autoauth for - a list of production-ready auto_auth methods that you can use instead. + see https://developer.hashicorp.com/vault/docs/agent-and-proxy/autoauth/methods + for a list of production-ready auto_auth methods that you can use instead. By default, the file will be generated in the local directory as 'agent.hcl' unless a path is specified as an argument.