Export (Mac) not handling relative paths with a ~

[stephen-holinaty-sp]

Describe the bug while exporting (r-click, export sp-config), the default path/filename doesnt work, and ~/Desktop/file.xml fails.

To Reproduce Using VSCode for mac:

right click on a source Select "Export SP-Config" in the "Enter the file name" box, its prepopulated with some data. hit enter "Error running command..." error try again, enter ~/Desktop/file.json "Error running command" try again, with /usr/admin/Desktop/file.json Success

Expected behavior the "Default" filename should provide a valid export, saved... somewhere. relative paths on mac using the ~ operator should be successful, i.e. ~/Desktop/filename.json

Screenshots

Environment Provide a screenshot of Help > About.

Logs [Extension Host] Writing to identitynowconfig-TENANT-sb.identitynow.com-NetSuite INTQA-2023-03-03T14-27-23.json

Error running command vscode-sailpoint-identitynow.export-node-config.view: A system error occurred (EROFS: read-only file system, open 'identitynowconfig-TENANT-sb.identitynow.com-NetSuite-2023-03-03T14-27-23.json'). This is likely caused by the extension that contributes vscode-sailpoint-identitynow.export-node-config.view.

[yannick-beot-sp]

~ is a 'shell nugget". To resolve ~, we need "extra work" to manage this case (cf. https://github.com/nodejs/node/issues/684).

[stephen-holinaty-sp]

@yannick-beot-sp that is entirely fair. is there any other way that the Default "export" can be a valid path, then? in my mind, "Export... Enter!" should not give a failing use-case.

I'm not sure what type of default save-to location i would even propose, but as we are populating a filename into the default value, my assumption would be fore it to work. or even to replace the default filename with (unix) \path\to\directory\filename.xml) (windows) c:\filepath\filename.xml

or, put another way: if we cant provide a valid path, at least provide a contextual breadcrumb so the user isnt stumbling to find out Why their export is failing.

[yannick-beot-sp]

Export is not failing case. It is just exporting where you do not know which is either the home folder or VSCode folder. I do not have any problem with export because I have a "workspace". I open a folder (for my project, my git repository) and then, VSCode will propose a folder under this folder. I will update this behavior soon to have some personnalization.

[stephen-holinaty-sp]

^ good point re: workspace. When i first open VSCode, there is no open workspace. then i begin interacting with the IdentityNow module, try to export, and

you are correct. with a workspace open, it auto-populates:

[yannick-beot-sp]

I started to work on being able to set the default path proposition in the settings cf. https://github.com/yannick-beot-sp/vscode-sailpoint-identitynow/blob/63aaef66625924217aadd0d17c2eb0f572d5e62b/package.json#L622

The idea is to extend what I just did for new reports to SP-Config exports.

With this capability, you could hard code a path to export to (within your home dir or not), set the architecture of files and folders you want, have dates or not in the filename, etc.

[yannick-beot-sp]

Releases as part of https://github.com/yannick-beot-sp/vscode-sailpoint-identitynow/releases/tag/releases%2Fv0.0.19