I want to implement this task 3 июля 2015 г. 15:00 пользователь "Sergey Kraynev" <skraynev at mirantis.com> написал: > Thank everyone for the good feedback. > If summarize all suggestions: > - I will continue add show as raw output (similar on clients show command > output) > - Also we decided to implement additional functional for "get_attr" > function, when it get only resource name and returns map with all > attributes (except "show"). > > About second one need volunteer :) > > Regards, > Sergey. > > On 3 July 2015 at 00:04, Steven Hardy <shardy at redhat.com> wrote: > >> On Fri, Jul 03, 2015 at 07:35:18AM +1200, Steve Baker wrote: >> > On 03/07/15 06:03, Randall Burt wrote: >> > >Maybe use "all" for all attributes in the schema and use "show" for >> the raw output from the service (as is done today for server and neutron >> stuff). >> > Instead of "all", how about allowing a special form of {get_attr: >> > [resource_name]} with no extra arguments to return a dict of all >> attributes? >> > This would be consistent with how extra arguments traverse attribute >> data. >> >> +1 >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150703/cdbdc5ff/attachment.html>