LifecycleNode: implement service request filtering of inactive managed nodes. #1838
Description
Feature request
Feature description
According to managed node design, while a managed node is in the inactive state, the node will not respond to functional service requests.
Primary State: Inactive
...
While in this state, the node will not receive any execution time to read topics, perform processing of data, respond to functional service requests, etc.
Implementation considerations
Similar to create_publisher(), create_service() API need to be implemented to return a custom service class (ex. LifecycleService)
Pros: In the Inactive state, service requests are filtered according to design concepts.
Cons: API need to be changed (return type of create_service)
I created PR for it. #1836