agentic-devtools 0.2.2__tar.gz → 0.2.4__tar.gz

{agentic_devtools-0.2.2 → agentic_devtools-0.2.4}/.github/workflows/test.yml

@@ -36,6 +36,10 @@ jobs:
           python -m pip install --upgrade pip
           pip install -e ".[dev]"
       
+      - name: Validate 1:1:1 test structure
+        run: |
+          python scripts/validate_test_structure.py
+
       - name: Run tests with pytest
         run: |
           pytest --cov=agentic_devtools --cov-report=term-missing

{agentic_devtools-0.2.2 → agentic_devtools-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentic-devtools
-Version: 0.2.2
+Version: 0.2.4
 Summary: AI assistant helper commands for the Dragonfly platform
 Author: Dragonfly Team
 License-Expression: MIT
@@ -174,39 +174,190 @@ agdt-show
 
 ## Azure DevOps Commands
 
+All Azure DevOps commands support both CLI parameters and state-based execution.
+Parameters passed via CLI are automatically persisted to state for reuse.
+
 ### Reply to PR Thread
 
 ```bash
-agdt-set pr_id 23046
+# Option A: With CLI parameters (explicit, self-documenting)
+agdt-reply-to-pull-request-thread --pull-request-id 23046 --thread-id 139474 --content "Your reply"
+agdt-reply-to-pull-request-thread -p 23046 -t 139474 -c "Thanks!"
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
 agdt-set thread_id 139474
 agdt-set content "Your reply message"
-agdt-reply-to-pr-thread
+agdt-reply-to-pull-request-thread
 
 # Optionally resolve the thread after replying
 agdt-set resolve_thread true
-agdt-reply-to-pr-thread
-```text
+agdt-reply-to-pull-request-thread
+```
 
 ### Add New PR Comment
 
 ```bash
-agdt-set pr_id 23046
+# Option A: With CLI parameters (explicit)
+agdt-add-pull-request-comment --pull-request-id 23046 --content "LGTM!"
+agdt-add-pull-request-comment -p 23046 -c "Looks good"
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
 agdt-set content "Your comment"
-agdt-add-pr-comment
+agdt-add-pull-request-comment
 
 # For file-level comment
 agdt-set path "src/example.py"
 agdt-set line 42
-agdt-add-pr-comment
-```text
+agdt-add-pull-request-comment
+```
+
+### Approve Pull Request
+
+```bash
+# Option A: With CLI parameters
+agdt-approve-pull-request --pull-request-id 23046 --content "Approved!"
+agdt-approve-pull-request -p 23046
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
+agdt-approve-pull-request
+```
+
+### Get PR Threads
+
+```bash
+# Option A: With CLI parameter
+agdt-get-pull-request-threads --pull-request-id 23046
+agdt-get-pull-request-threads -p 23046
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
+agdt-get-pull-request-threads
+```
+
+### Resolve Thread
+
+```bash
+# Option A: With CLI parameters
+agdt-resolve-thread --pull-request-id 23046 --thread-id 139474
+agdt-resolve-thread -p 23046 -t 139474
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
+agdt-set thread_id 139474
+agdt-resolve-thread
+```
 
 ### Dry Run Mode
 
 ```bash
 agdt-set dry_run true
-agdt-reply-to-pr-thread  # Previews without making API calls
+agdt-reply-to-pull-request-thread  # Previews without making API calls
+```
+
+## Azure Context Management
+
+Manage multiple Azure CLI accounts (e.g., corporate account for Azure DevOps and AZA account for App Insights) without repeated `az login` / `az logout` cycles.
+
+### Overview
+
+The Azure context system uses separate `AZURE_CONFIG_DIR` directories per account context. Both accounts can stay authenticated simultaneously and can be switched instantly via environment variable.
+
+**Available Contexts:**
+
+- `devops` - Corporate account for Azure DevOps, Service Bus, etc.
+- `resources` - AZA account for App Insights, Azure resources, Terraform, etc.
+
+### Setup
+
+1. **Switch to a context** (one-time setup per context):
+
+```bash
+# Switch to DevOps context
+agdt-azure-context-use devops
+
+# Switch to resources context
+agdt-azure-context-use resources
+```text
+
+2. **Log in to each context** (one-time per context):
+
+```bash
+# After switching to a context, log in using Azure CLI
+az login
+# This login is stored in the context's isolated config directory
+```text
+
+### Usage
+
+**Show all contexts with login status:**
+
+```bash
+agdt-azure-context-status
+```text
+
+Output:
+```text
+Azure CLI Contexts:
+================================================================================
+
+devops [ACTIVE]
+  Description: Corporate account for Azure DevOps, Service Bus, etc.
+  Config Dir:  ~/.azure-contexts/devops
+  Status:      ✓ Logged in as user@company.com
+
+resources
+  Description: AZA account for App Insights, Azure resources, Terraform, etc.
+  Config Dir:  ~/.azure-contexts/resources
+  Status:      ✓ Logged in as user@company.com
+
+================================================================================
+```text
+
+**Check current active context:**
+
+```bash
+agdt-azure-context-current
+```text
+
+**Switch contexts:**
+
+```bash
+# Switch to DevOps context
+agdt-azure-context-use devops
+
+# Switch to resources context
+agdt-azure-context-use resources
 ```text
 
+**Ensure logged in (prompts if needed):**
+
+```bash
+# Ensure current context is logged in
+agdt-azure-context-ensure-login
+
+# Ensure specific context is logged in
+agdt-azure-context-ensure-login devops
+```text
+
+### How It Works
+
+Each context uses its own isolated Azure CLI configuration directory:
+- `~/.azure-contexts/devops/` - DevOps context config and tokens
+- `~/.azure-contexts/resources/` - Resources context config and tokens
+
+When you run `az` commands, the active context's `AZURE_CONFIG_DIR` is used, so both accounts stay authenticated simultaneously. Switching contexts is instant (no browser login flow).
+
+### Integration
+
+**With VPN toggle:**
+Contexts work seamlessly with the VPN toggle system. When certain contexts require VPN, the system coordinates VPN state automatically.
+
+**With Azure CLI:**
+All `az` commands respect the active context automatically via the `AZURE_CONFIG_DIR` environment variable.
+
 ## Git Commands
 
 The package provides streamlined Git workflow commands that support the
@@ -428,6 +579,97 @@ agdt-set jira.dry_run true
 agdt-create-issue  # Previews payload without API call
 ```text
 
+## VPN & Network Management
+
+The corporate VPN (Pulse Secure/Ivanti) creates a full tunnel that blocks public registries (npm, PyPI) while being required for internal resources (Jira, ESB). These commands provide intelligent VPN management so you don't need to manually connect/disconnect VPN when switching between tasks.
+
+### Network Status
+
+Check your current network context:
+
+```bash
+agdt-network-status
+```
+
+Output shows:
+
+- 🏢 Corporate network (in office) - VPN operations skipped automatically
+- 🔌 Remote with VPN - Can access internal resources, external blocked
+- 📡 Remote without VPN - Can access external resources, internal blocked
+
+### Run Command with VPN Context
+
+Automatically manage VPN based on command requirements:
+
+```bash
+# Ensure VPN is connected before running (for Jira, ESB, etc.)
+agdt-vpn-run --require-vpn "curl https://jira.swica.ch/rest/api/2/issue/DP-123"
+
+# Temporarily disconnect VPN for public access (npm, pip, etc.)
+agdt-vpn-run --require-public "npm install"
+
+# Auto-detect requirement from command content (default)
+agdt-vpn-run --smart "az devops ..."
+agdt-vpn-run "npm install express"  # --smart is the default
+```
+
+The command will:
+
+- Detect if you're on corporate network (in office) and skip VPN operations
+- Connect VPN if needed for internal resources
+- Disconnect VPN temporarily for public registry access
+- Restore VPN state after command completes
+
+### Manual VPN Control
+
+Direct VPN control commands (run in background):
+
+```bash
+# Connect VPN (skipped if on corporate network)
+agdt-vpn-on
+agdt-task-wait
+
+# Disconnect VPN
+agdt-vpn-off
+agdt-task-wait
+
+# Check VPN status
+agdt-vpn-status
+agdt-task-wait
+```
+
+### Common Workflows
+
+**Install npm packages (needs public access):**
+
+```bash
+agdt-vpn-run --require-public "npm install"
+```
+
+**Access Jira API (needs VPN):**
+
+```bash
+agdt-vpn-run --require-vpn "curl https://jira.swica.ch/rest/api/2/serverInfo"
+```
+
+**Smart detection (recommended):**
+
+```bash
+# Auto-detects that npm install needs public access
+agdt-vpn-run "npm install express lodash"
+
+# Auto-detects that Jira URL needs VPN
+agdt-vpn-run "curl https://jira.swica.ch/rest/api/2/issue/DP-123"
+```
+
+### In-Office Behavior
+
+When on the corporate network (physically in the office), VPN operations are
+automatically skipped since internal resources are already accessible. However,
+note that the corporate network may still block external registries (npm, PyPI) -
+in that case, consider connecting to a different network (e.g., mobile hotspot)
+for external access.
+
 ## Environment Variables
 
 | Variable                    | Purpose

{agentic_devtools-0.2.2 → agentic_devtools-0.2.4}/README.md

@@ -149,39 +149,190 @@ agdt-show
 
 ## Azure DevOps Commands
 
+All Azure DevOps commands support both CLI parameters and state-based execution.
+Parameters passed via CLI are automatically persisted to state for reuse.
+
 ### Reply to PR Thread
 
 ```bash
-agdt-set pr_id 23046
+# Option A: With CLI parameters (explicit, self-documenting)
+agdt-reply-to-pull-request-thread --pull-request-id 23046 --thread-id 139474 --content "Your reply"
+agdt-reply-to-pull-request-thread -p 23046 -t 139474 -c "Thanks!"
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
 agdt-set thread_id 139474
 agdt-set content "Your reply message"
-agdt-reply-to-pr-thread
+agdt-reply-to-pull-request-thread
 
 # Optionally resolve the thread after replying
 agdt-set resolve_thread true
-agdt-reply-to-pr-thread
-```text
+agdt-reply-to-pull-request-thread
+```
 
 ### Add New PR Comment
 
 ```bash
-agdt-set pr_id 23046
+# Option A: With CLI parameters (explicit)
+agdt-add-pull-request-comment --pull-request-id 23046 --content "LGTM!"
+agdt-add-pull-request-comment -p 23046 -c "Looks good"
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
 agdt-set content "Your comment"
-agdt-add-pr-comment
+agdt-add-pull-request-comment
 
 # For file-level comment
 agdt-set path "src/example.py"
 agdt-set line 42
-agdt-add-pr-comment
-```text
+agdt-add-pull-request-comment
+```
+
+### Approve Pull Request
+
+```bash
+# Option A: With CLI parameters
+agdt-approve-pull-request --pull-request-id 23046 --content "Approved!"
+agdt-approve-pull-request -p 23046
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
+agdt-approve-pull-request
+```
+
+### Get PR Threads
+
+```bash
+# Option A: With CLI parameter
+agdt-get-pull-request-threads --pull-request-id 23046
+agdt-get-pull-request-threads -p 23046
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
+agdt-get-pull-request-threads
+```
+
+### Resolve Thread
+
+```bash
+# Option A: With CLI parameters
+agdt-resolve-thread --pull-request-id 23046 --thread-id 139474
+agdt-resolve-thread -p 23046 -t 139474
+
+# Option B: Parameterless (uses current state)
+agdt-set pull_request_id 23046
+agdt-set thread_id 139474
+agdt-resolve-thread
+```
 
 ### Dry Run Mode
 
 ```bash
 agdt-set dry_run true
-agdt-reply-to-pr-thread  # Previews without making API calls
+agdt-reply-to-pull-request-thread  # Previews without making API calls
+```
+
+## Azure Context Management
+
+Manage multiple Azure CLI accounts (e.g., corporate account for Azure DevOps and AZA account for App Insights) without repeated `az login` / `az logout` cycles.
+
+### Overview
+
+The Azure context system uses separate `AZURE_CONFIG_DIR` directories per account context. Both accounts can stay authenticated simultaneously and can be switched instantly via environment variable.
+
+**Available Contexts:**
+
+- `devops` - Corporate account for Azure DevOps, Service Bus, etc.
+- `resources` - AZA account for App Insights, Azure resources, Terraform, etc.
+
+### Setup
+
+1. **Switch to a context** (one-time setup per context):
+
+```bash
+# Switch to DevOps context
+agdt-azure-context-use devops
+
+# Switch to resources context
+agdt-azure-context-use resources
+```text
+
+2. **Log in to each context** (one-time per context):
+
+```bash
+# After switching to a context, log in using Azure CLI
+az login
+# This login is stored in the context's isolated config directory
+```text
+
+### Usage
+
+**Show all contexts with login status:**
+
+```bash
+agdt-azure-context-status
+```text
+
+Output:
+```text
+Azure CLI Contexts:
+================================================================================
+
+devops [ACTIVE]
+  Description: Corporate account for Azure DevOps, Service Bus, etc.
+  Config Dir:  ~/.azure-contexts/devops
+  Status:      ✓ Logged in as user@company.com
+
+resources
+  Description: AZA account for App Insights, Azure resources, Terraform, etc.
+  Config Dir:  ~/.azure-contexts/resources
+  Status:      ✓ Logged in as user@company.com
+
+================================================================================
+```text
+
+**Check current active context:**
+
+```bash
+agdt-azure-context-current
+```text
+
+**Switch contexts:**
+
+```bash
+# Switch to DevOps context
+agdt-azure-context-use devops
+
+# Switch to resources context
+agdt-azure-context-use resources
 ```text
 
+**Ensure logged in (prompts if needed):**
+
+```bash
+# Ensure current context is logged in
+agdt-azure-context-ensure-login
+
+# Ensure specific context is logged in
+agdt-azure-context-ensure-login devops
+```text
+
+### How It Works
+
+Each context uses its own isolated Azure CLI configuration directory:
+- `~/.azure-contexts/devops/` - DevOps context config and tokens
+- `~/.azure-contexts/resources/` - Resources context config and tokens
+
+When you run `az` commands, the active context's `AZURE_CONFIG_DIR` is used, so both accounts stay authenticated simultaneously. Switching contexts is instant (no browser login flow).
+
+### Integration
+
+**With VPN toggle:**
+Contexts work seamlessly with the VPN toggle system. When certain contexts require VPN, the system coordinates VPN state automatically.
+
+**With Azure CLI:**
+All `az` commands respect the active context automatically via the `AZURE_CONFIG_DIR` environment variable.
+
 ## Git Commands
 
 The package provides streamlined Git workflow commands that support the
@@ -403,6 +554,97 @@ agdt-set jira.dry_run true
 agdt-create-issue  # Previews payload without API call
 ```text
 
+## VPN & Network Management
+
+The corporate VPN (Pulse Secure/Ivanti) creates a full tunnel that blocks public registries (npm, PyPI) while being required for internal resources (Jira, ESB). These commands provide intelligent VPN management so you don't need to manually connect/disconnect VPN when switching between tasks.
+
+### Network Status
+
+Check your current network context:
+
+```bash
+agdt-network-status
+```
+
+Output shows:
+
+- 🏢 Corporate network (in office) - VPN operations skipped automatically
+- 🔌 Remote with VPN - Can access internal resources, external blocked
+- 📡 Remote without VPN - Can access external resources, internal blocked
+
+### Run Command with VPN Context
+
+Automatically manage VPN based on command requirements:
+
+```bash
+# Ensure VPN is connected before running (for Jira, ESB, etc.)
+agdt-vpn-run --require-vpn "curl https://jira.swica.ch/rest/api/2/issue/DP-123"
+
+# Temporarily disconnect VPN for public access (npm, pip, etc.)
+agdt-vpn-run --require-public "npm install"
+
+# Auto-detect requirement from command content (default)
+agdt-vpn-run --smart "az devops ..."
+agdt-vpn-run "npm install express"  # --smart is the default
+```
+
+The command will:
+
+- Detect if you're on corporate network (in office) and skip VPN operations
+- Connect VPN if needed for internal resources
+- Disconnect VPN temporarily for public registry access
+- Restore VPN state after command completes
+
+### Manual VPN Control
+
+Direct VPN control commands (run in background):
+
+```bash
+# Connect VPN (skipped if on corporate network)
+agdt-vpn-on
+agdt-task-wait
+
+# Disconnect VPN
+agdt-vpn-off
+agdt-task-wait
+
+# Check VPN status
+agdt-vpn-status
+agdt-task-wait
+```
+
+### Common Workflows
+
+**Install npm packages (needs public access):**
+
+```bash
+agdt-vpn-run --require-public "npm install"
+```
+
+**Access Jira API (needs VPN):**
+
+```bash
+agdt-vpn-run --require-vpn "curl https://jira.swica.ch/rest/api/2/serverInfo"
+```
+
+**Smart detection (recommended):**
+
+```bash
+# Auto-detects that npm install needs public access
+agdt-vpn-run "npm install express lodash"
+
+# Auto-detects that Jira URL needs VPN
+agdt-vpn-run "curl https://jira.swica.ch/rest/api/2/issue/DP-123"
+```
+
+### In-Office Behavior
+
+When on the corporate network (physically in the office), VPN operations are
+automatically skipped since internal resources are already accessible. However,
+note that the corporate network may still block external registries (npm, PyPI) -
+in that case, consider connecting to a different network (e.g., mobile hotspot)
+for external access.
+
 ## Environment Variables
 
 | Variable                    | Purpose

{agentic_devtools-0.2.2 → agentic_devtools-0.2.4}/agentic_devtools/_version.py

@@ -28,7 +28,7 @@ version_tuple: VERSION_TUPLE
 commit_id: COMMIT_ID
 __commit_id__: COMMIT_ID
 
-__version__ = version = '0.2.2'
-__version_tuple__ = version_tuple = (0, 2, 2)
+__version__ = version = '0.2.4'
+__version_tuple__ = version_tuple = (0, 2, 4)
 
 __commit_id__ = commit_id = None

agentic_devtools-0.2.4/agentic_devtools/cli/azure_context/__init__.py

@@ -0,0 +1,29 @@
+"""
+Azure CLI context management for multi-account support.
+
+Exports all public functions for managing Azure CLI contexts.
+"""
+
+from agentic_devtools.cli.azure_context.config import (
+    AzureContext,
+    AzureContextConfig,
+    get_context_config,
+)
+from agentic_devtools.cli.azure_context.management import (
+    ensure_logged_in,
+    get_current_context,
+    run_with_context,
+    show_all_contexts,
+    switch_context,
+)
+
+__all__ = [
+    "AzureContext",
+    "AzureContextConfig",
+    "get_context_config",
+    "ensure_logged_in",
+    "get_current_context",
+    "run_with_context",
+    "show_all_contexts",
+    "switch_context",
+]