L1nq0 commented on issue #9073: URL: https://github.com/apache/storm/issues/9073#issuecomment-5535965553
Following up on the design alignment: I've put up #9075 implementing option (2)'s mechanism — bridge-scoped programmatic filter, config-key driven — but shipping it with the deny-list default rather than empty. Reasoning in the PR description; the short version: the knob exists exactly because this path is dangerous by default, so the default should constrain it, and the empty-default escape hatch is one config line for anyone who needs the old behavior. If you prefer strict option (2), say the word and I'll drop the defaults.yaml line — no code change needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
