Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ability to manage folders from CLI #73

Closed
allanbowe opened this issue Sep 9, 2020 · 3 comments · Fixed by #118
Closed

ability to manage folders from CLI #73

allanbowe opened this issue Sep 9, 2020 · 3 comments · Fixed by #118
Assignees
Labels

Comments

@allanbowe
Copy link
Member

We need to import the ability to create / delete folders using the cli

sample commands

sasjs createfolder /Public/folder

sasjs deletefolder /Public/folder

sasjs movefolder /Public/source/childFolder /Public/parentTarget
@allanbowe allanbowe changed the title ability to manager folders from CLI ability to manage folders from CLI Sep 9, 2020
@YuryShkoda
Copy link
Member

YuryShkoda commented Sep 25, 2020

We should also provide target to gain an access token:
sasjs createfolder /Public/folder -t target
Suggestion:
sasjs createfolder /Public/folder --> sasjs fs create /Public/folder -t target
sasjs deletefolder /Public/folder --> sasjs fs delete /Public/folder -t target
sasjs movefolder /Public/source/childFolder /Public/parentTarget --> sasjs fs move /Public/source/childFolder /Public/parentTarget -t target

@allanbowe
Copy link
Member Author

-t or --target should definitely be an optional param (leaving it out would take the first target)

I like the suggestion of maintaining the sasjs <action> <verb> however we shouldn't use fs as that implies a filesystem change. In this case we are updating the Viya (and in the future, metadata) logical folder tree (doesn't impact any physical directories).

So perhaps:

sasjs folder create /Public/folder
sasjs folder delete /Public/folder
sasjs folder move /Public/source/childFolder /Public/parentTarget

All of which can have an optional -t parameter

@krishna-acondy
Copy link
Contributor

🎉 This issue has been resolved in version 1.13.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants