Comment 4 for bug 1705755

In regards to the "gap" herein specifically with neutron support in OSC; resource attribute extensions today have the following problems:
- They must redefine the entry points they want to override. For example [1][2]. While this works sometimes, there's no guarantees as to which entry point will be loaded first/last.
- They must duplicate the "base action" code since there's no way to extend them in base OSC. For example [3]. Ideally extensions can reuse OSCs functionality only providing the difference they need. Without such constructs the code in the client extension can get out of sync with the base OSC (since it duplicates code).
- There's still no way to add attributes to collect/display in the SDK resource. Thus even if the above things are done, the attribute(s) are not collected/shown in the OSC CLI output.

[1] https://github.com/openstack/vmware-nsx/blob/master/setup.cfg#L69
[2] https://github.com/openstack/python-openstackclient/blob/master/setup.cfg#L456
[3] https://github.com/openstack/vmware-nsx/blob/master/vmware_nsx/osc/v2/security_group.py#L80