mcli-framework 7.10.1__tar.gz → 7.11.0__tar.gz

{mcli_framework-7.10.1 → mcli_framework-7.11.0}/.github/dependabot.yml

@@ -1,6 +1,3 @@
-# Dependabot configuration for automated dependency updates
-# https://docs.github.com/en/code-security/dependabot
-
 version: 2
 updates:
   # Python dependencies
@@ -16,31 +13,15 @@ updates:
       - "dependencies"
       - "python"
     commit-message:
-      prefix: "chore(deps)"
+      prefix: "chore"
       include: "scope"
-    # Group minor and patch updates
-    groups:
-      development-dependencies:
-        patterns:
-          - "pytest*"
-          - "black"
-          - "isort"
-          - "mypy"
-          - "flake8*"
-        update-types:
-          - "minor"
-          - "patch"
-      production-dependencies:
-        patterns:
-          - "*"
-        update-types:
-          - "patch"
 
   # GitHub Actions
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
       interval: "weekly"
+      day: "monday"
     open-pull-requests-limit: 5
     reviewers:
       - "gwicho38"
@@ -48,4 +29,21 @@ updates:
       - "dependencies"
       - "github-actions"
     commit-message:
-      prefix: "chore(ci)"
+      prefix: "chore"
+      include: "scope"
+
+  # Docker
+  - package-ecosystem: "docker"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+    open-pull-requests-limit: 5
+    reviewers:
+      - "gwicho38"
+    labels:
+      - "dependencies"
+      - "docker"
+    commit-message:
+      prefix: "chore"
+      include: "scope"

{mcli_framework-7.10.1 → mcli_framework-7.11.0}/.github/workflows/ci.yml

@@ -113,10 +113,19 @@ jobs:
         cd mcli_rust
         maturin develop
         
-    - name: Run Python tests
+    - name: Run Python tests with coverage
       run: |
-        pytest tests/ -v --tb=short
-        
+        pytest tests/ -v --tb=short --cov=src/mcli --cov-report=xml --cov-report=term-missing
+
+    - name: Upload coverage to Codecov
+      uses: codecov/codecov-action@v4
+      if: matrix.os == 'ubuntu-latest' && matrix.python-version == '3.11'
+      with:
+        file: ./coverage.xml
+        flags: unittests
+        name: codecov-umbrella
+        fail_ci_if_error: false
+
     - name: Test CLI functionality
       run: |
         mcli version
@@ -191,11 +200,33 @@ jobs:
   security-scan:
     name: Security Scan
     runs-on: ubuntu-latest
-    
+
     steps:
     - name: Checkout code
       uses: actions/checkout@v4
-      
+
+    - name: Set up Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: ${{ env.PYTHON_VERSION }}
+
+    - name: Install security tools
+      run: |
+        python -m pip install --upgrade pip
+        pip install bandit safety
+
+    - name: Run Bandit security linter
+      run: |
+        bandit -r src/ -f json -o bandit-report.json || true
+        bandit -r src/ -ll
+      continue-on-error: true
+
+    - name: Run Safety dependency check
+      run: |
+        safety check --json > safety-report.json || true
+        safety check
+      continue-on-error: true
+
     - name: Run Trivy vulnerability scanner
       uses: aquasecurity/trivy-action@master
       with:
@@ -203,7 +234,8 @@ jobs:
         scan-ref: '.'
         format: 'sarif'
         output: 'trivy-results.sarif'
-        
+        severity: 'CRITICAL,HIGH'
+
     - name: Upload Trivy scan results
       uses: github/codeql-action/upload-sarif@v3
       if: always()
@@ -211,6 +243,16 @@ jobs:
       with:
         sarif_file: 'trivy-results.sarif'
 
+    - name: Upload security reports
+      uses: actions/upload-artifact@v3
+      if: always()
+      with:
+        name: security-reports
+        path: |
+          bandit-report.json
+          safety-report.json
+        retention-days: 30
+
   build-package:
     name: Build Distribution Package
     runs-on: ubuntu-latest

mcli_framework-7.11.0/.github/workflows/codeql.yml

@@ -0,0 +1,43 @@
+name: CodeQL Security Analysis
+
+on:
+  push:
+    branches: [ main, develop ]
+  pull_request:
+    branches: [ main ]
+  schedule:
+    # Run at 00:00 every Sunday
+    - cron: '0 0 * * 0'
+  workflow_dispatch:
+
+jobs:
+  analyze:
+    name: Analyze Code with CodeQL
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'python' ]
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: ${{ matrix.language }}
+        queries: +security-and-quality
+
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v3
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3
+      with:
+        category: "/language:${{ matrix.language }}"

mcli_framework-7.11.0/.github/workflows/main_mcli.yml

@@ -0,0 +1,76 @@
+# Docs for the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy
+# More GitHub Actions for Azure: https://github.com/Azure/actions
+# More info on Python, GitHub Actions, and Azure App Service: https://aka.ms/python-webapps-actions
+
+name: Build and deploy Python app to Azure Web App - mcli
+
+on:
+  push:
+    branches:
+      - main
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read #This is required for actions/checkout
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python version
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.x'
+
+      # 🛠️ Local Build Section (Optional)
+      # The following section in your workflow is designed to catch build issues early on the client side, before deployment. This can be helpful for debugging and validation. However, if this step significantly increases deployment time and early detection is not critical for your workflow, you may remove this section to streamline the deployment process.
+      - name: Create and Start virtual environment and Install dependencies
+        run: |
+          python -m venv antenv
+          source antenv/bin/activate
+          pip install -r requirements.txt
+                
+      # By default, when you enable GitHub CI/CD integration through the Azure portal, the platform automatically sets the SCM_DO_BUILD_DURING_DEPLOYMENT application setting to true. This triggers the use of Oryx, a build engine that handles application compilation and dependency installation (e.g., pip install) directly on the platform during deployment. Hence, we exclude the antenv virtual environment directory from the deployment artifact to reduce the payload size. 
+      - name: Upload artifact for deployment jobs
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-app
+          path: |
+            .
+            !antenv/
+
+      # 🚫 Opting Out of Oryx Build
+      # If you prefer to disable the Oryx build process during deployment, follow these steps:
+      # 1. Remove the SCM_DO_BUILD_DURING_DEPLOYMENT app setting from your Azure App Service Environment variables.
+      # 2. Refer to sample workflows for alternative deployment strategies: https://github.com/Azure/actions-workflow-samples/tree/master/AppService
+      
+
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    permissions:
+      id-token: write #This is required for requesting the JWT
+      contents: read #This is required for actions/checkout
+
+    steps:
+      - name: Download artifact from build job
+        uses: actions/download-artifact@v4
+        with:
+          name: python-app
+      
+      - name: Login to Azure
+        uses: azure/login@v2
+        with:
+          client-id: ${{ secrets.AZUREAPPSERVICE_CLIENTID_83BA9E673F8446BE82F742FB6394A06F }}
+          tenant-id: ${{ secrets.AZUREAPPSERVICE_TENANTID_6D1336E8E2224AF899A4E08410F7A172 }}
+          subscription-id: ${{ secrets.AZUREAPPSERVICE_SUBSCRIPTIONID_921B80061CBE4DF0B9BCF8E87DA28876 }}
+
+      - name: 'Deploy to Azure Web App'
+        uses: azure/webapps-deploy@v3
+        id: deploy-to-webapp
+        with:
+          app-name: 'mcli'
+          slot-name: 'Production'
+          

{mcli_framework-7.10.1 → mcli_framework-7.11.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcli-framework
-Version: 7.10.1
+Version: 7.11.0
 Summary: Portable workflow framework - transform any script into a versioned, schedulable command. Store in ~/.mcli/commands/, version with lockfile, run as daemon or cron job.
 Author-email: Luis Fernandez de la Vara <luis@lefv.io>
 Maintainer-email: Luis Fernandez de la Vara <luis@lefv.io>
@@ -160,6 +160,11 @@ Dynamic: license-file
 
 # MCLI - Portable Workflow Framework
 
+[![codecov](https://codecov.io/gh/gwicho38/mcli/branch/main/graph/badge.svg)](https://codecov.io/gh/gwicho38/mcli)
+[![Tests](https://github.com/gwicho38/mcli/workflows/CI%2FCD%20Pipeline/badge.svg)](https://github.com/gwicho38/mcli/actions)
+[![Python Version](https://img.shields.io/badge/python-3.9%20%7C%203.10%20%7C%203.11%20%7C%203.12-blue)](https://www.python.org/downloads/)
+[![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
+
 **Transform any script into a versioned, portable, schedulable workflow command.**
 
 MCLI is a modular CLI framework that lets you write scripts once and run them anywhere - as interactive commands, scheduled jobs, or background daemons. Your workflows live in `~/.mcli/commands/`, are versioned via lockfile, and completely decoupled from the engine source code.
@@ -170,6 +175,35 @@ Write a script. Store it. Version it. Run it anywhere. Schedule it. Share it.
 
 No coupling to the engine. No vendor lock-in. Just portable workflows that work.
 
+## 🚀 Visual Workflow Editing
+
+Edit your workflow JSON files like Jupyter notebooks with our VSCode extension!
+
+[![VSCode Extension](https://img.shields.io/badge/VSCode-Extension-blue?logo=visualstudiocode)](vscode-extension/)
+[![Visual Editing](https://img.shields.io/badge/workflows-visual%20editing-brightgreen)](vscode-extension/)
+
+**Features:**
+- 📝 Cell-based editing (Jupyter-like interface)
+- ⚡ Live code execution (Python, Shell, Bash, Zsh, Fish)
+- 🎯 Monaco editor with IntelliSense
+- 📊 Rich markdown documentation cells
+- 💾 Files stay as `.json` (git-friendly)
+
+**Quick Install:**
+```bash
+# From VSCode Marketplace (pending publication)
+code --install-extension gwicho38.mcli-framework
+
+# Or install from VSIX
+code --install-extension vscode-extension/mcli-framework-1.0.0.vsix
+```
+
+**Learn More:**
+- [Extension README](vscode-extension/README.md) - Features and usage
+- [Visual Editing Guide](README-VISUAL-EDITING.md) - Quick start
+- [Installation Guide](vscode-extension/INSTALL.md) - Detailed setup
+- [Workflow Notebooks Docs](docs/workflow-notebooks.md) - Complete guide
+
 ## ⚡ Quick Start
 
 ### Installation
@@ -199,20 +233,20 @@ def app(message):
 EOF
 
 # Import as workflow
-mcli commands import-script my_task.py --name my-task --group workflow
+mcli workflow import-script my_task.py --name my-task
 
 # Run it
-mcli workflow my-task --message "Hi"
+mcli workflowss my-task --message "Hi"
 ```
 
 #### Method 2: Interactive Creation
 
 ```bash
 # Create workflow interactively
-mcli commands add my-task --group workflow
+mcli workflow add my-task
 
 # Edit in your $EDITOR, then run
-mcli workflow my-task
+mcli workflowss my-task
 ```
 
 ## 📦 Workflow System Features
@@ -223,29 +257,28 @@ Multiple ways to create workflows:
 
 ```bash
 # Import from existing Python script
-mcli commands import-script script.py --name my-workflow --group workflow
-
+mcli workflow import-script script.py --name my-workflow
 # Create new workflow interactively
-mcli commands add my-workflow --group workflow --description "Does something useful"
+mcli workflow add my-workflow --group workflow --description "Does something useful"
 
 # List all workflows
-mcli commands list-custom
+mcli workflow list-custom
 ```
 
 ### 2. **Edit & Manage Workflows**
 
 ```bash
 # Edit workflow in $EDITOR
-mcli commands edit my-workflow
+mcli workflow edit my-workflow
 
 # Show workflow details
-mcli commands info my-workflow
+mcli workflow info my-workflow
 
 # Search workflows
-mcli commands search "pdf"
+mcli workflow search "pdf"
 
 # Remove workflow
-mcli commands remove my-workflow
+mcli workflow remove my-workflow
 ```
 
 ### 3. **Export & Import (Portability)**
@@ -254,13 +287,13 @@ Share workflows across machines or with your team:
 
 ```bash
 # Export all workflows to JSON
-mcli commands export my-workflows.json
+mcli workflow export my-workflows.json
 
 # Import on another machine
-mcli commands import my-workflows.json
+mcli workflow import my-workflows.json
 
 # Export single workflow to Python script
-mcli commands export-script my-workflow --output my_workflow.py
+mcli workflow export-script my-workflow --output my_workflow.py
 ```
 
 Your workflows are just JSON files in `~/.mcli/commands/`:
@@ -279,10 +312,10 @@ MCLI automatically maintains a lockfile for reproducibility:
 
 ```bash
 # Update lockfile with current workflow versions
-mcli commands update-lockfile
+mcli workflow update-lockfile
 
 # Verify workflows match lockfile
-mcli commands verify
+mcli workflow verify
 ```
 
 Example `commands.lock.json`:
@@ -312,7 +345,7 @@ git commit -m "Update workflows"
 
 # On another machine
 git pull
-mcli commands verify  # Ensures consistency
+mcli workflow verify  # Ensures consistency
 ```
 
 ### 5. **Run as Daemon or Scheduled Task**
@@ -323,29 +356,29 @@ Workflows aren't coupled to the engine - run them however you want:
 
 ```bash
 # Start workflow as background daemon
-mcli workflow daemon start my-task-daemon --workflow my-task
+mcli workflows daemon start my-task-daemon --workflow my-task
 
 # Check daemon status
-mcli workflow daemon status
+mcli workflows daemon status
 
 # Stop daemon
-mcli workflow daemon stop my-task-daemon
+mcli workflows daemon stop my-task-daemon
 ```
 
 #### As Scheduled Task:
 
 ```bash
 # Schedule workflow to run every hour
-mcli workflow scheduler add \
+mcli workflows scheduler add \
   --name hourly-sync \
   --schedule "0 * * * *" \
   --workflow my-task
 
 # List scheduled workflows
-mcli workflow scheduler list
+mcli workflows scheduler list
 
 # View logs
-mcli workflow scheduler logs hourly-sync
+mcli workflows scheduler logs hourly-sync
 ```
 
 ## 🎨 Real-World Workflow Examples
@@ -354,12 +387,11 @@ mcli workflow scheduler logs hourly-sync
 
 ```bash
 # Create PDF processing workflow
-mcli commands import-script pdf_tool.py --name pdf --group workflow
-
+mcli workflow import-script pdf_tool.py --name pdf
 # Use it
-mcli workflow pdf extract ~/Documents/report.pdf
-mcli workflow pdf compress ~/Documents/*.pdf --output compressed/
-mcli workflow pdf split large.pdf --pages 10
+mcli workflows pdf extract ~/Documents/report.pdf
+mcli workflows pdf compress ~/Documents/*.pdf --output compressed/
+mcli workflows pdf split large.pdf --pages 10
 ```
 
 ### Example 2: Data Sync Workflow
@@ -389,13 +421,12 @@ def status():
     click.echo("Checking sync status...")
 EOF
 
-mcli commands import-script sync.py --name sync --group workflow
-
+mcli workflow import-script sync.py --name sync
 # Run manually
-mcli workflow sync backup ~/data remote:backup
+mcli workflows sync backup ~/data remote:backup
 
 # Or schedule it
-mcli workflow scheduler add \
+mcli workflows scheduler add \
   --name nightly-backup \
   --schedule "0 2 * * *" \
   --workflow "sync backup ~/data remote:backup"
@@ -405,13 +436,12 @@ mcli workflow scheduler add \
 
 ```bash
 # Already included as built-in workflow
-mcli workflow git-commit
+mcli workflows git-commit
 
 # Or create your own variant
-mcli commands export-script git-commit --output my_git_helper.py
+mcli workflow export-script git-commit --output my_git_helper.py
 # Edit my_git_helper.py to customize
-mcli commands import-script my_git_helper.py --name my-git --group workflow
-```
+mcli workflow import-script my_git_helper.py --name my-git```
 
 ## 🔧 Workflow Structure
 
@@ -437,7 +467,7 @@ Each workflow is a JSON file with this structure:
 MCLI comes with powerful built-in workflows:
 
 ```bash
-mcli workflow --help
+mcli workflows --help
 ```
 
 Available workflows:
@@ -450,7 +480,7 @@ Available workflows:
 - **redis** - Redis cache management
 - **videos** - Video processing and overlay removal
 - **sync** - Multi-cloud synchronization
-- **politician-trading** - Financial data collection (specialized)
+- **politician-trading** - Now available as standalone package: [politician-trading-tracker](https://github.com/gwicho38/politician-trading-tracker)
 
 ## 💡 Why MCLI?
 
@@ -481,8 +511,8 @@ You write scripts. They work. Then:
 mcli self completion install
 
 # Now use tab completion
-mcli workflow <TAB>          # Shows all workflows
-mcli workflow pdf <TAB>      # Shows pdf subcommands
+mcli workflows <TAB>          # Shows all workflows
+mcli workflows pdf <TAB>      # Shows pdf subcommands
 ```
 
 ### AI Chat Integration
@@ -528,10 +558,13 @@ make wheel
 
 ## 📖 Documentation
 
-- **Installation**: See [Installation Guide](docs/setup/INSTALLATION.md)
+- **📚 Documentation Index**: [Complete Documentation Index](docs/INDEX.md) - All docs organized by category
+- **Installation**: See [Installation Guide](docs/setup/INSTALL.md)
 - **Workflows**: Full workflow documentation (this README)
 - **Shell Completion**: See [Shell Completion Guide](docs/features/SHELL_COMPLETION.md)
+- **Testing**: See [Testing Guide](docs/development/TESTING.md)
 - **Contributing**: See [Contributing Guide](CONTRIBUTING.md)
+- **Release Notes**: See [Latest Release (7.10.2)](docs/releases/7.10.2.md)
 
 ## 🎯 Common Use Cases
 
@@ -539,21 +572,20 @@ make wheel
 
 ```bash
 # Create your daily automation
-mcli commands add daily-tasks --group workflow
-# Add your tasks in $EDITOR
-mcli workflow scheduler add --name daily --schedule "0 9 * * *" --workflow daily-tasks
+mcli workflow add daily-tasks# Add your tasks in $EDITOR
+mcli workflows scheduler add --name daily --schedule "0 9 * * *" --workflow daily-tasks
 ```
 
 ### Use Case 2: Team Workflow Sharing
 
 ```bash
 # On your machine
-mcli commands export team-workflows.json
+mcli workflow export team-workflows.json
 
 # Share file with team
 # On teammate's machine
-mcli commands import team-workflows.json
-mcli commands verify  # Ensure consistency
+mcli workflow import team-workflows.json
+mcli workflow verify  # Ensure consistency
 ```
 
 ### Use Case 3: CI/CD Integration
@@ -561,9 +593,9 @@ mcli commands verify  # Ensure consistency
 ```bash
 # In your CI pipeline
 - pip install mcli-framework
-- mcli commands import ci-workflows.json
-- mcli workflow build-and-test
-- mcli workflow deploy --env production
+- mcli workflow import ci-workflows.json
+- mcli workflows build-and-test
+- mcli workflows deploy --env production
 ```
 
 ## 📦 Dependencies
@@ -593,7 +625,7 @@ We welcome contributions! Especially workflow examples.
 1. Fork the repository
 2. Create feature branch: `git checkout -b feature/awesome-workflow`
 3. Create your workflow
-4. Export it: `mcli commands export my-workflow.json`
+4. Export it: `mcli workflow export my-workflow.json`
 5. Submit PR with workflow JSON
 
 ## 📄 License
@@ -612,5 +644,4 @@ MIT License - see [LICENSE](LICENSE) for details.
 
 ```bash
 pip install mcli-framework
-mcli commands add my-first-workflow --group workflow
-```
+mcli workflow add my-first-workflow```