To make sure we're on the same page, it would be good to state the exact steps to repro the issue you're observing. If I understand correctly, are you saying that it is currently impossible to update the value of a sub-attribute by means of the REST API call:
PUT /v2.0/api_prefix/top_level_resource/{resource_id}/sub_resource
That said, everything else works fine, ie. DELETE, POST and GET?
Agreed with your point about lack of consistency. I can see the use of sub-attributes is _extensively_ used in other parts of the bgpvpn API, as well as APIs like QoS and Flavors. We definitely need to come up with an answer.
To make sure we're on the same page, it would be good to state the exact steps to repro the issue you're observing. If I understand correctly, are you saying that it is currently impossible to update the value of a sub-attribute by means of the REST API call:
PUT /v2.0/api_ prefix/ top_level_ resource/ {resource_ id}/sub_ resource
That said, everything else works fine, ie. DELETE, POST and GET?
Agreed with your point about lack of consistency. I can see the use of sub-attributes is _extensively_ used in other parts of the bgpvpn API, as well as APIs like QoS and Flavors. We definitely need to come up with an answer.