cloudos-cli 2.91.0__tar.gz → 2.92.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (79) hide show
  1. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/PKG-INFO +28 -30
  2. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/README.md +27 -29
  3. cloudos_cli-2.92.0/cloudos_cli/_version.py +1 -0
  4. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/procurement/cli.py +7 -10
  5. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/procurement/images.py +7 -9
  6. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli.egg-info/PKG-INFO +28 -30
  7. cloudos_cli-2.91.0/cloudos_cli/_version.py +0 -1
  8. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/LICENSE +0 -0
  9. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/__init__.py +0 -0
  10. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/__main__.py +0 -0
  11. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/bash/__init__.py +0 -0
  12. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/bash/cli.py +0 -0
  13. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/clos.py +0 -0
  14. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/configure/__init__.py +0 -0
  15. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/configure/cli.py +0 -0
  16. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/configure/configure.py +0 -0
  17. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/constants.py +0 -0
  18. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/cost/__init__.py +0 -0
  19. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/cost/cost.py +0 -0
  20. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/cromwell/__init__.py +0 -0
  21. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/cromwell/cli.py +0 -0
  22. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/datasets/__init__.py +0 -0
  23. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/datasets/cli.py +0 -0
  24. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/datasets/datasets.py +0 -0
  25. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/import_wf/__init__.py +0 -0
  26. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/import_wf/import_wf.py +0 -0
  27. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/interactive_session/__init__.py +0 -0
  28. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/interactive_session/cli.py +0 -0
  29. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/interactive_session/interactive_session.py +0 -0
  30. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/jobs/__init__.py +0 -0
  31. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/jobs/cli.py +0 -0
  32. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/jobs/job.py +0 -0
  33. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/link/__init__.py +0 -0
  34. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/link/cli.py +0 -0
  35. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/link/link.py +0 -0
  36. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/logging/__init__.py +0 -0
  37. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/logging/logger.py +0 -0
  38. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/procurement/__init__.py +0 -0
  39. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/projects/__init__.py +0 -0
  40. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/projects/cli.py +0 -0
  41. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/queue/__init__.py +0 -0
  42. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/queue/cli.py +0 -0
  43. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/queue/queue.py +0 -0
  44. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/related_analyses/__init__.py +0 -0
  45. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/related_analyses/related_analyses.py +0 -0
  46. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/__init__.py +0 -0
  47. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/array_job.py +0 -0
  48. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/cli_helpers.py +0 -0
  49. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/cloud.py +0 -0
  50. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/details.py +0 -0
  51. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/errors.py +0 -0
  52. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/last_wf.py +0 -0
  53. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/nextflow_version.py +0 -0
  54. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/requests.py +0 -0
  55. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/utils/resources.py +0 -0
  56. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/workflows/__init__.py +0 -0
  57. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli/workflows/cli.py +0 -0
  58. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli.egg-info/SOURCES.txt +0 -0
  59. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli.egg-info/dependency_links.txt +0 -0
  60. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli.egg-info/entry_points.txt +0 -0
  61. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli.egg-info/requires.txt +0 -0
  62. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/cloudos_cli.egg-info/top_level.txt +0 -0
  63. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/setup.cfg +0 -0
  64. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/setup.py +0 -0
  65. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/__init__.py +0 -0
  66. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/functions_for_pytest.py +0 -0
  67. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_cli_project_create.py +0 -0
  68. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_cost/__init__.py +0 -0
  69. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_cost/test_job_cost.py +0 -0
  70. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_details.py +0 -0
  71. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_error_messages.py +0 -0
  72. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_interactive_session/__init__.py +0 -0
  73. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_interactive_session/test_create_session.py +0 -0
  74. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_interactive_session/test_list_sessions.py +0 -0
  75. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_logging/__init__.py +0 -0
  76. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_logging/test_logger.py +0 -0
  77. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_nextflow_version.py +0 -0
  78. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_related_analyses/__init__.py +0 -0
  79. {cloudos_cli-2.91.0 → cloudos_cli-2.92.0}/tests/test_related_analyses/test_related_analyses.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: cloudos_cli
3
- Version: 2.91.0
3
+ Version: 2.92.0
4
4
  Summary: Python package for interacting with the Lifebit Platform
5
5
  Home-page: https://github.com/lifebit-ai/cloudos-cli
6
6
  Author: David Piñeyro
@@ -231,10 +231,10 @@ This will tell you the implemented commands. Each implemented command has its ow
231
231
  ```bash
232
232
  cloudos job list --help
233
233
  ```
234
- ```console Usage: cloudos job list [OPTIONS]
235
-
236
- Collect workspace jobs from a Lifebit Platform workspace in CSV or JSON format.
237
-
234
+ ```console Usage: cloudos job list [OPTIONS]
235
+
236
+ Collect workspace jobs from a Lifebit Platform workspace in CSV or JSON format.
237
+
238
238
  ╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────╮
239
239
  │ * --apikey -k TEXT Your Lifebit Platform API key [required] │
240
240
  │ * --cloudos-url -c TEXT The Lifebit Platform url you are trying to access to. │
@@ -299,7 +299,7 @@ $HOME
299
299
 
300
300
  ### Configure Default Profile
301
301
 
302
- To facilitate the reuse of required parameters, you can create profiles.
302
+ To facilitate the reuse of required parameters, you can create profiles.
303
303
 
304
304
  To generate a profile called `default`, use the following command:
305
305
 
@@ -321,7 +321,7 @@ The same prompts will appear, including the execution platform (aws or azure). I
321
321
 
322
322
  When configuring a profile, you can specify:
323
323
  - **API Key**: Your Lifebit Platform API credentials
324
- - **Platform URL**: The Lifebit Platform instance URL
324
+ - **Platform URL**: The Lifebit Platform instance URL
325
325
  - **Project Name**: Default project for commands
326
326
  - **Execution Platform**: `aws` (default) or `azure` - determines default instance types and available features
327
327
  - **Repository Platform**: Version control system (github, gitlab, etc.)
@@ -1314,7 +1314,7 @@ cloudos job cost --profile my_profile --job-id 62c83a1191fe06013b7ef355
1314
1314
  The expected output is a formatted table showing:
1315
1315
 
1316
1316
  ```console
1317
- Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1317
+ Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1318
1318
  ┏━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━┓
1319
1319
  ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ Compute ┃ ┃
1320
1320
  ┃ ┃ Instance ┃ ┃ Life-cycle ┃ ┃ Compute ┃ Instance ┃ storage ┃ ┃
@@ -1343,7 +1343,7 @@ On page 1/2: n = next, p = prev, q = quit
1343
1343
 
1344
1344
  By pressing 'n', it will show the next page or the last if it is the case.
1345
1345
 
1346
- Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1346
+ Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1347
1347
  ┏━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━┓
1348
1348
  ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ Compute ┃ ┃
1349
1349
  ┃ ┃ Instance ┃ ┃ Life-cycle ┃ ┃ Compute ┃ Instance ┃ storage ┃ ┃
@@ -1462,7 +1462,7 @@ The expected output is a formatted table showing:
1462
1462
  ```console
1463
1463
  Total related analyses found: 15
1464
1464
 
1465
- Related Analyses
1465
+ Related Analyses
1466
1466
  ┏━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━┳━━━━━━━━━━━━┓
1467
1467
  ┃ Status ┃ Name ┃ Owner ┃ ID ┃ Submit time ┃ Run time ┃ Total Cost ┃
1468
1468
  ┡━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━╇━━━━━━━━━━━━┩
@@ -1944,7 +1944,7 @@ Example Python Script:
1944
1944
  #!/usr/bin/python3
1945
1945
  print("Hello world")
1946
1946
  ```
1947
-
1947
+
1948
1948
  2. Or use an interpreter command in the executable field
1949
1949
 
1950
1950
  If your script doesn’t have a shebang line, you can execute it by explicitly specifying the interpreter in the executable command:
@@ -2021,7 +2021,7 @@ Interactive sessions allow you to work within the platform using different virtu
2021
2021
 
2022
2022
  You can get a list of all interactive sessions in your workspace by running `cloudos interactive-session list`. The command can produce three different output formats that can be selected using the `--output-format` option:
2023
2023
 
2024
- - **stdout** (default): Displays a table directly in the terminal with interactive pagination
2024
+ - **stdout** (default): Displays a table directly in the terminal with interactive pagination
2025
2025
  - **csv**: Saves session data to a CSV file with a minimum predefined set of columns by default, or all available columns using the `--all-fields` parameter
2026
2026
  - **json**: Saves complete session information to a JSON file with all available fields
2027
2027
 
@@ -2036,7 +2036,7 @@ cloudos interactive-session list --profile my_profile --output-format stdout
2036
2036
  The table displays sessions with pagination controls (press `n` for next page, `p` for previous page, or `q` to quit):
2037
2037
 
2038
2038
  ```console
2039
- Interactive Sessions
2039
+ Interactive Sessions
2040
2040
  ┏━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━┓
2041
2041
  ┃ Status ┃ Name ┃ Type ┃ ID ┃ Owner ┃
2042
2042
  ┡━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━┩
@@ -2646,7 +2646,7 @@ The `datasets ls` command supports different output formats using the `--output-
2646
2646
  - **`stdout` (default)**: Displays results in the console with Rich formatting
2647
2647
  - Without `--details`: Simple list of file/folder names with color coding (blue underlined for folders)
2648
2648
  - With `--details`: Rich formatted table with all file information
2649
-
2649
+
2650
2650
  - **`csv`**: Saves results to a CSV file
2651
2651
  - Without `--details`: CSV with two columns: "Name,Storage Path"
2652
2652
  - With `--details`: CSV with columns "Type, Owner, Size, Size (bytes), Last Updated, Virtual Name, Storage Path"
@@ -2696,7 +2696,7 @@ Any of the `source_path` must be a full path, starting from the `Data` datasets
2696
2696
  An example of such command is:
2697
2697
 
2698
2698
  ```
2699
- cloudos datasets mv Data/results/my_plot.png Data/plots
2699
+ cloudos datasets mv Data/results/my_plot.png Data/plots
2700
2700
  ```
2701
2701
 
2702
2702
  #### Rename Files
@@ -2707,7 +2707,7 @@ Change file and folder names while keeping them in the same location. This helps
2707
2707
  > Files and folders within the `Data` dataset can be renamed using the following command
2708
2708
 
2709
2709
  ```bash
2710
- cloudos datasets rename <path> <new_name> --profile my_profile
2710
+ cloudos datasets rename <path> <new_name> --profile my_profile
2711
2711
  ```
2712
2712
  where `path` is the full path to the file/folder to be renamed and `new_name` is just the name, no path required, as the file will not be moved.
2713
2713
 
@@ -2733,12 +2733,12 @@ or it can happen **across different projects** within the same workspace
2733
2733
  cloudos datasets cp <source_path> <destination_path> --profile <profile> --destination-project-name <project>
2734
2734
  ```
2735
2735
 
2736
- Any of the `source_path` must be a full path; any `destination_path` must be a path starting with `Data` and finishing with the folder where to move the file/folder.
2736
+ Any of the `source_path` must be a full path; any `destination_path` must be a path starting with `Data` and finishing with the folder where to move the file/folder.
2737
2737
 
2738
2738
  An example of such command is:
2739
2739
 
2740
2740
  ```
2741
- cloudos datasets cp AnalysesResults/my_analysis/results/my_plot.png Data/plots
2741
+ cloudos datasets cp AnalysesResults/my_analysis/results/my_plot.png Data/plots
2742
2742
  ```
2743
2743
 
2744
2744
 
@@ -2789,7 +2789,7 @@ Create new organizational folders within your projects to maintain structured da
2789
2789
  > New folders can be created within the `Data` dataset and its subfolders.
2790
2790
 
2791
2791
  ```bash
2792
- cloudos datasets mkdir <new_folder_path> --profile my_profile
2792
+ cloudos datasets mkdir <new_folder_path> --profile my_profile
2793
2793
  ```
2794
2794
 
2795
2795
  #### Remove Files or Folders
@@ -2797,14 +2797,14 @@ cloudos datasets mkdir <new_folder_path> --profile my_profile
2797
2797
  Remove unnecessary files or empty folders from your File Explorer. Note that this removes files from Lifebit Platform but not from underlying cloud storage.
2798
2798
 
2799
2799
  > [!NOTE]
2800
- > Files and folders can be removed in the `Data` datasets and its subfolders.
2800
+ > Files and folders can be removed in the `Data` datasets and its subfolders.
2801
2801
 
2802
2802
  ```bash
2803
2803
  cloudos datasets rm <path> --profile my_profile
2804
2804
  ```
2805
2805
  > [!NOTE]
2806
2806
  > If a file was uploaded by the user, in order to be removed you must use `--force` and that will permanently remove the file. If the file is "linked" (e.g a s3 folder or file), removing it using `cloudos datasets rm` will not remove it from the the s3 bucket.
2807
-
2807
+
2808
2808
  ---
2809
2809
 
2810
2810
  ### Link
@@ -2926,7 +2926,7 @@ To list images for a specific procurement, use the following command:
2926
2926
 
2927
2927
  ```bash
2928
2928
  cloudos procurement images ls \
2929
- -- profile procurement_profile
2929
+ -- profile procurement_profile
2930
2930
  --procurement-id "your_procurement_id_here"
2931
2931
  ```
2932
2932
 
@@ -2985,12 +2985,10 @@ cloudos procurement images set --profile procurement_profile --image-type "JobDe
2985
2985
  - `--image-type`: The Lifebit Platform resource image type (required). Possible values:
2986
2986
  - `RegularInteractiveSessions`
2987
2987
  - `SparkInteractiveSessions`
2988
- - `RStudioInteractiveSessions`
2989
- - `JupyterInteractiveSessions`
2990
2988
  - `JobDefault`
2991
2989
  - `NextflowBatchComputeEnvironment`
2992
- - `--provider`: The cloud provider (required). Currently only `aws` is supported
2993
- - `--region`: The cloud region (required). Currently only AWS regions are supported
2990
+ - `--provider`: The cloud provider (required). Currently only supporting `aws` and `azure`.
2991
+ - `--region`: The cloud region (required). Currently only supporting aws and azure regions.
2994
2992
  - `--image-id`: The new image ID value (required)
2995
2993
  - `--image-name`: The new image name value (optional)
2996
2994
  - `--image-version`: The new image version (required)
@@ -3023,7 +3021,7 @@ cloudos procurement images reset --profile procurement_profile --image-type "Job
3023
3021
  - `--organisation-id`: The organization ID where the change will be applied (required)
3024
3022
  - `--image-type`: The Lifebit Platform resource image type (required). Same values as for `set` command
3025
3023
  - `--provider`: The cloud provider (required). Currently only `aws` is supported
3026
- - `--region`: The cloud region (required). Currently only AWS regions are supported
3024
+ - `--region`: The cloud region (required). Currently only supporting aws and azure regions.
3027
3025
  - `--disable-ssl-verification`: Disable SSL certificate verification
3028
3026
  - `--ssl-cert`: Path to your SSL certificate file
3029
3027
  - `--profile`: Profile to use from the config file
@@ -3052,7 +3050,7 @@ Executing status...
3052
3050
  Current Cromwell server status is: Stopped
3053
3051
  ```
3054
3052
 
3055
- ```bash
3053
+ ```bash
3056
3054
  # Cromwell start
3057
3055
  cloudos cromwell start --profile my_profile
3058
3056
  ```
@@ -3278,8 +3276,8 @@ responses>=0.21.0
3278
3276
  mock>=3.0.5
3279
3277
  ```
3280
3278
 
3281
- Command to run tests from the `cloudos-cli` main folder:
3279
+ Command to run tests from the `cloudos-cli` main folder:
3282
3280
 
3283
3281
  ```
3284
3282
  python -m pytest -s -v
3285
- ```
3283
+ ```
@@ -196,10 +196,10 @@ This will tell you the implemented commands. Each implemented command has its ow
196
196
  ```bash
197
197
  cloudos job list --help
198
198
  ```
199
- ```console Usage: cloudos job list [OPTIONS]
200
-
201
- Collect workspace jobs from a Lifebit Platform workspace in CSV or JSON format.
202
-
199
+ ```console Usage: cloudos job list [OPTIONS]
200
+
201
+ Collect workspace jobs from a Lifebit Platform workspace in CSV or JSON format.
202
+
203
203
  ╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────╮
204
204
  │ * --apikey -k TEXT Your Lifebit Platform API key [required] │
205
205
  │ * --cloudos-url -c TEXT The Lifebit Platform url you are trying to access to. │
@@ -264,7 +264,7 @@ $HOME
264
264
 
265
265
  ### Configure Default Profile
266
266
 
267
- To facilitate the reuse of required parameters, you can create profiles.
267
+ To facilitate the reuse of required parameters, you can create profiles.
268
268
 
269
269
  To generate a profile called `default`, use the following command:
270
270
 
@@ -286,7 +286,7 @@ The same prompts will appear, including the execution platform (aws or azure). I
286
286
 
287
287
  When configuring a profile, you can specify:
288
288
  - **API Key**: Your Lifebit Platform API credentials
289
- - **Platform URL**: The Lifebit Platform instance URL
289
+ - **Platform URL**: The Lifebit Platform instance URL
290
290
  - **Project Name**: Default project for commands
291
291
  - **Execution Platform**: `aws` (default) or `azure` - determines default instance types and available features
292
292
  - **Repository Platform**: Version control system (github, gitlab, etc.)
@@ -1279,7 +1279,7 @@ cloudos job cost --profile my_profile --job-id 62c83a1191fe06013b7ef355
1279
1279
  The expected output is a formatted table showing:
1280
1280
 
1281
1281
  ```console
1282
- Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1282
+ Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1283
1283
  ┏━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━┓
1284
1284
  ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ Compute ┃ ┃
1285
1285
  ┃ ┃ Instance ┃ ┃ Life-cycle ┃ ┃ Compute ┃ Instance ┃ storage ┃ ┃
@@ -1308,7 +1308,7 @@ On page 1/2: n = next, p = prev, q = quit
1308
1308
 
1309
1309
  By pressing 'n', it will show the next page or the last if it is the case.
1310
1310
 
1311
- Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1311
+ Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1312
1312
  ┏━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━┓
1313
1313
  ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ Compute ┃ ┃
1314
1314
  ┃ ┃ Instance ┃ ┃ Life-cycle ┃ ┃ Compute ┃ Instance ┃ storage ┃ ┃
@@ -1427,7 +1427,7 @@ The expected output is a formatted table showing:
1427
1427
  ```console
1428
1428
  Total related analyses found: 15
1429
1429
 
1430
- Related Analyses
1430
+ Related Analyses
1431
1431
  ┏━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━┳━━━━━━━━━━━━┓
1432
1432
  ┃ Status ┃ Name ┃ Owner ┃ ID ┃ Submit time ┃ Run time ┃ Total Cost ┃
1433
1433
  ┡━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━╇━━━━━━━━━━━━┩
@@ -1909,7 +1909,7 @@ Example Python Script:
1909
1909
  #!/usr/bin/python3
1910
1910
  print("Hello world")
1911
1911
  ```
1912
-
1912
+
1913
1913
  2. Or use an interpreter command in the executable field
1914
1914
 
1915
1915
  If your script doesn’t have a shebang line, you can execute it by explicitly specifying the interpreter in the executable command:
@@ -1986,7 +1986,7 @@ Interactive sessions allow you to work within the platform using different virtu
1986
1986
 
1987
1987
  You can get a list of all interactive sessions in your workspace by running `cloudos interactive-session list`. The command can produce three different output formats that can be selected using the `--output-format` option:
1988
1988
 
1989
- - **stdout** (default): Displays a table directly in the terminal with interactive pagination
1989
+ - **stdout** (default): Displays a table directly in the terminal with interactive pagination
1990
1990
  - **csv**: Saves session data to a CSV file with a minimum predefined set of columns by default, or all available columns using the `--all-fields` parameter
1991
1991
  - **json**: Saves complete session information to a JSON file with all available fields
1992
1992
 
@@ -2001,7 +2001,7 @@ cloudos interactive-session list --profile my_profile --output-format stdout
2001
2001
  The table displays sessions with pagination controls (press `n` for next page, `p` for previous page, or `q` to quit):
2002
2002
 
2003
2003
  ```console
2004
- Interactive Sessions
2004
+ Interactive Sessions
2005
2005
  ┏━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━┓
2006
2006
  ┃ Status ┃ Name ┃ Type ┃ ID ┃ Owner ┃
2007
2007
  ┡━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━┩
@@ -2611,7 +2611,7 @@ The `datasets ls` command supports different output formats using the `--output-
2611
2611
  - **`stdout` (default)**: Displays results in the console with Rich formatting
2612
2612
  - Without `--details`: Simple list of file/folder names with color coding (blue underlined for folders)
2613
2613
  - With `--details`: Rich formatted table with all file information
2614
-
2614
+
2615
2615
  - **`csv`**: Saves results to a CSV file
2616
2616
  - Without `--details`: CSV with two columns: "Name,Storage Path"
2617
2617
  - With `--details`: CSV with columns "Type, Owner, Size, Size (bytes), Last Updated, Virtual Name, Storage Path"
@@ -2661,7 +2661,7 @@ Any of the `source_path` must be a full path, starting from the `Data` datasets
2661
2661
  An example of such command is:
2662
2662
 
2663
2663
  ```
2664
- cloudos datasets mv Data/results/my_plot.png Data/plots
2664
+ cloudos datasets mv Data/results/my_plot.png Data/plots
2665
2665
  ```
2666
2666
 
2667
2667
  #### Rename Files
@@ -2672,7 +2672,7 @@ Change file and folder names while keeping them in the same location. This helps
2672
2672
  > Files and folders within the `Data` dataset can be renamed using the following command
2673
2673
 
2674
2674
  ```bash
2675
- cloudos datasets rename <path> <new_name> --profile my_profile
2675
+ cloudos datasets rename <path> <new_name> --profile my_profile
2676
2676
  ```
2677
2677
  where `path` is the full path to the file/folder to be renamed and `new_name` is just the name, no path required, as the file will not be moved.
2678
2678
 
@@ -2698,12 +2698,12 @@ or it can happen **across different projects** within the same workspace
2698
2698
  cloudos datasets cp <source_path> <destination_path> --profile <profile> --destination-project-name <project>
2699
2699
  ```
2700
2700
 
2701
- Any of the `source_path` must be a full path; any `destination_path` must be a path starting with `Data` and finishing with the folder where to move the file/folder.
2701
+ Any of the `source_path` must be a full path; any `destination_path` must be a path starting with `Data` and finishing with the folder where to move the file/folder.
2702
2702
 
2703
2703
  An example of such command is:
2704
2704
 
2705
2705
  ```
2706
- cloudos datasets cp AnalysesResults/my_analysis/results/my_plot.png Data/plots
2706
+ cloudos datasets cp AnalysesResults/my_analysis/results/my_plot.png Data/plots
2707
2707
  ```
2708
2708
 
2709
2709
 
@@ -2754,7 +2754,7 @@ Create new organizational folders within your projects to maintain structured da
2754
2754
  > New folders can be created within the `Data` dataset and its subfolders.
2755
2755
 
2756
2756
  ```bash
2757
- cloudos datasets mkdir <new_folder_path> --profile my_profile
2757
+ cloudos datasets mkdir <new_folder_path> --profile my_profile
2758
2758
  ```
2759
2759
 
2760
2760
  #### Remove Files or Folders
@@ -2762,14 +2762,14 @@ cloudos datasets mkdir <new_folder_path> --profile my_profile
2762
2762
  Remove unnecessary files or empty folders from your File Explorer. Note that this removes files from Lifebit Platform but not from underlying cloud storage.
2763
2763
 
2764
2764
  > [!NOTE]
2765
- > Files and folders can be removed in the `Data` datasets and its subfolders.
2765
+ > Files and folders can be removed in the `Data` datasets and its subfolders.
2766
2766
 
2767
2767
  ```bash
2768
2768
  cloudos datasets rm <path> --profile my_profile
2769
2769
  ```
2770
2770
  > [!NOTE]
2771
2771
  > If a file was uploaded by the user, in order to be removed you must use `--force` and that will permanently remove the file. If the file is "linked" (e.g a s3 folder or file), removing it using `cloudos datasets rm` will not remove it from the the s3 bucket.
2772
-
2772
+
2773
2773
  ---
2774
2774
 
2775
2775
  ### Link
@@ -2891,7 +2891,7 @@ To list images for a specific procurement, use the following command:
2891
2891
 
2892
2892
  ```bash
2893
2893
  cloudos procurement images ls \
2894
- -- profile procurement_profile
2894
+ -- profile procurement_profile
2895
2895
  --procurement-id "your_procurement_id_here"
2896
2896
  ```
2897
2897
 
@@ -2950,12 +2950,10 @@ cloudos procurement images set --profile procurement_profile --image-type "JobDe
2950
2950
  - `--image-type`: The Lifebit Platform resource image type (required). Possible values:
2951
2951
  - `RegularInteractiveSessions`
2952
2952
  - `SparkInteractiveSessions`
2953
- - `RStudioInteractiveSessions`
2954
- - `JupyterInteractiveSessions`
2955
2953
  - `JobDefault`
2956
2954
  - `NextflowBatchComputeEnvironment`
2957
- - `--provider`: The cloud provider (required). Currently only `aws` is supported
2958
- - `--region`: The cloud region (required). Currently only AWS regions are supported
2955
+ - `--provider`: The cloud provider (required). Currently only supporting `aws` and `azure`.
2956
+ - `--region`: The cloud region (required). Currently only supporting aws and azure regions.
2959
2957
  - `--image-id`: The new image ID value (required)
2960
2958
  - `--image-name`: The new image name value (optional)
2961
2959
  - `--image-version`: The new image version (required)
@@ -2988,7 +2986,7 @@ cloudos procurement images reset --profile procurement_profile --image-type "Job
2988
2986
  - `--organisation-id`: The organization ID where the change will be applied (required)
2989
2987
  - `--image-type`: The Lifebit Platform resource image type (required). Same values as for `set` command
2990
2988
  - `--provider`: The cloud provider (required). Currently only `aws` is supported
2991
- - `--region`: The cloud region (required). Currently only AWS regions are supported
2989
+ - `--region`: The cloud region (required). Currently only supporting aws and azure regions.
2992
2990
  - `--disable-ssl-verification`: Disable SSL certificate verification
2993
2991
  - `--ssl-cert`: Path to your SSL certificate file
2994
2992
  - `--profile`: Profile to use from the config file
@@ -3017,7 +3015,7 @@ Executing status...
3017
3015
  Current Cromwell server status is: Stopped
3018
3016
  ```
3019
3017
 
3020
- ```bash
3018
+ ```bash
3021
3019
  # Cromwell start
3022
3020
  cloudos cromwell start --profile my_profile
3023
3021
  ```
@@ -3243,8 +3241,8 @@ responses>=0.21.0
3243
3241
  mock>=3.0.5
3244
3242
  ```
3245
3243
 
3246
- Command to run tests from the `cloudos-cli` main folder:
3244
+ Command to run tests from the `cloudos-cli` main folder:
3247
3245
 
3248
3246
  ```
3249
3247
  python -m pytest -s -v
3250
- ```
3248
+ ```
@@ -0,0 +1 @@
1
+ __version__ = '2.92.0'
@@ -1,10 +1,11 @@
1
1
  """CLI commands for Lifebit Platform procurement management."""
2
2
 
3
3
  import rich_click as click
4
+ from rich.console import Console
5
+
6
+ from cloudos_cli.configure.configure import CLOUDOS_URL, with_profile_config
4
7
  from cloudos_cli.procurement.images import Images
5
8
  from cloudos_cli.utils.resources import ssl_selector
6
- from cloudos_cli.configure.configure import with_profile_config, CLOUDOS_URL
7
- from rich.console import Console
8
9
 
9
10
 
10
11
  @click.group()
@@ -87,12 +88,10 @@ def list_images(ctx,
87
88
  type=click.Choice([
88
89
  'RegularInteractiveSessions',
89
90
  'SparkInteractiveSessions',
90
- 'RStudioInteractiveSessions',
91
- 'JupyterInteractiveSessions',
92
91
  'JobDefault',
93
92
  'NextflowBatchComputeEnvironment']))
94
- @click.option('--provider', help='The cloud provider. Only aws is supported.', required=True, type=click.Choice(['aws']), default='aws')
95
- @click.option('--region', help='The cloud region. Only aws regions are supported.', required=True)
93
+ @click.option('--provider', help='The cloud provider. Only aws and azure are supported.', required=True, type=click.Choice(['aws', 'azure']), default='aws')
94
+ @click.option('--region', help='The cloud region. Only aws and azure regions are supported.', required=True)
96
95
  @click.option('--image-id', help='The new image id value.', required=True)
97
96
  @click.option('--image-name', help='The new image name value.', required=False)
98
97
  @click.option('--image-version', help='The new image version value.', required=True)
@@ -163,12 +162,10 @@ def set_organisation_image(ctx,
163
162
  type=click.Choice([
164
163
  'RegularInteractiveSessions',
165
164
  'SparkInteractiveSessions',
166
- 'RStudioInteractiveSessions',
167
- 'JupyterInteractiveSessions',
168
165
  'JobDefault',
169
166
  'NextflowBatchComputeEnvironment']))
170
- @click.option('--provider', help='The cloud provider. Only aws is supported.', required=True, type=click.Choice(['aws']), default='aws')
171
- @click.option('--region', help='The cloud region. Only aws regions are supported.', required=True)
167
+ @click.option('--provider', help='The cloud provider. Only aws and azure are supported.', required=True, type=click.Choice(['aws', 'azure']), default='aws')
168
+ @click.option('--region', help='The cloud region. Only aws and azure regions are supported.', required=True)
172
169
  @click.option('--disable-ssl-verification',
173
170
  help=('Disable SSL certificate verification. Please, remember that this option is ' +
174
171
  'not generally recommended for security reasons.'),
@@ -4,11 +4,13 @@ This is the main class for procurement images interaction.
4
4
 
5
5
  import json
6
6
  from dataclasses import dataclass
7
- from cloudos_cli.clos import Cloudos
8
7
  from typing import Union
8
+
9
+ from cloudos_cli.clos import Cloudos
9
10
  from cloudos_cli.utils.errors import BadRequestException
10
11
  from cloudos_cli.utils.requests import retry_requests_get, retry_requests_put
11
12
 
13
+
12
14
  @dataclass
13
15
  class Images(Cloudos):
14
16
  """Class for procurement images.
@@ -92,14 +94,12 @@ class Images(Cloudos):
92
94
  The image type. Possible values are:
93
95
  RegularInteractiveSessions
94
96
  SparkInteractiveSessions
95
- RStudioInteractiveSessions
96
- JupyterInteractiveSessions
97
97
  JobDefault
98
98
  NextflowBatchComputeEnvironment
99
99
  provider
100
- The cloud provider. Currently only supporting 'aws'.
100
+ The cloud provider. Currently only supporting 'aws' and 'azure'.
101
101
  region
102
- The region. Currently only supporting aws regions.
102
+ The region. Currently only supporting aws and azure regions.
103
103
  imageId
104
104
  The new value for image Id. Required.
105
105
  imageName
@@ -149,14 +149,12 @@ class Images(Cloudos):
149
149
  The image type. Possible values are:
150
150
  RegularInteractiveSessions
151
151
  SparkInteractiveSessions
152
- RStudioInteractiveSessions
153
- JupyterInteractiveSessions
154
152
  JobDefault
155
153
  NextflowBatchComputeEnvironment
156
154
  provider
157
- The cloud provider. Currently only supporting 'aws'.
155
+ The cloud provider. Currently only supporting 'aws' and 'azure'.
158
156
  region
159
- The region. Currently only supporting aws regions.
157
+ The region. Currently only supporting aws and azure regions.
160
158
  """
161
159
 
162
160
  headers = {
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: cloudos_cli
3
- Version: 2.91.0
3
+ Version: 2.92.0
4
4
  Summary: Python package for interacting with the Lifebit Platform
5
5
  Home-page: https://github.com/lifebit-ai/cloudos-cli
6
6
  Author: David Piñeyro
@@ -231,10 +231,10 @@ This will tell you the implemented commands. Each implemented command has its ow
231
231
  ```bash
232
232
  cloudos job list --help
233
233
  ```
234
- ```console Usage: cloudos job list [OPTIONS]
235
-
236
- Collect workspace jobs from a Lifebit Platform workspace in CSV or JSON format.
237
-
234
+ ```console Usage: cloudos job list [OPTIONS]
235
+
236
+ Collect workspace jobs from a Lifebit Platform workspace in CSV or JSON format.
237
+
238
238
  ╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────╮
239
239
  │ * --apikey -k TEXT Your Lifebit Platform API key [required] │
240
240
  │ * --cloudos-url -c TEXT The Lifebit Platform url you are trying to access to. │
@@ -299,7 +299,7 @@ $HOME
299
299
 
300
300
  ### Configure Default Profile
301
301
 
302
- To facilitate the reuse of required parameters, you can create profiles.
302
+ To facilitate the reuse of required parameters, you can create profiles.
303
303
 
304
304
  To generate a profile called `default`, use the following command:
305
305
 
@@ -321,7 +321,7 @@ The same prompts will appear, including the execution platform (aws or azure). I
321
321
 
322
322
  When configuring a profile, you can specify:
323
323
  - **API Key**: Your Lifebit Platform API credentials
324
- - **Platform URL**: The Lifebit Platform instance URL
324
+ - **Platform URL**: The Lifebit Platform instance URL
325
325
  - **Project Name**: Default project for commands
326
326
  - **Execution Platform**: `aws` (default) or `azure` - determines default instance types and available features
327
327
  - **Repository Platform**: Version control system (github, gitlab, etc.)
@@ -1314,7 +1314,7 @@ cloudos job cost --profile my_profile --job-id 62c83a1191fe06013b7ef355
1314
1314
  The expected output is a formatted table showing:
1315
1315
 
1316
1316
  ```console
1317
- Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1317
+ Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1318
1318
  ┏━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━┓
1319
1319
  ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ Compute ┃ ┃
1320
1320
  ┃ ┃ Instance ┃ ┃ Life-cycle ┃ ┃ Compute ┃ Instance ┃ storage ┃ ┃
@@ -1343,7 +1343,7 @@ On page 1/2: n = next, p = prev, q = quit
1343
1343
 
1344
1344
  By pressing 'n', it will show the next page or the last if it is the case.
1345
1345
 
1346
- Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1346
+ Job Cost Details - Job ID: 62c83a1191fe06013b7ef355
1347
1347
  ┏━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━┓
1348
1348
  ┃ ┃ ┃ ┃ ┃ ┃ ┃ ┃ Compute ┃ ┃
1349
1349
  ┃ ┃ Instance ┃ ┃ Life-cycle ┃ ┃ Compute ┃ Instance ┃ storage ┃ ┃
@@ -1462,7 +1462,7 @@ The expected output is a formatted table showing:
1462
1462
  ```console
1463
1463
  Total related analyses found: 15
1464
1464
 
1465
- Related Analyses
1465
+ Related Analyses
1466
1466
  ┏━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━┳━━━━━━━━━━━━┓
1467
1467
  ┃ Status ┃ Name ┃ Owner ┃ ID ┃ Submit time ┃ Run time ┃ Total Cost ┃
1468
1468
  ┡━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━╇━━━━━━━━━━━━┩
@@ -1944,7 +1944,7 @@ Example Python Script:
1944
1944
  #!/usr/bin/python3
1945
1945
  print("Hello world")
1946
1946
  ```
1947
-
1947
+
1948
1948
  2. Or use an interpreter command in the executable field
1949
1949
 
1950
1950
  If your script doesn’t have a shebang line, you can execute it by explicitly specifying the interpreter in the executable command:
@@ -2021,7 +2021,7 @@ Interactive sessions allow you to work within the platform using different virtu
2021
2021
 
2022
2022
  You can get a list of all interactive sessions in your workspace by running `cloudos interactive-session list`. The command can produce three different output formats that can be selected using the `--output-format` option:
2023
2023
 
2024
- - **stdout** (default): Displays a table directly in the terminal with interactive pagination
2024
+ - **stdout** (default): Displays a table directly in the terminal with interactive pagination
2025
2025
  - **csv**: Saves session data to a CSV file with a minimum predefined set of columns by default, or all available columns using the `--all-fields` parameter
2026
2026
  - **json**: Saves complete session information to a JSON file with all available fields
2027
2027
 
@@ -2036,7 +2036,7 @@ cloudos interactive-session list --profile my_profile --output-format stdout
2036
2036
  The table displays sessions with pagination controls (press `n` for next page, `p` for previous page, or `q` to quit):
2037
2037
 
2038
2038
  ```console
2039
- Interactive Sessions
2039
+ Interactive Sessions
2040
2040
  ┏━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━┓
2041
2041
  ┃ Status ┃ Name ┃ Type ┃ ID ┃ Owner ┃
2042
2042
  ┡━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━┩
@@ -2646,7 +2646,7 @@ The `datasets ls` command supports different output formats using the `--output-
2646
2646
  - **`stdout` (default)**: Displays results in the console with Rich formatting
2647
2647
  - Without `--details`: Simple list of file/folder names with color coding (blue underlined for folders)
2648
2648
  - With `--details`: Rich formatted table with all file information
2649
-
2649
+
2650
2650
  - **`csv`**: Saves results to a CSV file
2651
2651
  - Without `--details`: CSV with two columns: "Name,Storage Path"
2652
2652
  - With `--details`: CSV with columns "Type, Owner, Size, Size (bytes), Last Updated, Virtual Name, Storage Path"
@@ -2696,7 +2696,7 @@ Any of the `source_path` must be a full path, starting from the `Data` datasets
2696
2696
  An example of such command is:
2697
2697
 
2698
2698
  ```
2699
- cloudos datasets mv Data/results/my_plot.png Data/plots
2699
+ cloudos datasets mv Data/results/my_plot.png Data/plots
2700
2700
  ```
2701
2701
 
2702
2702
  #### Rename Files
@@ -2707,7 +2707,7 @@ Change file and folder names while keeping them in the same location. This helps
2707
2707
  > Files and folders within the `Data` dataset can be renamed using the following command
2708
2708
 
2709
2709
  ```bash
2710
- cloudos datasets rename <path> <new_name> --profile my_profile
2710
+ cloudos datasets rename <path> <new_name> --profile my_profile
2711
2711
  ```
2712
2712
  where `path` is the full path to the file/folder to be renamed and `new_name` is just the name, no path required, as the file will not be moved.
2713
2713
 
@@ -2733,12 +2733,12 @@ or it can happen **across different projects** within the same workspace
2733
2733
  cloudos datasets cp <source_path> <destination_path> --profile <profile> --destination-project-name <project>
2734
2734
  ```
2735
2735
 
2736
- Any of the `source_path` must be a full path; any `destination_path` must be a path starting with `Data` and finishing with the folder where to move the file/folder.
2736
+ Any of the `source_path` must be a full path; any `destination_path` must be a path starting with `Data` and finishing with the folder where to move the file/folder.
2737
2737
 
2738
2738
  An example of such command is:
2739
2739
 
2740
2740
  ```
2741
- cloudos datasets cp AnalysesResults/my_analysis/results/my_plot.png Data/plots
2741
+ cloudos datasets cp AnalysesResults/my_analysis/results/my_plot.png Data/plots
2742
2742
  ```
2743
2743
 
2744
2744
 
@@ -2789,7 +2789,7 @@ Create new organizational folders within your projects to maintain structured da
2789
2789
  > New folders can be created within the `Data` dataset and its subfolders.
2790
2790
 
2791
2791
  ```bash
2792
- cloudos datasets mkdir <new_folder_path> --profile my_profile
2792
+ cloudos datasets mkdir <new_folder_path> --profile my_profile
2793
2793
  ```
2794
2794
 
2795
2795
  #### Remove Files or Folders
@@ -2797,14 +2797,14 @@ cloudos datasets mkdir <new_folder_path> --profile my_profile
2797
2797
  Remove unnecessary files or empty folders from your File Explorer. Note that this removes files from Lifebit Platform but not from underlying cloud storage.
2798
2798
 
2799
2799
  > [!NOTE]
2800
- > Files and folders can be removed in the `Data` datasets and its subfolders.
2800
+ > Files and folders can be removed in the `Data` datasets and its subfolders.
2801
2801
 
2802
2802
  ```bash
2803
2803
  cloudos datasets rm <path> --profile my_profile
2804
2804
  ```
2805
2805
  > [!NOTE]
2806
2806
  > If a file was uploaded by the user, in order to be removed you must use `--force` and that will permanently remove the file. If the file is "linked" (e.g a s3 folder or file), removing it using `cloudos datasets rm` will not remove it from the the s3 bucket.
2807
-
2807
+
2808
2808
  ---
2809
2809
 
2810
2810
  ### Link
@@ -2926,7 +2926,7 @@ To list images for a specific procurement, use the following command:
2926
2926
 
2927
2927
  ```bash
2928
2928
  cloudos procurement images ls \
2929
- -- profile procurement_profile
2929
+ -- profile procurement_profile
2930
2930
  --procurement-id "your_procurement_id_here"
2931
2931
  ```
2932
2932
 
@@ -2985,12 +2985,10 @@ cloudos procurement images set --profile procurement_profile --image-type "JobDe
2985
2985
  - `--image-type`: The Lifebit Platform resource image type (required). Possible values:
2986
2986
  - `RegularInteractiveSessions`
2987
2987
  - `SparkInteractiveSessions`
2988
- - `RStudioInteractiveSessions`
2989
- - `JupyterInteractiveSessions`
2990
2988
  - `JobDefault`
2991
2989
  - `NextflowBatchComputeEnvironment`
2992
- - `--provider`: The cloud provider (required). Currently only `aws` is supported
2993
- - `--region`: The cloud region (required). Currently only AWS regions are supported
2990
+ - `--provider`: The cloud provider (required). Currently only supporting `aws` and `azure`.
2991
+ - `--region`: The cloud region (required). Currently only supporting aws and azure regions.
2994
2992
  - `--image-id`: The new image ID value (required)
2995
2993
  - `--image-name`: The new image name value (optional)
2996
2994
  - `--image-version`: The new image version (required)
@@ -3023,7 +3021,7 @@ cloudos procurement images reset --profile procurement_profile --image-type "Job
3023
3021
  - `--organisation-id`: The organization ID where the change will be applied (required)
3024
3022
  - `--image-type`: The Lifebit Platform resource image type (required). Same values as for `set` command
3025
3023
  - `--provider`: The cloud provider (required). Currently only `aws` is supported
3026
- - `--region`: The cloud region (required). Currently only AWS regions are supported
3024
+ - `--region`: The cloud region (required). Currently only supporting aws and azure regions.
3027
3025
  - `--disable-ssl-verification`: Disable SSL certificate verification
3028
3026
  - `--ssl-cert`: Path to your SSL certificate file
3029
3027
  - `--profile`: Profile to use from the config file
@@ -3052,7 +3050,7 @@ Executing status...
3052
3050
  Current Cromwell server status is: Stopped
3053
3051
  ```
3054
3052
 
3055
- ```bash
3053
+ ```bash
3056
3054
  # Cromwell start
3057
3055
  cloudos cromwell start --profile my_profile
3058
3056
  ```
@@ -3278,8 +3276,8 @@ responses>=0.21.0
3278
3276
  mock>=3.0.5
3279
3277
  ```
3280
3278
 
3281
- Command to run tests from the `cloudos-cli` main folder:
3279
+ Command to run tests from the `cloudos-cli` main folder:
3282
3280
 
3283
3281
  ```
3284
3282
  python -m pytest -s -v
3285
- ```
3283
+ ```
@@ -1 +0,0 @@
1
- __version__ = '2.91.0'
File without changes
File without changes
File without changes