[NETCONF-1099] Restore sal-remote create-notification-stream functionality Created: 25/Jul/23  Updated: 30/Oct/23  Resolved: 30/Oct/23

Status: Resolved
Project: netconf
Component/s: restconf-nb
Affects Version/s: None
Fix Version/s: 7.0.0

Type: Improvement Priority: High
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks NETCONF-1102 Refactor notification stream starts In Progress
Relates
relates to NETCONF-342 Make notifications defined by yangs a... Resolved

 Description   

RESTCONF northbound's data service contains a special case on access to ietf-restconf-monitoring's stream state: on each access we write populate streams derived from individual notifications. This was introduced for unknown reasons in NETCONF-342, which also removed implementation for sal-remote.yang's create-notification-stream.

Effectively revert NETCONF-342, as it just does not make sense, restoring proper support creating notification streams.

 Comments   
Comment by Robert Varga [ 29/Oct/23 ]

As part of this change we need to also rehost notification stream naming to ListenersBroker and then refactor them so the stream names do not carry all the metadata about how to establish them.

Generated at Wed Feb 07 20:16:40 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.