[bug] mapt should test the permission of the target files/directories before creating anything

[kpouget]

When launching mapt in containers with the wrong user permissions, mapt may fail to create the files necessary to destroy the cloud resource (with mapt).

Examples:

INFO Resources:
INFO     + 16 created
INFO
INFO Duration: 9m39s
INFO
open /workspace/host: is a directory

INFO Resources:
INFO     + 16 created
INFO
INFO Duration: 12m26s
INFO
open /workspace/username: permission denied

This one is less of an issue, as it fails early. But mapt could provide a more user-friendly error message:

DEBU Based on avg prices for instance types ...
DEBU Spot data: {[Standard_D48s_v4] 0.8233680000000001 uksouth  0}
DEBU managing stack stackCreateWindowsDesktop-kpouget-windows-desktop-test
ERRO Failed to create or select stack: failed to select stack: exit status 255
code: 255
stdout:
stderr: error: write ".pulumi/meta.yaml": blob (key ".pulumi/meta.yaml") (code=Unknown): mkdir /workspace/.pulumi: permission denied

[adrianriobo]

Did you use --user 0

[kpouget]

yes, my point with the ticket is not how to solve the permission issue, but to prevent mapt from going too far when it won't be able to complete its task

crc has a pre-flight check, that's the same spirit. Validate as much as possible early, to avoid users the trouble of a failure in the middle of the process, where it gets complicated to cleanup the cloud resources