-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Bitwarden: Fetching secrets matching a given name pattern returns keys #5183
Copy link
Copy link
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
Describe the bug
When I try to fetch secrets matching a given name pattern, it returns the keys instead of the names.
Works fine when I am using Vault as external secret store.
To Reproduce
Steps to reproduce the behavior:
- create 3 secrets in Bitwarden Secrets Manager, name it "db_..."
- create ExternalSecret
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
name: find-by-tags
namespace: external-secrets
spec:
dataFrom:- find:
conversionStrategy: Default
decodingStrategy: None
name:
regexp: db_
refreshInterval: 1h
secretStoreRef:
kind: SecretStore
name: bitwarden-secretsmanager
target:
creationPolicy: Owner
deletionPolicy: Retain
name: secret-to-be-created
- find:
- get result
$ kubectl get secret secret-to-be-created -o jsonpath='{.data}'|jq
{
"2989464a-03c2-4ced-9fe2-b34400aca42d": "bG9jYWxob3N0OjEyMzQ1",
"98c18ddb-314e-463c-97c3-b34400ac6593": "dWFzZXJuYW1lMQ==",
"c917a790-76bc-49ca-b303-b34400ac8035": "UGFzc1dvcmQx",
} - OpenShift Version: 4.19.9, Kubernetes Version: v1.32.7 and External Secrets Operator for Red Hat OpenShift,
0.1.0 provided by Red Hat, Inc.
Expected behavior I would expect instead if the keys to get the secret's name (db_...) like I get when I am using Vault as the external secret store.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Type
Projects
Status
Done