You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As noted in the release notes for v2.2.0, the flatten_fields_by_label option should default to false beginning with the next major version.
What this means
The fields key in the returned op_item dictionary will return a list instead of a nested dictionary. Fields with identical labels will not be de-duplicated. Users can opt to keep the behavior by setting the flatten_fields_by_label argument to yes
Example:
---
# Omitting `flatten_fields_by_label` => the `fields` key is a dict, non-unique field labels may overwrite each other
- name: Find and return Item details for "Dev-Database" onepassword.connect.item_info:
item: Dev-Databasevault: 2zbeu4smcibizsuxmyvhdh57b6# Set `flatten_fields_by_label` to false => fields are returned as a list, duplicate labels not removed
- name: Find and return Item details for "Dev-Database" - not flattenedonepassword.connect.item_info:
item: Dev-Databasevault: 2zbeu4smcibizsuxmyvhdh57b6flatten_fields_by_label: false
The text was updated successfully, but these errors were encountered:
edif2008
changed the title
field_info module: Change the flatten_fields_by_label default to false
[5] field_info module: Change the flatten_fields_by_label default to falseFeb 8, 2022
edif2008
changed the title
[5] field_info module: Change the flatten_fields_by_label default to false
field_info module: Change the flatten_fields_by_label default to falseMay 30, 2022
As noted in the release notes for v2.2.0, the
flatten_fields_by_label
option should default tofalse
beginning with the next major version.What this means
The
fields
key in the returnedop_item
dictionary will return a list instead of a nested dictionary. Fields with identical labels will not be de-duplicated. Users can opt to keep the behavior by setting theflatten_fields_by_label
argument toyes
Example:
The text was updated successfully, but these errors were encountered: