bitwarden / bitwarden/clients

CLI Performance concerns

Open
#2,741 38 comments 31 reactions 0 assignees View on GitHub
bug cli
Dominant language
TypeScript
Stars
13.8k
Forks
2k
Avg merge
3d 9h
Merged PRs (30d)
397

Description

We are in the move to switch from LastPass.

The lastpass cli is not supported and isn’t reliable to create or retrieve secrets anymore.

We use secrets management extensively in our devops process through an ansible lookup plugin.

So far, we didn’t get any issue while retrieving our hundreds of secrets from Bitwarden when running our ansible playbooks.

However we have huge performance issues. The retrieval of our secrets takes several minutes and considerably slows down the execution of ansible playbooks.

As ansible parses multiples times the variables files, we needed to use a caching lookup plugin to have a first acceptable performance solution.

But this solution is not well suited for secrets as it creates a plain text file with secrets on our machine.

Is there some workarounds to improve performance ?

I have currently imported around 100 secrets, I guess this is 5% of our lastpass secrets. Will I have more performance troubles when my vault will be entirely migrated ?

Thanks for your insights

Contributor guide

Open the contributing guide

Research direction

No file, test, or CLI entry point is named. Start by tracing the Bitwarden retrieval path used by the Ansible lookup plugin and measure repeated retrievals during playbook parsing; done means identifying a supported faster approach that avoids writing secrets to a plaintext cache.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible
Domain
cli, devops, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.