From f6ca786618a0823427604a7cc5fa9538d2c4f383 Mon Sep 17 00:00:00 2001 From: wangxiyuan Date: Fri, 19 Oct 2018 11:26:06 +0800 Subject: [PATCH] Add release note for unified limit APIs changing Some unified limit API related bugs have been fixed recently. This patch add the release notes for them. Once more bugs are fixed, this file can be updated as well. Change-Id: Ib9772d962a3a284e342db7825b16f610a099f0cf --- ...ied-limit-api-improvment-b34d18769d18a0a7.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 releasenotes/notes/unified-limit-api-improvment-b34d18769d18a0a7.yaml diff --git a/releasenotes/notes/unified-limit-api-improvment-b34d18769d18a0a7.yaml b/releasenotes/notes/unified-limit-api-improvment-b34d18769d18a0a7.yaml new file mode 100644 index 0000000000..7848484c1c --- /dev/null +++ b/releasenotes/notes/unified-limit-api-improvment-b34d18769d18a0a7.yaml @@ -0,0 +1,15 @@ +--- +fixes: + - > + Some bugs for unified limit APIs have been fixed, it includes: + + * [`bug 1798716 `_] + The `region_id` of registered limit now can be updated to `None`. + * [`bug 1798495 `_] + The length of unified limit's `resource_name` now is limited from `1` + to `255` (string). + * [`bug 1797876 `_] + The `default_limit` of registered limit and the `resource_limit` of + limit now are limited from `-1` to `2147483647` (integer). `-1` means + no limit. `2147483647` is the max value for integer by default in SQL + (4 bytes).