Can you develop on how having new attributes on an existing sub-resource complicates client API binding ?
About "considered working out a different way": you can have a look at [1] and see for yourself, but its not obvious to me where else we could put the new 'advertise_extra_routes' attribute on 'router_association' in a way that would be consistent with the rest of the BGPVPN API.
Can you develop on how having new attributes on an existing sub-resource complicates client API binding ?
About "considered working out a different way": you can have a look at [1] and see for yourself, but its not obvious to me where else we could put the new 'advertise_ extra_routes' attribute on 'router_ association' in a way that would be consistent with the rest of the BGPVPN API.
[1] https:/ /github. com/openstack/ neutron- lib/blob/ master/ neutron_ lib/api/ definitions/ bgpvpn_ routes_ control. py