Nikolay cb50408dc6 fscore: rollback trailing space trim (#7106) ... Previous commit 201fd6de1e removed trailing space trim from data read from file. But common practice is to remove such trailing space. And it leaded to the authorization errors for the major group of users. In first place, this change must help to mitigate an issue with kubernetes. When authorization information was read from Secret content. Changes to the operator was made to mitigate such problem at commit 1cf64358c8 We could introduce later optional flag for VictoriaMetrics to disable trim space behavior. Related issues: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6986 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7089 https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6947 --------- Signed-off-by: f41gh7 <nik@victoriametrics.com> Co-authored-by: Zhu Jiekun <jiekun@victoriametrics.com>		2024-09-29 14:48:36 +02:00
..
fscore.go	fscore: rollback trailing space trim (#7106)	2024-09-29 14:48:36 +02:00
fscore_test.go	all: allow dynamically reading *AuthKey flag values from files and urls	2024-01-22 01:23:23 +02:00