scripting: add export command

[naveenrajm7]

Fixes #6553

• Exposed VM export via Apple Scripting and CLI
• Turned on sandbox for unsigned utmctl binary to be consistent with unsigned UTM. So we can test the same data across unsigned products.

Example:

Usage in AppleScript

tell application "/Users/***/UTM.app"
  set vm to virtual machine named "ubuntu"
  set output to POSIX file "/Users/***/ubuntuExport.utm"
  export vm to output
end tell

Usage in cli (path must be writable by utmctl)

utmctl export ubuntu --path /Users/***/ubuntuExport.utm

[osy]

I'm curious how to document the fact that utmctl can only specify paths inside the sandbox. Any ideas?

[osy]

Maybe it would be better to not allow passing absolute paths but only relative paths?

[osy]

Can you explain what the use case for utmctl to only export (and import) to paths that are in the sandbox? I'm wondering if this should be in utmctl at all now... I do recall explicitly not adding this functionality for this reason.

[naveenrajm7]

Thanks for your comments, with these and the previous discussion on file URLs now I understand the problem.

When I did this pull request, I did not realize that utmctl command would not work for all paths.
This is because of the wrong test that I did. As shown in example, I first tried export in applescript and then used the same file path after deleting the previous export file to test in utmctl , it worked. But now I see any other file path tried directly via utmctl will not work.

We have two options,

1. Try to get access to path inside utmctl. Similar to what POSIX file in applescript does for us to use that file.
2. Remove support for export command from utmctl only. ( import is not in utmctl)

From your comments, I get a sense that option 1 is not feasible or desirable.
I will remove export from UTMCtl file, please acknowledge if you agree.

Note: Using these commands via apple script will still work, because the POSIX file of applescript takes care of permissions for us.

[osy]

Yeah I remember now I looked extensively into 1 before and found it's just a limitation of Apple's sandbox system. Basically any path accessed by the app must be passed as a bookmark initially. AppleScript does this correctly but there's no way to do this from the terminal. And yes, it still works from AppleScript.

I will go ahead and remove it from utmctl and mention in the release notes that it's only accessible through the AppleScript interface.

[naveenrajm7]

Thanks for agreeing to remove it by yourself.

The Xcode build from main branch fails for me with below error.

ld: framework 'phodav-3.0.0' not found
clang: error: linker command failed with exit code 1 (use -v to see invocation)

[osy]

Yes you need to download the latest dependencies from the actions