Stefan Benten 2f648fd981 satellite: make limits be nullable ... Currently we have no way to actually set one of the following limits to 0 (meaning not usable): - maxBuckets - usageLimit - bandwidthLimit With having the field nullable, NULL corresponds to the global default, 0 now actually 0 and a set value determines a custom limit. Change-Id: I92bb77529dcbd0881ae8368921be9d246eb0919e		2020-09-21 19:34:19 +00:00
..
live	all: add missing dots	2020-08-11 17:50:01 +03:00
projectbwcleanup	satellite/accounting: fix build - time rounding	2020-08-31 09:37:13 -04:00
reportedrollup	satellite/orders: use metabase types as arguments	2020-08-28 15:52:37 +03:00
rollup	satellite: fix scoping, formatting	2020-07-16 19:13:14 +03:00
tally	satellite/metainfo: replace ScopedPath with metabase.SegmentLocation	2020-09-04 10:06:52 +00:00
billing_test.go	satellite/metainfo: use metabase.SegmentKey with metainfo.Service	2020-09-03 15:11:32 +00:00
bucketstats.go	satellite/metainfo: use metabase in loop	2020-09-01 10:06:16 +00:00
bucketusage.go	all: fix dots	2020-07-16 14:58:28 +00:00
common.go	all: add missing dots	2020-08-11 17:50:01 +03:00
db_test.go	satellite: make limits be nullable	2020-09-21 19:34:19 +00:00
db.go	satellite: make limits be nullable	2020-09-21 19:34:19 +00:00
projectusage_test.go	satellite/metainfo: use metabase.SegmentKey with metainfo.Service	2020-09-03 15:11:32 +00:00
projectusage.go	satellite: make limits be nullable	2020-09-21 19:34:19 +00:00