paul cannon 5bc4c254d4 satellite/reputation: move Config fields into a Config struct ... This has been a cause of some confusion, even though the fields are labeled as being copies of config values. Having them be under a field explicitly named "Config" makes this clearer, plus, allows the values to be passed in simply as a copy of the Config struct from the satellite, rather than copying the fields individually (which can be error-prone, particularly as the AuditCount field in UpdateRequest is apparently not the same thing as the AuditCount field in reputation.Config). Refs: https://github.com/storj/storj/issues/4601 Change-Id: I386953347b71068596618616934aa28e3245cdc1		2022-05-24 20:57:51 +00:00
..
audithistory_test.go	satellite/reputation: don't need 3 identical AuditHistory types	2022-05-24 05:48:46 +00:00
audithistory.go	satellite/reputation: don't need 3 identical AuditHistory types	2022-05-24 05:48:46 +00:00
benchmark_test.go	satellite/reputation: move Config fields into a Config struct	2022-05-24 20:57:51 +00:00
config.go	satellite/reputation: move Config fields into a Config struct	2022-05-24 20:57:51 +00:00
db_test.go	satellite/reputation: move Config fields into a Config struct	2022-05-24 20:57:51 +00:00
service_test.go	satellite/reputation: add disqualification reason for status update	2022-04-20 13:29:10 +00:00
service.go	satellite/reputation: move Config fields into a Config struct	2022-05-24 20:57:51 +00:00
suspension_test.go	satellite/reputation: move Config fields into a Config struct	2022-05-24 20:57:51 +00:00