awsquery 0.1.0__tar.gz → 0.2.0__tar.gz

{awsquery-0.1.0 → awsquery-0.2.0}/.claude/settings.local.json

@@ -1,7 +1,9 @@
 {
   "permissions": {
     "allow": [
-      "Bash(python3 -m pytest tests/ --cov=src/awsquery --cov-report=term-missing -q)"
+      "Bash(python3 -m pytest tests/ --cov=src/awsquery --cov-report=term-missing -q)",
+      "Bash(mutmut show:*)",
+      "Bash(mutmut:*)"
     ],
     "deny": [],
     "ask": []

awsquery-0.2.0/.dockerignore

@@ -0,0 +1,52 @@
+# Ignore sample responses directory during build
+sample-responses/
+
+# Ignore temporary files and caches
+*.pyc
+__pycache__/
+.pytest_cache/
+*.egg-info/
+.mutmut-cache/
+htmlcov/
+.coverage
+coverage.xml
+
+# Ignore git and IDE files
+.git/
+.gitignore
+.vscode/
+.idea/
+.claude/
+
+# Ignore development and analysis files
+scripts/
+mutants/
+docs/
+awsinfo/
+*.log
+*.csv
+
+# Ignore temporary/development files
+core
+Name
+*.backup
+*.backup.md
+test_*.md
+*Plan*.md
+Todo.md
+Initial.md
+FixPlan.md
+.envrc
+
+# Ignore documentation (except essential README)
+*.md
+!README.md
+
+# Ignore Docker files themselves
+Dockerfile
+Dockerfile.prod
+docker-compose.yml
+.dockerignore
+
+# Ignore setup scripts that aren't needed in container
+setup-autocomplete.sh

{awsquery-0.1.0 → awsquery-0.2.0}/.gitignore

@@ -159,6 +159,12 @@ venv.bak/
 .dmypy.json
 dmypy.json
 
+# mutmut
+.mutmut-cache
+.mutmutrc
+html/
+mutants
+
 # Pyre type checker
 .pyre/
 

{awsquery-0.1.0 → awsquery-0.2.0}/CLAUDE.md

@@ -65,10 +65,85 @@ The tool enforces security through a comprehensive `policy.json` file that defin
 
 ### Testing Structure
 - Unit tests in `tests/unit/` with `@pytest.mark.unit`
-- Integration tests in `tests/integration/` with `@pytest.mark.integration` 
+- Integration tests in `tests/integration/` with `@pytest.mark.integration`
 - Critical path tests marked with `@pytest.mark.critical`
 - AWS mocks using moto library marked with `@pytest.mark.aws`
 
+### STRICT Testing Requirements - MUST FOLLOW
+
+#### 🚫 PROHIBITED: Test Anti-Patterns
+**NEVER CREATE:**
+1. **Duplicate Test Files**: Before creating ANY test file, search for existing tests covering the same functionality
+   - Flag tests: Use `test_cli_flags.py` ONLY
+   - Parser tests: Use `test_cli_parser.py` ONLY
+   - Filter tests: Use `test_filter_implementation.py` for real tests, `test_filter_matching.py` for patterns
+2. **Over-Mocked Tests**: Tests that mock the very functions they claim to test
+3. **Mock Assertion Tests**: Tests that only verify `mock.assert_called()` without testing actual behavior
+4. **Nested Mock Contexts**: More than 2 levels of `with patch()` indicates over-mocking
+
+#### ✅ REQUIRED: Test Best Practices
+**ALWAYS:**
+1. **Test Real Implementation**:
+   ```python
+   # GOOD: Tests actual function
+   result = filter_resources(real_data, ["filter"])
+   assert len(result) == expected
+
+   # BAD: Only tests mock
+   mock_filter.return_value = []
+   mock_filter.assert_called_once()
+   ```
+
+2. **Minimal Mocking**: Only mock external dependencies (boto3, file I/O, network)
+   ```python
+   # GOOD: Only mock AWS
+   @patch("boto3.client")
+   def test_feature(mock_client):
+       # Test real code with mocked AWS
+
+   # BAD: Mock everything
+   @patch("filter_resources")
+   @patch("format_output")
+   @patch("parse_args")
+   ```
+
+3. **Consolidate Related Tests**: Group similar tests in one file
+   - All flag position tests → `test_cli_flags.py`
+   - All parser tests → `test_cli_parser.py`
+   - All filter implementation → `test_filter_implementation.py`
+
+4. **Test Edge Cases**: Include malformed input, Unicode, empty values
+   ```python
+   # Test edge cases
+   test_cases = ["", None, "^$", "ˆ", "$^", "^^$$"]
+   ```
+
+5. **Verify Actual Output**: Check real results, not mock calls
+   ```python
+   # GOOD: Verify actual JSON
+   output = format_json_output(data, filters)
+   parsed = json.loads(output)  # Ensures valid JSON
+
+   # BAD: Only check mock called
+   mock_json.assert_called_once()
+   ```
+
+#### 📋 Test Review Checklist
+Before committing ANY test:
+1. ❓ Does a test file for this feature already exist?
+2. ❓ Am I testing real code or just mocks?
+3. ❓ Do assertions verify actual behavior?
+4. ❓ Is mocking limited to external dependencies only?
+5. ❓ Are edge cases covered?
+
+#### 🔍 Finding Duplicate Tests
+```bash
+# Check for existing tests before creating new ones
+grep -r "test.*flag.*position" tests/
+grep -r "test.*parser" tests/
+grep -r "test.*filter" tests/
+```
+
 ### Test Documentation Requirements
 - **Minimal Comments**: Remove all unnecessary verbose comments from test files
 - **Essential Only**: Keep comments only for complex test logic, specific assertions, or edge cases

{awsquery-0.1.0 → awsquery-0.2.0}/Dockerfile

@@ -1,5 +1,10 @@
 FROM python:3.11-slim
 
+# Development Dockerfile optimized for volume mounts
+# Only copies essential files needed for package installation
+# Development files (scripts/, docs/, test analysis files) are excluded
+# and will be available via volume mounts in docker-compose
+
 # Install system dependencies
 RUN apt-get update && apt-get install -y \
     make \
@@ -27,27 +32,28 @@ RUN ARCH=$(uname -m) \
 # Set working directory
 WORKDIR /app
 
-# Copy project configuration files
+# Copy only essential files for package installation
 COPY pyproject.toml .
-COPY pytest.ini .
-COPY .coveragerc .
-COPY Makefile .
 COPY policy.json .
 
-# Copy source code and tests
+# Copy source code (minimal for installation)
 COPY src/ ./src/
-COPY tests/ ./tests/
-COPY awsquery.py .
 
-# Install the package with all dependencies (production + dev for testing)
+# Install the package with all dependencies
+# Note: This installs from the copied source, but in development
+# the volume mount will override this with live code
 RUN pip install --no-cache-dir -e ".[dev]"
 
-# Make original awsquery.py executable for backward compatibility
-RUN chmod +x awsquery.py
+# Copy additional configuration files needed for testing/CI
+# These will be overridden by volume mounts in development
+COPY pytest.ini .
+COPY .coveragerc .
+COPY Makefile .
 
-# Create symlinks for both access methods
-RUN ln -sf /app/awsquery.py /usr/local/bin/awsquery-legacy \
-    && ln -sf /usr/local/bin/awsquery /usr/local/bin/awsquery-cli
+# Configure bash autocomplete for awsquery
+RUN echo '# Enable awsquery autocomplete' >> /root/.bashrc \
+    && echo 'eval "$(register-python-argcomplete awsquery)"' >> /root/.bashrc \
+    && echo 'echo "awsquery autocomplete enabled. Try: awsquery <TAB>"' >> /root/.bashrc
 
 # Set default command to bash for interactive use
 ENTRYPOINT ["/bin/bash"]

{awsquery-0.1.0 → awsquery-0.2.0}/Dockerfile.prod

@@ -1,5 +1,9 @@
 FROM python:3.11-slim as production
 
+# Production Dockerfile with minimal file copying
+# Only includes essential files needed for production deployment
+# Excludes all development, testing, and analysis files
+
 # Install system dependencies
 RUN apt-get update && apt-get install -y \
     curl \
@@ -29,20 +33,18 @@ WORKDIR /app
 COPY pyproject.toml .
 COPY policy.json .
 COPY src/ ./src/
-COPY awsquery.py .
 
 # Install only production dependencies
 RUN pip install --no-cache-dir .
 
-# Make original awsquery.py executable for backward compatibility
-RUN chmod +x awsquery.py
-
-# Create symlinks for access methods
-RUN ln -sf /app/awsquery.py /usr/local/bin/awsquery-legacy \
-    && ln -sf /usr/local/bin/awsquery /usr/local/bin/awsquery-cli
-
 # Create non-root user for security
 RUN useradd -m -u 1000 awsquery
+
+# Configure bash autocomplete for awsquery user
+RUN echo '# Enable awsquery autocomplete' >> /home/awsquery/.bashrc \
+    && echo 'eval "$(register-python-argcomplete awsquery)"' >> /home/awsquery/.bashrc \
+    && chown awsquery:awsquery /home/awsquery/.bashrc
+
 USER awsquery
 
 # Set default command to the CLI tool

{awsquery-0.1.0 → awsquery-0.2.0}/Makefile

@@ -57,6 +57,22 @@ coverage: ## Run tests with coverage report
 coverage-report: coverage ## Generate and show coverage report location
 	@echo "$(GREEN)Coverage report available at: htmlcov/index.html$(NC)"
 
+mutmut: ## Run mutation testing on the codebase
+	@echo "$(BLUE)Running mutation testing with mutmut$(NC)"
+	mutmut run
+
+mutmut-results: ## Show mutation testing results
+	@echo "$(BLUE)Mutation testing results:$(NC)"
+	mutmut results
+
+mutmut-html: ## Generate HTML report for mutation testing
+	mutmut html
+	@echo "$(GREEN)Mutation testing report available at: html/index.html$(NC)"
+
+mutmut-clean: ## Clean mutation testing cache
+	rm -f .mutmut-cache
+	@echo "$(GREEN)Mutation testing cache cleaned$(NC)"
+
 lint: ## Run linting checks
 	flake8 src/ tests/ --count --statistics --show-source
 	pylint src/awsquery

{awsquery-0.1.0 → awsquery-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: awsquery
-Version: 0.1.0
+Version: 0.2.0
 Summary: Advanced CLI tool for querying AWS APIs with flexible filtering and automatic parameter resolution
 Author-email: Florian Motlik <flo@flomotlik.me>
 License: MIT
@@ -54,6 +54,7 @@ Requires-Dist: interrogate>=1.5.0; extra == "dev"
 Requires-Dist: tox>=4.0.0; extra == "dev"
 Requires-Dist: twine>=4.0.0; extra == "dev"
 Requires-Dist: build>=0.10.0; extra == "dev"
+Requires-Dist: mutmut>=2.4.0; extra == "dev"
 Provides-Extra: docs
 Requires-Dist: sphinx>=7.0.0; extra == "docs"
 Requires-Dist: sphinx-rtd-theme>=1.3.0; extra == "docs"
@@ -107,6 +108,52 @@ cd awsquery
 pip install -e ".[dev]"
 ```
 
+### Enable Shell Autocomplete
+
+awsquery supports tab completion for AWS services and actions through argcomplete.
+
+#### Quick Setup (Automatic)
+```bash
+# Run the setup script
+./setup-autocomplete.sh
+
+# Then reload your shell configuration
+source ~/.bashrc  # or ~/.zshrc, etc.
+```
+
+#### Manual Setup
+
+##### Bash
+```bash
+# Add to ~/.bashrc or ~/.bash_profile
+eval "$(register-python-argcomplete awsquery)"
+```
+
+##### Zsh
+```bash
+# Add to ~/.zshrc
+autoload -U bashcompinit && bashcompinit
+eval "$(register-python-argcomplete awsquery)"
+```
+
+##### Fish
+```bash
+# Add to ~/.config/fish/config.fish
+register-python-argcomplete --shell fish awsquery | source
+```
+
+After adding the appropriate line to your shell configuration, restart your shell or source the file:
+```bash
+source ~/.bashrc  # or ~/.zshrc, etc.
+```
+
+Now you can use tab completion:
+```bash
+awsquery <TAB>              # Shows available services
+awsquery ec2 <TAB>          # Shows available ec2 actions
+awsquery s3 list-<TAB>      # Shows s3 list actions
+```
+
 ## Usage
 
 ### Basic Query
@@ -328,40 +375,59 @@ make release  # Create a new release with version bump
 
 ## Advanced Usage
 
-### Partial Matching Behavior
+### Filter Matching Behavior
+
+All filters in awsquery use **case-insensitive matching** with optional anchoring:
 
-All filters in awsquery use **case-insensitive partial matching**:
+#### Filter Operators
+- `^` at the start: matches values that START WITH the pattern (prefix match)
+  - Both `^` (U+005E) and `ˆ` (U+02C6) are supported for keyboard compatibility
+- `$` at the end: matches values that END WITH the pattern (suffix match)
+- `^...$`: matches values that EXACTLY equal the pattern (exact match)
+- No operators: matches values that CONTAIN the pattern (partial match)
 
 #### Value Filters (before `--`)
 - Match against ANY field in the response data
 - ALL specified filters must match (AND logic)
-- Case-insensitive substring matching
+- Case-insensitive matching with optional anchoring
 
 ```bash
-# "prod" matches: "production", "prod-server", "my-prod-app"
+# "prod" matches: "production", "prod-server", "my-prod-app" (contains)
 awsquery ec2 describe-instances prod
 
-# Both "prod" AND "web" must appear (in any fields)
-awsquery ec2 describe-instances prod web
+# "^prod" matches: "production", "prod-server" (starts with)
+awsquery ec2 describe-instances ^prod
+
+# "prod$" matches: "my-prod", "dev-prod" (ends with)
+awsquery ec2 describe-instances prod$
 
-# "i-123" matches any instance ID starting with "i-123"
-awsquery ec2 describe-instances i-123
+# "^prod$" matches: only exactly "prod" (exact match)
+awsquery ec2 describe-instances ^prod$
+
+# Both filters must match (AND logic)
+awsquery ec2 describe-instances ^prod web$
 ```
 
 #### Column Filters (after `--`)
 - Match against column/field names in the output
-- Partial, case-insensitive matching on column names
+- Case-insensitive matching with optional anchoring
 - Multiple columns can be specified
 
 ```bash
-# "Instance" matches: "InstanceId", "InstanceType", "InstanceName"
+# "Instance" matches: "InstanceId", "InstanceType", "InstanceName" (contains)
 awsquery ec2 describe-instances -- Instance
 
-# Shows columns containing "Tag", "State", or "IP"
-awsquery ec2 describe-instances -- Tag State IP
+# "^Instance" matches: "InstanceId", "InstanceType" (starts with)
+awsquery ec2 describe-instances -- ^Instance
+
+# "Name$" matches: "InstanceName", "GroupName", "Tags.Name" (ends with)
+awsquery ec2 describe-instances -- Name$
+
+# "^State.Name$" matches: only exactly "State.Name" (exact match)
+awsquery ec2 describe-instances -- ^State.Name$
 
-# Nested field matching
-awsquery ec2 describe-instances -- State.Name Tags.Environment
+# Multiple patterns
+awsquery ec2 describe-instances -- ^Instance Name$ State
 ```
 
 ### Multi-Level API Calls

{awsquery-0.1.0 → awsquery-0.2.0}/README.md

@@ -45,6 +45,52 @@ cd awsquery
 pip install -e ".[dev]"
 ```
 
+### Enable Shell Autocomplete
+
+awsquery supports tab completion for AWS services and actions through argcomplete.
+
+#### Quick Setup (Automatic)
+```bash
+# Run the setup script
+./setup-autocomplete.sh
+
+# Then reload your shell configuration
+source ~/.bashrc  # or ~/.zshrc, etc.
+```
+
+#### Manual Setup
+
+##### Bash
+```bash
+# Add to ~/.bashrc or ~/.bash_profile
+eval "$(register-python-argcomplete awsquery)"
+```
+
+##### Zsh
+```bash
+# Add to ~/.zshrc
+autoload -U bashcompinit && bashcompinit
+eval "$(register-python-argcomplete awsquery)"
+```
+
+##### Fish
+```bash
+# Add to ~/.config/fish/config.fish
+register-python-argcomplete --shell fish awsquery | source
+```
+
+After adding the appropriate line to your shell configuration, restart your shell or source the file:
+```bash
+source ~/.bashrc  # or ~/.zshrc, etc.
+```
+
+Now you can use tab completion:
+```bash
+awsquery <TAB>              # Shows available services
+awsquery ec2 <TAB>          # Shows available ec2 actions
+awsquery s3 list-<TAB>      # Shows s3 list actions
+```
+
 ## Usage
 
 ### Basic Query
@@ -266,40 +312,59 @@ make release  # Create a new release with version bump
 
 ## Advanced Usage
 
-### Partial Matching Behavior
+### Filter Matching Behavior
+
+All filters in awsquery use **case-insensitive matching** with optional anchoring:
 
-All filters in awsquery use **case-insensitive partial matching**:
+#### Filter Operators
+- `^` at the start: matches values that START WITH the pattern (prefix match)
+  - Both `^` (U+005E) and `ˆ` (U+02C6) are supported for keyboard compatibility
+- `$` at the end: matches values that END WITH the pattern (suffix match)
+- `^...$`: matches values that EXACTLY equal the pattern (exact match)
+- No operators: matches values that CONTAIN the pattern (partial match)
 
 #### Value Filters (before `--`)
 - Match against ANY field in the response data
 - ALL specified filters must match (AND logic)
-- Case-insensitive substring matching
+- Case-insensitive matching with optional anchoring
 
 ```bash
-# "prod" matches: "production", "prod-server", "my-prod-app"
+# "prod" matches: "production", "prod-server", "my-prod-app" (contains)
 awsquery ec2 describe-instances prod
 
-# Both "prod" AND "web" must appear (in any fields)
-awsquery ec2 describe-instances prod web
+# "^prod" matches: "production", "prod-server" (starts with)
+awsquery ec2 describe-instances ^prod
+
+# "prod$" matches: "my-prod", "dev-prod" (ends with)
+awsquery ec2 describe-instances prod$
 
-# "i-123" matches any instance ID starting with "i-123"
-awsquery ec2 describe-instances i-123
+# "^prod$" matches: only exactly "prod" (exact match)
+awsquery ec2 describe-instances ^prod$
+
+# Both filters must match (AND logic)
+awsquery ec2 describe-instances ^prod web$
 ```
 
 #### Column Filters (after `--`)
 - Match against column/field names in the output
-- Partial, case-insensitive matching on column names
+- Case-insensitive matching with optional anchoring
 - Multiple columns can be specified
 
 ```bash
-# "Instance" matches: "InstanceId", "InstanceType", "InstanceName"
+# "Instance" matches: "InstanceId", "InstanceType", "InstanceName" (contains)
 awsquery ec2 describe-instances -- Instance
 
-# Shows columns containing "Tag", "State", or "IP"
-awsquery ec2 describe-instances -- Tag State IP
+# "^Instance" matches: "InstanceId", "InstanceType" (starts with)
+awsquery ec2 describe-instances -- ^Instance
+
+# "Name$" matches: "InstanceName", "GroupName", "Tags.Name" (ends with)
+awsquery ec2 describe-instances -- Name$
+
+# "^State.Name$" matches: only exactly "State.Name" (exact match)
+awsquery ec2 describe-instances -- ^State.Name$
 
-# Nested field matching
-awsquery ec2 describe-instances -- State.Name Tags.Environment
+# Multiple patterns
+awsquery ec2 describe-instances -- ^Instance Name$ State
 ```
 
 ### Multi-Level API Calls

{awsquery-0.1.0 → awsquery-0.2.0}/docker-compose.yml

@@ -11,8 +11,6 @@ services:
       - ~/.aws:/root/.aws:ro
       # Mount current directory for development
       - .:/app
-      # Mount sample responses directory
-      - ./sample-responses:/app/sample-responses
     environment:
       # Set default AWS region if not specified
       - AWS_REGION=${AWS_REGION:-eu-central-1}
@@ -26,24 +24,6 @@ services:
     tty: true
     working_dir: /app
 
-  # Production environment with minimal dependencies
-  awsquery-prod:
-    build:
-      context: .
-      dockerfile: Dockerfile.prod
-    volumes:
-      # Mount AWS credentials (read-only for security)
-      - ~/.aws:/home/awsquery/.aws:ro
-    environment:
-      # Set default AWS region if not specified
-      - AWS_REGION=${AWS_REGION:-eu-central-1}
-      - AWS_DEFAULT_REGION=${AWS_DEFAULT_REGION:-eu-central-1}
-      # Preserve other AWS environment variables
-      - AWS_PROFILE=${AWS_PROFILE:-}
-      - AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID:-}
-      - AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY:-}
-      - AWS_SESSION_TOKEN=${AWS_SESSION_TOKEN:-}
-
   # Legacy service name for backward compatibility
   awsquery:
     extends: awsquery-dev

awsquery-0.2.0/docs/mutation-testing.md

@@ -0,0 +1,75 @@
+# Mutation Testing with Mutmut
+
+This project uses `mutmut` for mutation testing to verify test suite quality.
+
+## Installation
+
+Mutmut is included in development dependencies:
+
+```bash
+pip install -e ".[dev]"
+```
+
+## Configuration
+
+Mutation testing is configured in `pyproject.toml`:
+
+```toml
+[tool.mutmut]
+paths_to_mutate = ["src/awsquery/"]
+runner = "python -m pytest -x -q"
+```
+
+## Usage
+
+### Run Mutation Testing
+
+```bash
+# Run complete mutation testing
+make mutmut
+
+# Or directly
+mutmut run
+```
+
+### View Results
+
+```bash
+# Show summary of results
+make mutmut-results
+
+# Generate HTML report
+make mutmut-html
+
+# Clean mutation cache
+make mutmut-clean
+```
+
+## Interpreting Results
+
+Mutmut creates mutations in your code and runs tests to see if they detect the changes:
+
+- **Killed**: Test suite detected the mutation (good)
+- **Survived**: Test suite didn't detect the mutation (indicates missing test coverage)
+- **Timeout**: Mutation caused infinite loop or significant slowdown
+- **Suspicious**: Test behavior inconsistent
+
+## Best Practices
+
+1. Focus on critical code paths first
+2. Run on specific modules during development
+3. Use mutation testing to identify weak test areas
+4. Not all survived mutations need fixing - use judgment
+
+## Example: Testing Specific Module
+
+```bash
+# Test only the filters module
+mutmut run src/awsquery/filters.py
+```
+
+## Performance Tips
+
+- Use `--max-children` to limit parallel processes
+- Run on subsets of code during development
+- Full runs can be done in CI or before releases