deeplow

Not sure I recall my thoughts on this, unfortunately. But happy to contribute to this conversation.

Here are my findings, building upon previous discussions. I'll start off with some good news. Expectedly, the 4.2 updater has the potential to replace most of the SDW Launcher functionality...

> a) know if updates succeeded; Via exit code, I'd say is the easiest way. > b) know for which VMs updates failed, if any This is a bit more...

> Yeah, I was specifically testing out the cli because you'd mentioned you'd been testing the GUI more heavily, Good thinking. Thanks for that! > Right now, we do basically...

Thanks for the summary @rocodes. Per your suggestion, I'll implement the CLI until the GUI bugs are fixed. I can't foresee many complications in the original. So this is what...

It makes sense the update dom0 part first. It's actually in line with my comment above: > If it's through dom0 then we may hit the case where we need...

I have updated the diagram according to these new changes (plus I added the "check if we should update" part). ![Screenshot 2024-03-22 at 13-57-30 Online FlowChart Diagrams Editor - Mermaid...

### Unfolding the Updater's UI Thinking a bit more about the dom0 updates first part. This has some UX implications which requires adapting the current user interface. In particular I...

I wasn't aware of the existence of this issue and accidentally created a duplicate. Copying an pasting here my comment ---- The current way to import the Tails SVS' credentials...

As I understand, the setting up a CI groundwork is already done and what we're missing now actually creating the integration tests.