Is your feature request related to a problem? Please describe.
As of now in GlooPortal, we can only define usageplan at apiproduct spec level, and also the access_level at apiproducts level.
Customers would like to define the usageplan at apidoc's Operation path/verb level. And also the access_level for users at apidoc's Operation path/verb level as well.
Describe the solution you'd like
Usage Plan to be applied on the verb/operation? | endpoint level ratelimit | User ratelimit
=> Difficult to create multiple products
Give Access to that specific user at the endpoint
Reason: Creating multiple products is a Pain point
Each Microservice => Product at endpoint => Traffic control at endpoint bundles up
Context Path needs to have its own set of rules (Someone well versed with Gloo Portal will need to sort of review once)
Timeline : Want to go live next month…
Example:
Product: GENERAL
POST /dogs (100,000 per month + 10 TPS)
POST /cats (150,000 per month + 15 TPS)
GET /dogs (1,000,000 per month + 100 TPS)
GET /cats (1,500,000 per month + 150 TPS)
(GET ONE, PUT, PATCH etc)
Product: PREMIUM
POST /dogs (200,000 per month + 20 TPS)
GET /dogs (2,000,000 per month + 200 TPS)
(GET ONE, PUT, PATCH etc)
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe. As of now in GlooPortal, we can only define
usageplanat apiproduct spec level, and also the access_level at apiproducts level. Customers would like to define theusageplanat apidoc's Operation path/verb level. And also theaccess_levelfor users at apidoc's Operation path/verb level as well.Describe the solution you'd like Usage Plan to be applied on the verb/operation? | endpoint level ratelimit | User ratelimit => Difficult to create multiple products Give Access to that specific user at the endpoint Reason: Creating multiple products is a Pain point Each Microservice => Product at endpoint => Traffic control at endpoint bundles up Context Path needs to have its own set of rules (Someone well versed with Gloo Portal will need to sort of review once) Timeline : Want to go live next month…
Example: Product: GENERAL POST /dogs (100,000 per month + 10 TPS) POST /cats (150,000 per month + 15 TPS) GET /dogs (1,000,000 per month + 100 TPS) GET /cats (1,500,000 per month + 150 TPS) (GET ONE, PUT, PATCH etc)
Product: PREMIUM POST /dogs (200,000 per month + 20 TPS) GET /dogs (2,000,000 per month + 200 TPS) (GET ONE, PUT, PATCH etc)
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.