Skip to content

Bitwarden: Fetching secrets matching a given name pattern returns keys #5185

@rbaumgar

Description

@rbaumgar

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/v1
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

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",
}

Kubernetes Version: v1.32.7 and external-secrets-0.19.2 (helm)

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.

Additional context
Find by name works fine with Bitwarden.
No more details at https://external-secrets.io/latest/provider/bitwarden-secrets-manager/#find-by-name
Same behavior as #5183, but now with community version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions