![Miguel Lavalle](/assets/img/avatar_default.png)
Change [1] wrongly attempted to re-define bandwidth_limit_rules, dscp_marking_rules and minimum_bandwidth_rules as first level API resources, leading to conflicts in the QoS API. We now define alias_bandwidth_limit_rules, alias_dscp_marking_rules and alias_minimum_bandwidth_rules that will enable users to perform GET, PUT and DELETE operations on the corresponding QoS rules without having to specify the associated policy ID. [1] I5366dfee9b760ff5c884981582cdd17245b4d16f Change-Id: I978668ee073c26d6e05ea5e5a0a4e16a7e513fa1 Partial-Bug: #1777627
12 lines
541 B
YAML
12 lines
541 B
YAML
---
|
|
fixes:
|
|
- |
|
|
The ``qos-rules-alias`` API extension wrongly attempted to re-define
|
|
``bandwidth_limit_rules``, ``dscp_marking_rules`` and
|
|
``minimum_bandwidth_rules`` as first level API resources, leading to
|
|
conflicts in the QoS API. We now define ``alias_bandwidth_limit_rules``,
|
|
``alias_dscp_marking_rules`` and ``alias_minimum_bandwidth_rules`` that
|
|
will enable users to perform ``GET``, ``PUT`` and ``DELETE`` operations
|
|
on the corresponding QoS rules without having to specify the associated
|
|
policy ID.
|