-
Story
-
Resolution: Done
-
Medium
-
None
The objective of this spike story is to design the filtering option at dataspace level for event notifications.
Here are some questions to be looked at for this feature:
- How and where do we store the notification filter configurations (on the dataspace itself, on a new specific notification filter configuration, ...)
- What would be the API for creating, updating these configurations ?
- What about using application configuration with regular expressions ? (simple solution, is it flexible enough ?)
- How to be generic enough to be extensible to other kinds of filtering without over-engineer ? As a reminder other potential filtering options later on could be:
- Anchor level
- Yang specific path level (using extension ?)
- Define the hierarchy/priority of filtering options between application global, dataspace, ...
AC:
- Design is documented in Implementation proposal
- Design is shared and agreed with the team
- Story
CPS-469is ready to be implemented