The request sounds reasonable request to me. The current API requires users to fetch the current set of allowed-address-pairs and then update it. We had the similar issue around router routes and we added "router routes (atomic) extension" [1]. I think we can use the similar approach for allowed-address-pairs too.
I am not sure the current API is "time-consuming" as described in the bug description though.
The request sounds reasonable request to me. The current API requires users to fetch the current set of allowed- address- pairs and then update it. We had the similar issue around router routes and we added "router routes (atomic) extension" [1]. I think we can use the similar approach for allowed- address- pairs too.
I am not sure the current API is "time-consuming" as described in the bug description though.
[1] https:/ /docs.openstack .org/api- ref/network/ v2/index. html?expanded= remove- extra-routes- from-router- detail, add-extra- routes- to-router- detail# extra-routes- atomic- extension