Hi Mohammed,
The reason I think is that taas was not a Neutron Stadium project for years and the team obviously not allowed
CLI code to be merged to python-neutronclient or to python-openstackclient, and the cheapest solution at that time
was to have it in the server repository.
The x/networking-l2gw has similar setup and for the same reason I suppose.
As taas is under Neutron governance I suppose the CLI code can be moved to neutronclient
(https://opendev.org/openstack/python-neutronclient/src/branch/master/neutronclient/osc/v2 )

I can bring this topic to he Drivers meeting (I am not sure I can participated this week, but on a coming one )

Best wishes
Lajos Katona

Mohammed Naser <mnaser@vexxhost.com> ezt írta (időpont: 2025. szept. 10., Sze, 16:56):
Hi there,

It seems that at the moment, tap-as-a-service package contains both the
server and the client components, which means that if you are trying to
pull in the CLI components, you end up with Neutron as well, which is
quite heavy.

Is there a reason behind it that decision or is this something that
someone needs to get around doing but no one has?

Thanks,
Mohammed