Skip to content

docs: fix token usage instructions with FLOW_AUTH_TOKEN #2841

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
SeanWhelan wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

docs: fix token usage instructions with FLOW_AUTH_TOKEN #2841

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions site/docs/guides/flowctl/ci-cd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading