[FEATURE] CLI commands for common dataset tasks
See original GitHub issue🚨🚨 Feature Request
- Related to an existing Issue
- A new implementation (Improvement, Extension)
If your feature will improve HUB
Add CLI commands to run basic dataset tasks, e.g.:
- delete dataset
- hub.auto ingest dataset (requires hub auto)
- get dataset meta
Difficulty: Medium
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
create-data-set-import-task - AWS Documentation
Override command's default URL with the given URL. --no-verify-ssl (boolean). By default, the AWS CLI uses SSL when communicating with AWS services. For...
Read more >Support CLI Commands - IBM
The following CLI commands are to be used only with the direction of Technical ... This command will list the audit processes and...
Read more >CmdLine@2 - Command line v2 task - Microsoft Learn
Run a command line script using Bash on Linux and macOS and cmd.exe on Windows. ... For more information, see Control options and...
Read more >Command Line Interface (CLI) — CKAN 2.9.7 documentation
Perform commands in the datapusher. dataset, Manage datasets. datastore, Perform commands to set up the datastore. db, Perform various tasks on the database....
Read more >Command Line Interface (CLI) - Oracle Help Center
The CLI is a small-footprint tool that you can use on its own or with the Console to complete Oracle Cloud Infrastructure tasks....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @TakshPanchal - thanks for your willingness to contribute! Yep, the first command should delete the entire dataset which is present at the specified path.
@istranic - we did resolve #1 and #2 (I guess @FayazRahman has completed them), correct?