Flow classification rules: add directionality to specify inbound rules for a consumer #7031
Closed
5 tasks done
Labels
fixed (test & close)
An issue has been fixed, merged into master and is ready for further testing
noteworthy
probably worth mentioning in release notes
Milestone
Description
The goal is to be able to express 'resistance' rules or similar where a consuming application can express that they do not want to be receiving flows with a given data type.
Resourcing
We intend to contribute this feature
The text was updated successfully, but these errors were encountered: