See example examples.confd/cli/c_cli/confd.cli to see how to implement clispec call point.
From your latest code it seems to me you are trying to model in clispec same command structure like you get from YNAG data model. This is not suggested (in original post).
The suggestion was to use clispec if you need command (command alias) that would behave same like some other command. E.g.:
show session (implemented as clispec) would be alias to show session brief - command would call in callpoint show session brief with use of maapi_cli_cmd function.
I look through example /cli/c_cli/. I didn’t find function maapi_cli_cmd.
So, i need help to understand why I do command “show my_feature” container is making it iterate through all the existing my_feature enties How to fix this issue?For example in container my_feature have other container session, where as we are concerned about list inside a particular “brief” entry. I create function path_parse in which call particular handler.
Yes, /cli/c_cli/ shows how to implement callpoint (show_my_feature_session_brief in your case), but does not use maapi_cli_cmd. Currently there is no example using maapi_cli_cmd. intro/12-c_maapi show how to use MAAPI from callpoint (but not maapi_cli_cmd). You need to look at MAAPI man page or into User guide section.
Do you mean that data provider iterates through all sublists?
This is how it works. The command tries to show everything under my_feature.
If you want to to do anything, just implement show_my_feature_summary callpoint and do nothing here. But note, all this (clispec) relates only to CLI, not other northbound interfaces.
Can you verify (e.g. with some pritnf logging) that callpoint was called by ConfD. My guess is something wrong went in the application (callpoint). The error should be also visible in devel.log.
If you call maapi_... API from the callpoint, then you need maapi socket. Also note that you should not call anything that can invoke another event on control socket as your ConfD (poll) loop is blocked (worker socket event for this event) - e.g. validatiion (maapi_commit.., dataprovider (maapi_get_....), etc. . If you need this, you need another workersocket and poll loop in different thread.