From bc69ef899a84bdc33ad790dee52107cb15eb0a9f Mon Sep 17 00:00:00 2001 From: Pavlos Karakalidis Date: Fri, 15 Sep 2023 20:02:18 +0300 Subject: [PATCH] docs(agent): clarify usage of exit_after_auth flag (#22954) Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --- website/content/docs/agent-and-proxy/agent/index.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/website/content/docs/agent-and-proxy/agent/index.mdx b/website/content/docs/agent-and-proxy/agent/index.mdx index 5551caf8a7..5fae0df525 100644 --- a/website/content/docs/agent-and-proxy/agent/index.mdx +++ b/website/content/docs/agent-and-proxy/agent/index.mdx @@ -126,7 +126,12 @@ These are the currently-available general configuration options: - `exit_after_auth` `(bool: false)` - If set to `true`, the agent will exit with code `0` after a single successful auth, where success means that a - token was retrieved and all sinks successfully wrote it + token was retrieved and all sinks successfully wrote it. If you have + `template` stanzas defined in your agent configuration, the agent + waits for the configured templates to render successfully before + exiting. If you use environment templates (`env_template` ) and set + `exit_after_auth` to true, Vault agent will not run the child processes + defined in your `exec` stanza. - `disable_idle_connections` `(string array: [])` - A list of strings that disables idle connections for various features in Vault Agent. Valid values include: `auto-auth`, `caching`, `proxying`, and `templating`. `proxying` configures this for the API proxy, which is