Details
-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
Description
Any policy name changes need to be done before Apicast 3.3 ER1 release on Aug 30.
Product need to close the new names by August 29th at the latest.
- new policies in 2.3 can in theory be renamed to anything. Might break some person's setup and maybe a test or two , but if we're going to do that - it's now or never.
- we cannot rename policies that were included in 2.2, but I believe we can change the "Display Name" that is shown on the UI
- changes to "Rate Limiting" policy name were discussed.
- changing "Apicast" policy to "3scale" (display name) was discussed.
- I suggest that the "Batching" part of the "Caching and Batching" policy is in fact "aggregation" (as a number of counter increments are aggregated to result in one counter increase that is sent to backend in 1 request). But not huge one for me.