Guard aggregates at the query dispatch, not per route #19
Reference in New Issue
Block a user
Delete Branch "benvin/central-aggregate-guard"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A merged route that forgets the parseAggregate check silently returns one backend's rows: an aggregate row carries no certname, hash or name, so it collapses into a single bucket in the identity-keyed merges. That is how /facts/ shipped broken, and a check at each call site means every future route opts out by omission.