Closed colinhusu closed 2 months ago
I know,there is a lot of newautocli code in the controller, that needs to be retrofitted into more generic clixon code. But I never got edit modes to work, so the submission is appreciated.
Thanks for merging this!
But I never got edit modes to work, so the submission is appreciated.
Do you remember any specific problems in this area? For me edit mode basically appears to work in combination with mountpoints.
Operation across mountpoints, such as "up"
Do you remember any specific problems in this area? For me edit mode basically appears to work in combination with mountpoints.
Not really but there is an issue in the controller project: https://github.com/clicon/clixon-controller/issues/83
I don't remember having seen error messages similar to the one in the mentioned clixon-controller issue.
However, I did get some error-messages before due to inconsistent cli-edit-* states caused by earlier calls to up and top commands. But these should be addressed now.
We will revisit that issue and see if it works now.
The
up
command right now does not properly handle mountpoints. Partly fix that.Note that this does not yet fix the case where the current level is the top-level of the mounted module. In that case the
up
command should switch to the presence container that holds the mounted module. Instead it switches all the way up to the topmost level, so it has the same effect as thetop
command.Fixing that would be more involved:
co_up()
on the top-levelcg_obj
of a mounted module returnsNULL
. That case would need to be handled by finding thecg_obj
matching the mount-point container, i.e. the path stored in"cli-edit-mtpoint"
, and setting that as the newcligen_ph_workpoint
. But I don't now how to get that cg_obj.