-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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.
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
Add support to Bitwarden Lookup for filtering results by collection id #5849
Comments
psalkowski
added a commit
to psalkowski/community.general
that referenced
this issue
Jan 17, 2023
Files identified in the description: If these files are incorrect, please update the |
ansibullbot
added
feature
This issue/PR relates to a feature request
lookup
lookup plugin
plugins
plugin (any type)
labels
Jan 17, 2023
psalkowski
added a commit
to psalkowski/community.general
that referenced
this issue
Jan 17, 2023
psalkowski
added a commit
to psalkowski/community.general
that referenced
this issue
Jan 18, 2023
psalkowski
added a commit
to psalkowski/community.general
that referenced
this issue
Jan 18, 2023
psalkowski
added a commit
to psalkowski/community.general
that referenced
this issue
Jan 26, 2023
psalkowski
added a commit
to psalkowski/community.general
that referenced
this issue
Jan 26, 2023
felixfontein
pushed a commit
that referenced
this issue
Jan 28, 2023
…5849) (#5851) * Add support to Bitwarden Lookup for filtering results by collection id (#5849) * Debug * Add support to Bitwarden Lookup for filtering results by collection id (#5849) * Update comments * Fix blank line issue * Fix unit tests for bitwarden lookup plugin. Add changelog fragment file. * Change collectionId to collection_id parameter on bitwarden plugin * Fix collection id parameter name when used in bw cli
patchback bot
pushed a commit
that referenced
this issue
Jan 28, 2023
…5849) (#5851) * Add support to Bitwarden Lookup for filtering results by collection id (#5849) * Debug * Add support to Bitwarden Lookup for filtering results by collection id (#5849) * Update comments * Fix blank line issue * Fix unit tests for bitwarden lookup plugin. Add changelog fragment file. * Change collectionId to collection_id parameter on bitwarden plugin * Fix collection id parameter name when used in bw cli (cherry picked from commit 7b8b73f)
felixfontein
pushed a commit
that referenced
this issue
Jan 28, 2023
…p for filtering results by collection (#5849) (#5904) Add support to Bitwarden Lookup for filtering results by collection (#5849) (#5851) * Add support to Bitwarden Lookup for filtering results by collection id (#5849) * Debug * Add support to Bitwarden Lookup for filtering results by collection id (#5849) * Update comments * Fix blank line issue * Fix unit tests for bitwarden lookup plugin. Add changelog fragment file. * Change collectionId to collection_id parameter on bitwarden plugin * Fix collection id parameter name when used in bw cli (cherry picked from commit 7b8b73f) Co-authored-by: Piotr <skc.peter@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Bitwarden allow to use collections for storing data. In some cases, to simplify CI/CD process with ansible, users may setup collections per environment (like dev, staging, production). They will use the same names for vault items, but stores in different collections. At the end, in CI/CD you can setup one ENV variable that mention the collection id and pass it to ansible. Otherwise, you will have to have unique vault item names.
Of course collection id should be optional.
Issue Type
Feature Idea
Component Name
lookup/bitwarden
Additional Information
Code of Conduct
The text was updated successfully, but these errors were encountered: