Anis Elleuch 05685863e3 Cancel old logger/audit targets outside lock (#14927) ... When configuring a new target, such as an audit target, the server waits until all audit events are sent to the audit target before doing the swap from the old to the new audit target. Therefore current S3 operations can suffer from this since the audit swap lock will be held. This behavior is unnecessary as the new audit target can enter in a functional mode immediately and the old audit will just cancel itself at its own pace.		2022-05-16 13:32:36 -07:00
..
message	Add audit log for decommissioning (#14858)	2022-05-04 00:45:27 -07:00
target	Fix waitgroup add after wait on config reload (#14584)	2022-03-19 09:15:45 -07:00
audit.go	logger lock should be more granular (#14901)	2022-05-12 07:20:58 -07:00
config.go	Make audit webhook and kafka config dynamic (#14390)	2022-02-24 09:05:33 -08:00
console.go	improve logs, fix banner formatting (#14456)	2022-03-03 13:21:16 -08:00
help.go	Add "enable" to config help (#14866)	2022-05-05 04:17:04 -07:00
legacy.go	feat: Add support for kakfa audit logger target (#12678)	2021-07-13 09:39:13 -07:00
logger.go	logger lock should be more granular (#14901)	2022-05-12 07:20:58 -07:00
logonce.go	logger lock should be more granular (#14901)	2022-05-12 07:20:58 -07:00
reqinfo.go	fix: audit log to support object names in multipleObjectNames() handler (#14017)	2022-01-03 01:28:52 -08:00
targets.go	Cancel old logger/audit targets outside lock (#14927)	2022-05-16 13:32:36 -07:00
utils.go	run gofumpt cleanup across code-base (#14015)	2022-01-02 09:15:06 -08:00