From 362e43b90ef7d2c7d85c1dbb4ee2400339e0a21e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Se=C3=A1n=20Whelan?= Date: Wed, 8 Apr 2026 14:16:38 +0100 Subject: [PATCH] docs: fix FLOW_AUTH_TOKEN to reference refresh token instead of access token --- site/docs/guides/flowctl/ci-cd.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/site/docs/guides/flowctl/ci-cd.md b/site/docs/guides/flowctl/ci-cd.md index 99c3a5ab230..5cd2595cf28 100644 --- a/site/docs/guides/flowctl/ci-cd.md +++ b/site/docs/guides/flowctl/ci-cd.md @@ -19,11 +19,11 @@ During development, you can locally create, manage, and test your resources befo Before creating these resources, you will need: * An [Estuary account](https://dashboard.estuary.dev/register) * `flowctl` [installed](../get-started-with-flowctl.md) on your machine -* An Estuary [access token](../how_to_generate_refresh_token.md) +* An Estuary [refresh token](../how_to_generate_refresh_token.md) You can authenticate your `flowctl` session in one of two ways: -* Set the `FLOW_AUTH_TOKEN` environment variable to your Estuary access token. This is the recommended way to handle a CI or automation setup. +* Set the `FLOW_AUTH_TOKEN` environment variable to your Estuary refresh token. This is the recommended way to handle a CI or automation setup. * Or run the `flowctl auth login` command and paste in your token. This is handy for local development.