This PR addresses the “misalignments” of #33682.
Summing up: The change which was brought with v30 was broadly discussed and deliberately chosen. I think that reverting the defaults now would be a bad idea. And even if, the path to do this should not be this PR and changing defaults should not be bundled with introducing a new knob. @cedwies, this new PR keeps v30 defaults AND also removes the “public knob”. It must definitely keep the new count default constant, as that is the main new concept introduced. Specifically for:
- Custom client’s policy, including ones that wish full pre-v30 policy compatibility
- More exhaustive testing
- Consistency and specificity @achow101, this new PR should not be “re-litigating” anything, but if there is, I’ll be glad to discover how.
Constructive feedback is welcomed.