The schema defines entity.health.first with min: 1, max: 500, and DAB correctly rejects first=0 with "Invalid value for first: 0. Value must be greater than 0." However, first=501 is accepted without error.
Expected
DAB should reject first=501 at config deserialization with a message like "Invalid value for first: 501. Value must be at most 500."
Actual
DAB starts normally and runs health checks with first=501. The query becomes SELECT TOP 502 ..., which works but exceeds the documented maximum.
The schema defines
entity.health.firstwithmin: 1, max: 500, and DAB correctly rejectsfirst=0with"Invalid value for first: 0. Value must be greater than 0."However,first=501is accepted without error.Expected
DAB should reject
first=501at config deserialization with a message like"Invalid value for first: 501. Value must be at most 500."Actual
DAB starts normally and runs health checks with
first=501. The query becomesSELECT TOP 502 ..., which works but exceeds the documented maximum.