ADD: Organization and Collection to lookup.

[atta]

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

[atta]

@c0sco hey can we talk about this request and your opinion on it!?

[evrardjp]

Any interest in this?

[kemcon]

there is a bug in def get_custom_field(self, key, field, organizationId=None, collectionId=None):
the original def get_entry is always a string, but your def get_entry is json, so you dont need to json.loads(self.get_entry...

just do:

    def get_custom_field(self, key, field, organizationId=None, collectionId=None):
        data = self.get_entry(key, 'item', organizationId, collectionId)
        return next(x for x in data['fields'] if x['name'] == field)['value']

[atta]

there is a bug in def get_custom_field(self, key, field, organizationId=None, collectionId=None): the original def get_entry is always a string, but your def get_entry is json, so you dont need to json.loads(self.get_entry...

Thanks for the hint i did some work today toi change the way how custom fields and attachments work with Organization and Collection #25

[kemcon]

there is a bug in def get_custom_field(self, key, field, organizationId=None, collectionId=None): the original def get_entry is always a string, but your def get_entry is json, so you dont need to json.loads(self.get_entry...

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.