@pedronis no, this was a follow-up task to the other console-conf work.
In snapd we could add an option to snap managed or something like this to implement waiting for a real response, etc. but I think this needs some design decisions on how much work we want to do in snapd vs work in console-conf-wrapper to call `snap managed` in a more robust way.
This could be done almost entirely in snapd by adding a special option to `snap managed`, and then all console-conf would need to do is use that option and add a little bit of handling around what if the snap command doesn't exist, etc. and just rely on the snapd work.
Or this could be done entirely in console-conf using a loop like I pasted in the description with a bit more error messages, etc. to make it more user-friendly.
@pedronis no, this was a follow-up task to the other console-conf work.
In snapd we could add an option to snap managed or something like this to implement waiting for a real response, etc. but I think this needs some design decisions on how much work we want to do in snapd vs work in console- conf-wrapper to call `snap managed` in a more robust way.
This could be done almost entirely in snapd by adding a special option to `snap managed`, and then all console-conf would need to do is use that option and add a little bit of handling around what if the snap command doesn't exist, etc. and just rely on the snapd work.
Or this could be done entirely in console-conf using a loop like I pasted in the description with a bit more error messages, etc. to make it more user-friendly.