-
Notifications
You must be signed in to change notification settings - Fork 44
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: Organization and Collection to lookup. #22
base: master
Are you sure you want to change the base?
Conversation
This will enable lager bitwarden deployments to make use of collections. In order to have the same key stored with different values, for multiple environments
@c0sco hey can we talk about this request and your opinion on it!? |
Any interest in this? |
there is a bug in def get_custom_field(self, key, field, organizationId=None, collectionId=None): just do:
|
[STOR-368] add attachments and customfields in ansible-bitwarden
Thanks for the hint i did some work today toi change the way how custom fields and attachments work with Organization and Collection #25 |
your welcome. i started my own fork and added a lot, but with breaking changed. especially i got rid of custom value and now one can read every single value or list from the item-json. the custom values are available with "fields.valuename", but "id" ist also possible and organziation id and collection id is available too and all is working always with the names instead of the ids. |
This will enable lager bitwarden deployments to make use of collections.
In order to have the same key stored with different values,
for multiple environments