8 Commits (2e69d59dd2c8edd452ddf753b4fbf8a41d963b76)

Author	SHA1	Message	Date
Timothy Messier	5aafe66c3c	test(ratelimit): Update tests due to new endpoint	2 years ago
Jeff Mitchell	f5dd457b34	Multiple grant scope IDs (#4251) ... Co-authored-by: Timothy Messier <tim.messier@gmail.com> Co-authored-by: Todd <github@quaddi.com>	2 years ago
Damian Debkowski	2dda19aafe	fix: reapply-storage-policy	2 years ago
Louis Ruch	f26243e9af	feat(recording): Delete Session Recording	2 years ago
Louis Ruch	360dd616ff	fix(rate-limiting): Add support for Scope-StoragePolicy actions	2 years ago
Hugo	edbb33de5b	feat(handlers): Implement Policy Service ... This also includes adding new grant and type primitives, as well as package domain names.	2 years ago
Timothy Messier	a77c88ae5d	feat(ratelimit): Increase default values (#4129) ... This increases the default rate limits to: - 1,500 reqs / 30 seconds for list actions in total - 1,500 reqs / 30 seconds for list actions per IP address - 150 reqs / 30 seconds for list actions per auth token And for all other actions: - 30,000 reqs / 30 seconds for list actions in total - 30,000 reqs / 30 seconds for list actions per IP address - 3,000 reqs / 30 seconds for list actions per auth token This seems to be a reasonable default for a small to medium size cluster based on some scale testing. (cherry picked from commit 237c8b6084)	2 years ago
Timothy Messier	a150c588bb	feat(controller): Emit sys event detailing the rate limit configuration ... A sys event will be emitted when the controller is constructed, and if the rate limits are changed via a SIGHUP. The event contains the details of the rate limits for each combination of resource and action. This event can be used by operators to confirm the limits are set as they would expect based on the controller config.	2 years ago