cloudos-cli 2.95.1__tar.gz → 2.96.1__tar.gz

{cloudos_cli-2.95.1 → cloudos_cli-2.96.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cloudos_cli
-Version: 2.95.1
+Version: 2.96.1
 Summary: Python package for interacting with the Lifebit Platform
 Home-page: https://github.com/lifebit-ai/cloudos-cli
 Author: David Piñeyro
@@ -1891,7 +1891,7 @@ The `--command` parameter is required and will setup the command for the paramet
 Each `--parameter` can have a different prefix, either '--', '-', or '', depending on the use case. These can be used as many times as needed.
 
 > [!NOTE]
-> At the moment only string values are allowed to the `--parameter` options, adding a filepath at the moment does not upload/download the file. This feature will be available in a future implementation.
+> `--parameter` supports text values, File Explorer paths under `Data/`, and glob patterns. Files must already exist in the platform; local files are not uploaded. Filenames do not need an extension: `--parameter "--f1=Data/no_extension_file"` resolves the file for staging into the job's working directory. See [using files from multiple projects](#use-multiple-projects-for-files-in---parameter-option) for path formats.
 
 If everything went well, you should see something like:
 
@@ -2024,6 +2024,8 @@ The option `--parameter` could specify a file input located in a different proje
 - `-p/--parameter "--file=<project>/Data/*.txt"`
 - `-p/--parameter "--file=Data/*.txt"` (the same project as `--project-name`)
 
+These file paths also support filenames without extensions, such as `Data/no_extension_file` or `<project>/Data/subfolder/no_extension_file`, for both Bash jobs and Bash array jobs. If a referenced file does not exist, the CLI reports an error before submitting the job.
+
 The project should be specified at the beginning of the file path. For example:
 
 ```bash

{cloudos_cli-2.95.1 → cloudos_cli-2.96.1}/README.md

@@ -1856,7 +1856,7 @@ The `--command` parameter is required and will setup the command for the paramet
 Each `--parameter` can have a different prefix, either '--', '-', or '', depending on the use case. These can be used as many times as needed.
 
 > [!NOTE]
-> At the moment only string values are allowed to the `--parameter` options, adding a filepath at the moment does not upload/download the file. This feature will be available in a future implementation.
+> `--parameter` supports text values, File Explorer paths under `Data/`, and glob patterns. Files must already exist in the platform; local files are not uploaded. Filenames do not need an extension: `--parameter "--f1=Data/no_extension_file"` resolves the file for staging into the job's working directory. See [using files from multiple projects](#use-multiple-projects-for-files-in---parameter-option) for path formats.
 
 If everything went well, you should see something like:
 
@@ -1989,6 +1989,8 @@ The option `--parameter` could specify a file input located in a different proje
 - `-p/--parameter "--file=<project>/Data/*.txt"`
 - `-p/--parameter "--file=Data/*.txt"` (the same project as `--project-name`)
 
+These file paths also support filenames without extensions, such as `Data/no_extension_file` or `<project>/Data/subfolder/no_extension_file`, for both Bash jobs and Bash array jobs. If a referenced file does not exist, the CLI reports an error before submitting the job.
+
 The project should be specified at the beginning of the file path. For example:
 
 ```bash

cloudos_cli-2.96.1/cloudos_cli/_version.py

@@ -0,0 +1 @@
+__version__ = '2.96.1'

{cloudos_cli-2.95.1 → cloudos_cli-2.96.1}/cloudos_cli/jobs/job.py

@@ -1089,7 +1089,8 @@ class Job(Cloudos):
         -----
         - The function uses helper methods `extract_project`, `classify_pattern`, and `get_file_or_folder_id` to process the parameter.
         - If the parameter represents a file path or glob pattern, the function retrieves the corresponding file or folder ID from the cloud workspace.
-        - If the parameter does not match any specific pattern or file extension, it is treated as a simple text value.
+        - Paths under Data/ are resolved as files even when the filename has no extension.
+        - Other values without a pattern or file extension are treated as simple text values.
         """
 
         # split '--param_name=example_test'
@@ -1121,7 +1122,7 @@ class Job(Cloudos):
                 "parameterKind": "globPattern",
                 "folder": f"{folder}"
             }
-        elif ext:
+        elif ext or file_path.startswith('Data/'):
             if not (file_path.startswith('/Data') or file_path.startswith('Data')):
                 raise ValueError("The file path inside the project must start with '/Data' or 'Data'. ")
 

{cloudos_cli-2.95.1 → cloudos_cli-2.96.1}/cloudos_cli/utils/array_job.py

@@ -226,7 +226,8 @@ def extract_project(path):
     """
     Extracts the project name and the remaining path from a given file path.
 
-    The function assumes that a "project" exists if the path contains at least three parts
+    Paths starting with Data/ belong to the current project, regardless of their depth.
+    Otherwise, the function assumes that a "project" exists if the path contains at least three parts
     when split by slashes. If the path has fewer than three parts, the project name is
     considered empty, and the entire path is returned as the remaining path.
 
@@ -243,6 +244,8 @@ def extract_project(path):
     """
     # Strip slashes and split the path
     parts = path.strip("/").split("/")
+    if parts[0] == "Data":
+        return "", "/".join(parts)
     # A "project" exists only if there are at least 3 parts
     # globs needs more than 3 parts i.e. PROJECT/Data/Downloads/*.csv
     if (len(parts) >= 3 and not is_glob_pattern(path)) or \
@@ -251,4 +254,4 @@ def extract_project(path):
         return parts[0], "/".join(parts[1:])
     else:
         # project is empty, use the project_name of the function
-        return "", "/".join(parts)
+        return "", "/".join(parts)

{cloudos_cli-2.95.1 → cloudos_cli-2.96.1}/cloudos_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cloudos_cli
-Version: 2.95.1
+Version: 2.96.1
 Summary: Python package for interacting with the Lifebit Platform
 Home-page: https://github.com/lifebit-ai/cloudos-cli
 Author: David Piñeyro
@@ -1891,7 +1891,7 @@ The `--command` parameter is required and will setup the command for the paramet
 Each `--parameter` can have a different prefix, either '--', '-', or '', depending on the use case. These can be used as many times as needed.
 
 > [!NOTE]
-> At the moment only string values are allowed to the `--parameter` options, adding a filepath at the moment does not upload/download the file. This feature will be available in a future implementation.
+> `--parameter` supports text values, File Explorer paths under `Data/`, and glob patterns. Files must already exist in the platform; local files are not uploaded. Filenames do not need an extension: `--parameter "--f1=Data/no_extension_file"` resolves the file for staging into the job's working directory. See [using files from multiple projects](#use-multiple-projects-for-files-in---parameter-option) for path formats.
 
 If everything went well, you should see something like:
 
@@ -2024,6 +2024,8 @@ The option `--parameter` could specify a file input located in a different proje
 - `-p/--parameter "--file=<project>/Data/*.txt"`
 - `-p/--parameter "--file=Data/*.txt"` (the same project as `--project-name`)
 
+These file paths also support filenames without extensions, such as `Data/no_extension_file` or `<project>/Data/subfolder/no_extension_file`, for both Bash jobs and Bash array jobs. If a referenced file does not exist, the CLI reports an error before submitting the job.
+
 The project should be specified at the beginning of the file path. For example:
 
 ```bash

cloudos_cli-2.95.1/cloudos_cli/_version.py

@@ -1 +0,0 @@
-__version__ = '2.95.1'