dyngle 0.1.2__py3-none-any.whl → 0.2.0__py3-none-any.whl

dyngle/command/run_command.py

@@ -1,3 +1,4 @@
+import shlex
 import subprocess
 from wizlib.parser import WizParser
 
@@ -12,27 +13,27 @@ class RunCommand(DyngleCommand):
     @classmethod
     def add_args(cls, parser: WizParser):
         super().add_args(parser)
-        parser.add_argument('flow', help='Flow name to run')
+        parser.add_argument('flow', help='Operation name to run')
 
     def handle_vals(self):
         super().handle_vals()
         if not self.provided('flow'):
             self.flow = self.app.ui.get_input('Enter flow name: ')
 
-    def _validate_flow_exists(self, flows):
+    def _validate_flow_exists(self, operations):
         """Validate that the requested flow exists in configuration"""
-        if not flows:
-            raise RuntimeError('No flows configured')
+        if not operations:
+            raise RuntimeError('No operations configured')
 
-        if self.flow not in flows:
-            available_flows = ', '.join(flows.keys())
+        if self.flow not in operations:
+            available_operations = ', '.join(operations.keys())
             raise RuntimeError(
-                f'Flow "{self.flow}" not found. " + \
-                    f"Available flows: {available_flows}')
+                f'Operation "{self.flow}" not found. " + \
+                    f"Available operations: {available_operations}')
 
     def _execute_task(self, task_str):
         """Execute a single task and handle errors"""
-        task_parts = task_str.split()
+        task_parts = shlex.split(task_str)
         result = subprocess.run(task_parts)
 
         if result.returncode != 0:
@@ -41,11 +42,11 @@ class RunCommand(DyngleCommand):
 
     @DyngleCommand.wrap
     def execute(self):
-        flows = self.app.config.get('dyngle-flows')
-        self._validate_flow_exists(flows)
+        operations = self.app.config.get('dyngle-operations')
+        self._validate_flow_exists(operations)
 
-        tasks = flows[self.flow]
+        tasks = operations[self.flow]
         for task_str in tasks:
             self._execute_task(task_str)
 
-        return f'Flow "{self.flow}" completed successfully'
+        return f'Operation "{self.flow}" completed successfully'

{dyngle-0.1.2.dist-info → dyngle-0.2.0.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: dyngle
-Version: 0.1.2
+Version: 0.2.0
 Summary: Run lightweight local workflows
 License: MIT
 Author: Steampunk Wizard
@@ -21,11 +21,11 @@ Dyngle is a simple workflow runner that executes sequences of commands defined i
 
 ## Basic usage
 
-Create a configuration file (e.g., `config.yml`) with your workflows:
+Create a configuration file (e.g., `.dyngle.yml`) with your workflows:
 
 ```yaml
 dyngle:
-  flows:
+  operations:
     build:
       - python -m pip install -e .
       - python -m pytest
@@ -37,10 +37,10 @@ dyngle:
       - rm -rf .pytest_cache
 ```
 
-Run a workflow:
+Run an operation:
 
 ```bash
-dyngle --config config.yml run build
+dyngle run build
 ```
 
 ## Configuration
@@ -54,13 +54,13 @@ Dyngle reads configuration from YAML files. You can specify the config file loca
 
 ## Workflow structure
 
-Each workflow (called a "flow") is defined as a list of tasks under `dyngle.flows`. Tasks are executed sequentially using Python's subprocess module for security.
+Each operation is defined as a list of tasks under `dyngle.operations`. Tasks are executed sequentially using Python's subprocess module for security.
 
-Example with multiple flows:
+Example with multiple operations:
 
 ```yaml
 dyngle:
-  flows:
+  operations:
     test:
       - python -m unittest discover
       - python -m coverage report
@@ -75,13 +75,13 @@ dyngle:
 
 ## Security
 
-Commands are executed using Python's `subprocess.run()` with arguments split by spaces. The shell is not used, preventing shell injection attacks.
+Commands are executed using Python's `subprocess.run()` with arguments split in a shell-like fashion. The shell is not used, which reduces the likelihood of shell injection attacks. However, note that Dyngle is not robust to malicious configuration. 
 
 ## Quick installation (MacOS)
 
 ```bash
 brew install python@3.11
 python3.11 -m pip install pipx
-pipx install kwark
+pipx install dyngle
 ```
 

dyngle-0.2.0.dist-info/RECORD

@@ -0,0 +1,8 @@
+dyngle/__init__.py,sha256=2KD52sWHfMhk1g1wxHdnxjRtEKeYNJn7sTPkKRpSqNA,338
+dyngle/__main__.py,sha256=mXOQ5tiUi5mEfp1NG2viz5kW2DEeWg1oCPFhfXgxJ4U,92
+dyngle/command/__init__.py,sha256=1S86gbef8MYvG-TWD5JRIWzFg7qV5xKhp9QXx9zEx5c,94
+dyngle/command/run_command.py,sha256=UbkzqlrbAkxQSbN8lHBaTaV23xYmVBlGEOZTiiuARjo,1667
+dyngle-0.2.0.dist-info/METADATA,sha256=naF-xfNR-gcqrJGOOur2pM0gX5tRTwbrTcqfePuhntQ,2288
+dyngle-0.2.0.dist-info/WHEEL,sha256=b4K_helf-jlQoXBBETfwnf4B04YC67LOev0jo4fX5m8,88
+dyngle-0.2.0.dist-info/entry_points.txt,sha256=rekiGhtweiHKm9g1jdGb3FhzqDrk1kigJDeSNollZSA,48
+dyngle-0.2.0.dist-info/RECORD,,

dyngle-0.1.2.dist-info/RECORD

@@ -1,8 +0,0 @@
-dyngle/__init__.py,sha256=2KD52sWHfMhk1g1wxHdnxjRtEKeYNJn7sTPkKRpSqNA,338
-dyngle/__main__.py,sha256=mXOQ5tiUi5mEfp1NG2viz5kW2DEeWg1oCPFhfXgxJ4U,92
-dyngle/command/__init__.py,sha256=1S86gbef8MYvG-TWD5JRIWzFg7qV5xKhp9QXx9zEx5c,94
-dyngle/command/run_command.py,sha256=89GMbVcjqLLTRLvF9fVr5ehzC-1aoznS-mN2L5zzpBk,1574
-dyngle-0.1.2.dist-info/METADATA,sha256=up7gMCVwJPMWk7gYRQxcf5X9fROikh9OpIgY9XepT_4,2197
-dyngle-0.1.2.dist-info/WHEEL,sha256=b4K_helf-jlQoXBBETfwnf4B04YC67LOev0jo4fX5m8,88
-dyngle-0.1.2.dist-info/entry_points.txt,sha256=rekiGhtweiHKm9g1jdGb3FhzqDrk1kigJDeSNollZSA,48
-dyngle-0.1.2.dist-info/RECORD,,