tree 7effe5b22c8347defba22f65d512009fe6d72baa
parent eab4915929601700edbc72683ac86d7275d30342
author Laura Peskin <pesk@google.com> 1613654805 +0000
committer CQ Bot <commit-bot@chromium.org> 1613654805 +0000

[config_validator] Change numeric bounds validation to match PrivacyEncoder
usage

Makes a few changes to bring config validation into line with
what is expected by the PrivacyEncoder and privacy encoding params
calculator:
- min_value and/or max_value is required for FleetwideOccurrenceCounts
  with added privacy
- max_count is required for FleetwideHistograms with added privacy
- no bounds are required for UniqueDeviceHistograms and
  HourlyValueHistograms with added privacy

In a follow-up, uses of min_value, max_value, and max_count
are forbidden when not required (e.g. for reports without added
privacy).

DO NOT SUBMIT until https://fxrev.dev/486960 has rolled.

Bug: 70382
Change-Id: I70c6a327bffc24527365a9ccaa14119d192ba9ee
Reviewed-on: https://fuchsia-review.googlesource.com/c/cobalt/+/487001
Commit-Queue: Laura Peskin <pesk@google.com>
Reviewed-by: Zach Bush <zmbush@google.com>