Skip to content
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

chore: remove --gcloud-auth from README #2354

Merged
merged 1 commit into from
Dec 19, 2024
Merged

chore: remove --gcloud-auth from README #2354

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
5 changes: 2 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,11 +211,10 @@ account, the VM must have at least the `sqlservice.admin` API scope (i.e.,
must have the SQL Admin API enabled. The default service account must also have
at least writer or editor privileges to any projects of target SQL instances.

The Proxy also supports three flags related to credentials:
The Proxy also supports two flags related to credentials:

- `--token` to use an OAuth2 token
- `--credentials-file` to use a service account key file
- `--gcloud-auth` to use the Gcloud user's credentials (local development only)

### Basic Usage

Expand All @@ -231,7 +230,7 @@ To start the Proxy, use:
```

The Proxy will automatically detect the default database engine's port and start
a corresponding listener. Production deployments should use the --port flag to
a corresponding listener. Production deployments should use the `--port` flag to
reduce startup time.

The Proxy supports multiple instances:
Expand Down
Loading