I think the idea for extras was to add custom fields, but not allow the entire "extras" json blob to be searchable so that resources in keystone wouldn't become data stores. You can already update these fields by their attribute name (I know "email" is a popular one for Users), but searching would require some discussion and I think the current consensus is to avoid doing that. If you are needing to search projects by some field, there is a current spec that is WIP for Queens to add "tags" to projects. [0]
[0] https://specs.openstack.org/openstack/keystone- specs/specs/keystone/queens/project-tags.html ** Changed in: keystone Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1714179 Title: keystone project can not update or search extra field Status in OpenStack Identity (keystone): Invalid Bug description: keystone project can not update or search extra field To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1714179/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
