splight-cli 4.10.0__tar.gz → 4.11.1__tar.gz

{splight_cli-4.10.0 → splight_cli-4.11.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: splight-cli
-Version: 4.10.0
+Version: 4.11.1
 Summary: Splight Command Line Interface
 Author: Splight Dev
 Author-email: dev@splight-ae.com
@@ -21,16 +21,13 @@ Requires-Dist: py7zr (==0.20.8)
 Requires-Dist: requests (==2.31.0)
 Requires-Dist: rich (==13.0.1)
 Requires-Dist: setuptools (==60.9.3)
-Requires-Dist: splight-lib (>=5.2.2,<6.0.0)
+Requires-Dist: splight-lib (>=5.4.1,<6.0.0)
 Requires-Dist: toposort (>=1.10,<2.0)
 Requires-Dist: typer (==0.9.0)
 Description-Content-Type: text/markdown
 
 # Splight CLI
 
-![snyk_code](https://github.com/splightplatform/splight-cli/blob/gh-pages/snyk_code.svg?raw=True)
-![snyk_dependencies](https://github.com/splightplatform/splight-cli/blob/gh-pages/snyk_dependencies.svg?raw=True)
-
 ---
 
 ## Table of Content
@@ -75,6 +72,7 @@ pip install splight-cli
 ```
 
 Once you have installed `splight-cli` you can check the installation with
+
 ```bash
 splight --version
 ```
@@ -250,12 +248,15 @@ You can also retrieve one of the parameters using the `get` command:
 ```bash
 splight configure get <parameter>
 ```
+
 for example for reading the `SPLIGHT_PLATFORM_API_HOST`:
+
 ```bash
 splight configure get splight_platform_api_host
 ```
 
 In the same way you can modify one parameter using the `set` command
+
 ```bash
 splight configure set <parameter> <value>
 ```
@@ -310,6 +311,7 @@ The `engine` command is used for interacting with the Splight Engine. So far, th
 subcommands provide an interface for creating, reaading and deleting resources in the engine.
 
 The command is
+
 ```bash
 splight engine <subcommand> <action> [extra args]
 ```
@@ -318,6 +320,7 @@ depending on the which sub-command you use you can get different actions
 to perform
 
 The valid sub-commands so far are:
+
 - `asset`
 - `attribute`
 - `component`
@@ -343,7 +346,7 @@ The available subcommands are
 
 - `create <name>` to create a new workspace. After the creation of a new worskpace you need to configure _Splight CLI_ with `splight configure`.
 - `delete <name>` to delete an existing workspace.
-- `list` to list all workspaces. Current workspace displays a '*' to the left.
+- `list` to list all workspaces. Current workspace displays a '\*' to the left.
 - `select <name>` to switch between different configured workspaces.
 - `show <name>` to display the contents of an existing workspace.
 
@@ -579,10 +582,10 @@ splight component run <component directory> --local
 ```
 
 This way, the component will run using local clients for database and datalake. This is extremely
-useful for development since you can create instances of the different database objects in the 
-local database for running different scenearios or differents tests. The same can be applied for 
+useful for development since you can create instances of the different database objects in the
+local database for running different scenearios or differents tests. The same can be applied for
 datalake data, the local client stores the data in files. In both cases, for database and datalake,
-the files are created in the same directory as the `__init__.py` file of the component, so you 
+the files are created in the same directory as the `__init__.py` file of the component, so you
 can modified it based on your needs.
 
 You can interact with the local databases using the library, for example
@@ -604,3 +607,4 @@ db_client.save(attribute)
 
 df = client.get_dataframe(Number, asset=all_assets[0].id, attribute=attribute.id)
 ```
+

{splight_cli-4.10.0 → splight_cli-4.11.1}/README.md

@@ -1,8 +1,5 @@
 # Splight CLI
 
-![snyk_code](https://github.com/splightplatform/splight-cli/blob/gh-pages/snyk_code.svg?raw=True)
-![snyk_dependencies](https://github.com/splightplatform/splight-cli/blob/gh-pages/snyk_dependencies.svg?raw=True)
-
 ---
 
 ## Table of Content
@@ -47,6 +44,7 @@ pip install splight-cli
 ```
 
 Once you have installed `splight-cli` you can check the installation with
+
 ```bash
 splight --version
 ```
@@ -222,12 +220,15 @@ You can also retrieve one of the parameters using the `get` command:
 ```bash
 splight configure get <parameter>
 ```
+
 for example for reading the `SPLIGHT_PLATFORM_API_HOST`:
+
 ```bash
 splight configure get splight_platform_api_host
 ```
 
 In the same way you can modify one parameter using the `set` command
+
 ```bash
 splight configure set <parameter> <value>
 ```
@@ -282,6 +283,7 @@ The `engine` command is used for interacting with the Splight Engine. So far, th
 subcommands provide an interface for creating, reaading and deleting resources in the engine.
 
 The command is
+
 ```bash
 splight engine <subcommand> <action> [extra args]
 ```
@@ -290,6 +292,7 @@ depending on the which sub-command you use you can get different actions
 to perform
 
 The valid sub-commands so far are:
+
 - `asset`
 - `attribute`
 - `component`
@@ -315,7 +318,7 @@ The available subcommands are
 
 - `create <name>` to create a new workspace. After the creation of a new worskpace you need to configure _Splight CLI_ with `splight configure`.
 - `delete <name>` to delete an existing workspace.
-- `list` to list all workspaces. Current workspace displays a '*' to the left.
+- `list` to list all workspaces. Current workspace displays a '\*' to the left.
 - `select <name>` to switch between different configured workspaces.
 - `show <name>` to display the contents of an existing workspace.
 
@@ -551,10 +554,10 @@ splight component run <component directory> --local
 ```
 
 This way, the component will run using local clients for database and datalake. This is extremely
-useful for development since you can create instances of the different database objects in the 
-local database for running different scenearios or differents tests. The same can be applied for 
+useful for development since you can create instances of the different database objects in the
+local database for running different scenearios or differents tests. The same can be applied for
 datalake data, the local client stores the data in files. In both cases, for database and datalake,
-the files are created in the same directory as the `__init__.py` file of the component, so you 
+the files are created in the same directory as the `__init__.py` file of the component, so you
 can modified it based on your needs.
 
 You can interact with the local databases using the library, for example
@@ -575,4 +578,4 @@ attribute = Attribute(name="SomeAttribute")
 db_client.save(attribute)
 
 df = client.get_dataframe(Number, asset=all_assets[0].id, attribute=attribute.id)
-```
+```

{splight_cli-4.10.0 → splight_cli-4.11.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "splight-cli"
-version = "4.10.0"
+version = "4.11.1"
 description = "Splight Command Line Interface"
 authors = ["Splight Dev <dev@splight-ae.com>"]
 readme = "README.md"
@@ -11,7 +11,7 @@ case-converter = "1.1.0"
 click = "8.0.4"
 click-default-group = "1.2.2"
 setuptools = "60.9.3"
-splight-lib = "^5.2.2"
+splight-lib = "^5.4.1"
 py7zr = "0.20.8"
 typer = "0.9.0"
 colorama = "0.4.4"

{splight_cli-4.10.0 → splight_cli-4.11.1}/splight_cli/hub/component/hub_manager.py

@@ -76,7 +76,8 @@ class HubComponentManager:
         if not components:
             raise HubComponentNotFound(name, version)
 
-        component_data = components[0].download()
+        component_file_wrapper = components[0].download()
+        component_data = component_file_wrapper.read()
 
         # TODO: search for a better approach
         version_modified = version.replace(".", "_")

{splight_cli-4.10.0 → splight_cli-4.11.1}/splight_cli/hub/component/tests/test_hub_manager.py

@@ -109,7 +109,11 @@ def test_push_already_exists_with_force(mock_exists, mock_component_manager):
 
 
 @patch.object(HubComponent, "list_mine", return_value=[HUB_COMPONENT])
-@patch.object(HubComponent, "download", return_value=b"This is a component")
+@patch.object(
+    HubComponent,
+    "download",
+    return_value=open(os.path.join(TEST_COMPONENT_PATH, "spec.json"), "r"),
+)
 @patch("builtins.open", new_callable=mock_open())
 @patch("py7zr.SevenZipFile")
 @patch("shutil.move", return_value=None)