Skip to content

docs: remove Custom API Endpoint secret manager integration #920

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

Merged
d-bytebase merged 1 commit into from
Oct 24, 2025
Merged

docs: remove Custom API Endpoint secret manager integration #920

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
14 changes: 0 additions & 14 deletions mintlify/get-started/connect/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,6 @@ Never store database passwords in Bytebase. Use your existing secret manager for
- **[AWS Secrets Manager](/get-started/connect/aws#aws-secrets-manager)** - For AWS deployments
- **[GCP Secret Manager](/get-started/connect/gcp#gcp-secret-manager)** - For GCP deployments
- **HashiCorp Vault** - Enterprise secret management
- **Custom API Endpoint** - Custom integrations

#### HashiCorp Vault

Expand All @@ -118,19 +117,6 @@ Requires Vault KV v2 engine
2. Choose authentication: Token or AppRole
3. Specify secret location

#### Custom API Endpoint

**Endpoint Format:** `{{http://example.com/secrets/mydbkey}}`

**Expected Response:**
```json
{
"payload": {
"data": "base64_encoded_password"
}
}
```

## Instance Management

Configure instance-level settings to optimize how Bytebase interacts with your databases.
Expand Down