From 20c6766d2005b34a892b10842c2d1116eebc7a5d Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Wed, 4 Dec 2024 09:47:53 +0100 Subject: [PATCH] Committing DJs suggestion Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> --- .../edb-postgres-ai/console/estate/agent/install-agent.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx index 7ca575059e7..6b9c1ecd041 100644 --- a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx +++ b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx @@ -82,7 +82,7 @@ export BEACON_AGENT_ACCESS_KEY= export BEACON_AGENT_PROJECT_ID= ``` -Running the `beacon-agent setup` command creates a configuration file in the Beacon configuration directory using those environment variables. +These environment variables are used when you run the `beacon-agent setup` command to create a configuration file in the Beacon configuration directory. You also need to specify the Beacon configuration directory for storing the configuration file and the name of the configuration file to generate there. The `$HOME/.beacon/` file is one of the default locations which `beacon_agent` searches for `beacon_agent.yaml` when it starts. Using the `-file` flag tells the agent setup process to create its configuration file in a specific location.