Skip to content

Commit

Permalink
docs: Adding Bitwarden Secrets Manager backend
Browse files Browse the repository at this point in the history
Signed-off-by: Richard Cox <[email protected]>
  • Loading branch information
Khabi committed Aug 9, 2024
1 parent fd2ade0 commit 0741964
Showing 1 changed file with 46 additions and 1 deletion.
47 changes: 46 additions & 1 deletion docs/backends.md
Original file line number Diff line number Diff line change
Expand Up @@ -807,4 +807,49 @@ metadata:
type: Opaque
data:
password: <path:prod:my-secret#key>
```
```

### Bitwarden Secrets Manager

**Note**: The Bitwarden Secrets Manager backend does not support versioning.

##### Authentication

These are the parameters for Delinea:
```
AVP_TYPE: bitwardensecretsmanager
AVP_BITWARDEN_TOKEN: Bitwarden machine Account Token
Optional:
AVP_BITWARDEN_API_URL: API Endpoint URL (default: https://api.bitwarden.com)
AVP_BITWARDEN_IDENTITY_URL: Identity Endpoint URL (default: https://identity.bitwarden.com)
```
##### Examples
Examples assume that the secrets are not saved base64 encoded in the Secret Server.

###### Path Annotation

```yaml
kind: Secret
apiVersion: v1
metadata:
name: test-secret
annotations:
avp.kubernetes.io/path: "organization-id"
type: Opaque
stringData:
password: <secret-id>
```

###### Inline Path

```yaml
kind: Secret
apiVersion: v1
metadata:
name: test-secret
type: Opaque
data:
password: <path:organization-id#secret-id | base64encode>
```

0 comments on commit 0741964

Please sign in to comment.