lkr-dev-cli 0.0.30__tar.gz → 0.0.31__tar.gz

lkr_dev_cli-0.0.31/.github/workflows/test-dependencies.yml

@@ -0,0 +1,34 @@
+name: Test Dependency Resolution
+
+on:
+  push:
+    branches: [ main, develop ]
+  pull_request:
+    branches: [ main, develop ]
+  workflow_dispatch:
+
+jobs:
+  test-dependencies:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+      
+    - name: Setup Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: '3.12'
+        
+    - name: Install uv
+      uses: astral-sh/setup-uv@v2
+      with:
+        version: latest
+        
+    - name: Install dependencies
+      run: |
+        uv sync --extra all
+        
+    - name: Run with pytest
+      run: |
+        uv run pytest tests/test_dependency_resolution.py -v 

{lkr_dev_cli-0.0.30 → lkr_dev_cli-0.0.31}/Dockerfile

@@ -9,6 +9,6 @@ WORKDIR /app
 COPY pyproject.toml uv.lock README.md LICENSE ./
 COPY lkr ./lkr
 ENV UV_PROJECT_ENVIRONMENT="/usr/local/"
-RUN uv sync --frozen --no-dev --no-editable
+RUN uv sync --frozen --no-dev --no-editable --extra=all
 
 CMD []

lkr_dev_cli-0.0.31/Makefile

@@ -0,0 +1,7 @@
+.PHONY: docs test-deps
+
+docs:
+	typer lkr/main.py utils docs --output lkr.md
+
+test-deps:
+	python tests/test_dependency_resolution.py 

lkr_dev_cli-0.0.30/README.md → lkr_dev_cli-0.0.31/PKG-INFO

@@ -1,3 +1,34 @@
+Metadata-Version: 2.4
+Name: lkr-dev-cli
+Version: 0.0.31
+Summary: lkr: a command line interface for looker
+Author: bwebs
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.12
+Requires-Dist: cryptography>=42.0.0
+Requires-Dist: looker-sdk>=25.4.0
+Requires-Dist: pydantic>=2.11.4
+Requires-Dist: pydash>=8.0.5
+Requires-Dist: questionary>=2.1.0
+Requires-Dist: requests>=2.31.0
+Requires-Dist: structlog>=25.3.0
+Requires-Dist: typer>=0.15.2
+Provides-Extra: all
+Requires-Dist: duckdb>=1.2.2; extra == 'all'
+Requires-Dist: fastapi>=0.115.12; extra == 'all'
+Requires-Dist: mcp[cli]>=1.9.2; extra == 'all'
+Requires-Dist: selenium>=4.32.0; extra == 'all'
+Provides-Extra: embed-observability
+Requires-Dist: fastapi>=0.115.12; extra == 'embed-observability'
+Requires-Dist: selenium>=4.32.0; extra == 'embed-observability'
+Provides-Extra: mcp
+Requires-Dist: duckdb>=1.2.2; extra == 'mcp'
+Requires-Dist: mcp[cli]>=1.9.2; extra == 'mcp'
+Provides-Extra: user-attribute-updater
+Requires-Dist: fastapi>=0.115.12; extra == 'user-attribute-updater'
+Description-Content-Type: text/markdown
+
 # lkr cli
 
 The `lkr` cli is a tool for interacting with Looker. It combines Looker's SDK and customer logic to interact with Looker in meaninful ways. For a full list of commands, see the full [cli docs](./lkr.md)
@@ -192,10 +223,13 @@ This can also be used to stress test your Looker environment as it serves an API
 ## User Attribute Updater (OIDC Token)
 
 1. Create a new cloud run using the `lkr-cli` public docker image `us-central1-docker.pkg.dev/lkr-dev-production/lkr-cli/cli:latest`
-2. Put in the environment variables LOOKERSDK_CLIENT_ID, LOOKERSDK_CLIENT_SECRET, LOOKERSDK_BASE_URL, LOOKER_WHITELISTED_BASE_URLS. The `LOOKER_WHITELISTED_BASE_URLS` would be the same url as the `LOOKERSDK_BASE_URL` if you are only using this for a single Looker instance. For more advanced use cases, you can set the `LOOKER_WHITELISTED_BASE_URLS` to a comma separated list of urls. The body of the request also accepts a `base_url`, `client_id`, and `client_secret` key that will override these settings.
-3. Deploy the cloud run
-4. Retrieve the URL of the cloud run
-5. Create the user attribute 
+2. Put in the environment variables LOOKERSDK_CLIENT_ID, LOOKERSDK_CLIENT_SECRET, LOOKERSDK_BASE_URL, LOOKER_WHITELISTED_BASE_URLS. The `LOOKER_WHITELISTED_BASE_URLS` would be the same url as the `LOOKERSDK_BASE_URL` if you are only using this for a single Looker instance. For more advanced use cases, you can set the `LOOKER_WHITELISTED_BASE_URLS` to a comma separated list of urls. The body of the request also accepts a `base_url`, `client_id`, and `client_secret` key that will override these settings. See example [`gcloud` command](#example-gcloud-command)
+3. For the command and arguments use:
+   - command: `lkr`
+   - args: `tools` `user-attribute-updater`
+4. Deploy the cloud run
+5. Retrieve the URL of the cloud run
+6. Create the user attribute 
    - Name: cloud_run_access_token 
    - Data Type: String
    - User Access: None
@@ -228,6 +262,23 @@ This can also be used to stress test your Looker environment as it serves an API
 9. Check the logs of the cloud run to see if there was a 200 response
 
 
+### Example `gcloud` command
+```bash
+export REGION=<your region>
+export PROJECT=<your project id>
+
+gcloud run deploy lkr-access-token-updater \
+  --image us-central1-docker.pkg.dev/lkr-dev-production/lkr-cli/cli:latest \
+  --command lkr \
+  --args tools,user-attribute-updater \
+  --platform managed \
+  --region $REGION \
+  --project $PROJECT \
+  --cpu 1 \
+  --memory 2Gi \
+  --set-env-vars LOOKERSDK_CLIENT_ID=<your client id>,LOOKERSDK_CLIENT_SECRET=<your client secret>,LOOKERSDK_BASE_URL=<your instance url>,LOOKER_WHITELISTED_BASE_URLS=<your instance url>
+  ```
+
 ## UserAttributeUpdater `lkr-dev-cli`
 
 Exported from the `lkr-dev-cli` package is the `UserAttributeUpdater` pydantic class. This class has all the necessary logic to update a user attribute value. 
@@ -279,12 +330,12 @@ from lkr import UserAttributeUpdater
 def request_authorization(request: Request):
     body = await request.json()
     updater = UserAttributeUpdater.model_validate(body)
-    updater.get_request_authorization_for_value(request)
+    updater.get_request_authorization_for_value(request.headers.items())
     updater.update_user_attribute_value()
 
 @app.post("/as_body")
 def as_body(request: Request, body: UserAttributeUpdater):
-    body.get_request_authorization_for_value(request)
+    body.get_request_authorization_for_value(request.headers.items())
     body.update_user_attribute_value()
 
 @app.post("/assigning_value")
@@ -295,4 +346,64 @@ def assigning_value(request: Request):
     )
     updater.value = request.headers.get("my_custom_header")
     updater.update_user_attribute_value()
+
+@app.delete("/:user_attribute_name/:email")
+def delete_user_attribute(user_attribute_name: str, email: str):
+    updater = UserAttributeUpdater(
+      user_attribute=user_attribute_name,
+      update_type="user",
+      email=email,
+    )
+    updater.delete_user_attribute_value()
+
+## Optional Dependencies
+
+The `lkr` CLI supports optional dependencies that enable additional functionality. You can install these individually or all at once.
+
+### Available Extras
+
+- **`mcp`**: Enables the MCP (Model Context Protocol) server functionality
+  - Includes: `mcp[cli]>=1.9.2`, `duckdb>=1.2.2`
+- **`embed-observability`**: Enables the observability embed monitoring features
+  - Includes: `fastapi>=0.115.12`, `selenium>=4.32.0`
+- **`user-attribute-updater`**: Enables the user attribute updater functionality
+  - Includes: `fastapi>=0.115.12`
+
+### Installing Optional Dependencies
+
+**Install all optional dependencies:**
+```bash
+uv sync --extra all
 ```
+
+**Install specific extras:**
+```bash
+# Install MCP functionality
+uv sync --extra mcp
+
+# Install observability features
+uv sync --extra embed-observability
+
+# Install user attribute updater
+uv sync --extra user-attribute-updater
+
+# Install multiple extras
+uv sync --extra mcp --extra embed-observability
+```
+
+**Using pip:**
+```bash
+# Install all optional dependencies
+pip install lkr-dev-cli[all]
+
+# Install specific extras
+pip install lkr-dev-cli[mcp,embed-observability,user-attribute-updater]
+```
+
+### What Each Extra Enables
+
+- **`mcp`**: Use the MCP server with tools like Cursor for enhanced IDE integration
+- **`embed-observability`**: Run the observability embed server for monitoring Looker dashboard performance
+- **`user-attribute-updater`**: Deploy the user attribute updater service for OIDC token management
+
+All extras are designed to work together seamlessly, and installing `all` is equivalent to installing all individual extras.

lkr_dev_cli-0.0.30/PKG-INFO → lkr_dev_cli-0.0.31/README.md

@@ -1,25 +1,3 @@
-Metadata-Version: 2.4
-Name: lkr-dev-cli
-Version: 0.0.30
-Summary: lkr: a command line interface for looker
-Author: bwebs
-License-Expression: MIT
-License-File: LICENSE
-Requires-Python: >=3.12
-Requires-Dist: cryptography>=42.0.0
-Requires-Dist: duckdb>=1.2.2
-Requires-Dist: fastapi>=0.115.12
-Requires-Dist: looker-sdk>=25.4.0
-Requires-Dist: mcp[cli]>=1.9.2
-Requires-Dist: pydantic>=2.11.4
-Requires-Dist: pydash>=8.0.5
-Requires-Dist: questionary>=2.1.0
-Requires-Dist: requests>=2.31.0
-Requires-Dist: selenium>=4.32.0
-Requires-Dist: structlog>=25.3.0
-Requires-Dist: typer>=0.15.2
-Description-Content-Type: text/markdown
-
 # lkr cli
 
 The `lkr` cli is a tool for interacting with Looker. It combines Looker's SDK and customer logic to interact with Looker in meaninful ways. For a full list of commands, see the full [cli docs](./lkr.md)
@@ -214,10 +192,13 @@ This can also be used to stress test your Looker environment as it serves an API
 ## User Attribute Updater (OIDC Token)
 
 1. Create a new cloud run using the `lkr-cli` public docker image `us-central1-docker.pkg.dev/lkr-dev-production/lkr-cli/cli:latest`
-2. Put in the environment variables LOOKERSDK_CLIENT_ID, LOOKERSDK_CLIENT_SECRET, LOOKERSDK_BASE_URL, LOOKER_WHITELISTED_BASE_URLS. The `LOOKER_WHITELISTED_BASE_URLS` would be the same url as the `LOOKERSDK_BASE_URL` if you are only using this for a single Looker instance. For more advanced use cases, you can set the `LOOKER_WHITELISTED_BASE_URLS` to a comma separated list of urls. The body of the request also accepts a `base_url`, `client_id`, and `client_secret` key that will override these settings.
-3. Deploy the cloud run
-4. Retrieve the URL of the cloud run
-5. Create the user attribute 
+2. Put in the environment variables LOOKERSDK_CLIENT_ID, LOOKERSDK_CLIENT_SECRET, LOOKERSDK_BASE_URL, LOOKER_WHITELISTED_BASE_URLS. The `LOOKER_WHITELISTED_BASE_URLS` would be the same url as the `LOOKERSDK_BASE_URL` if you are only using this for a single Looker instance. For more advanced use cases, you can set the `LOOKER_WHITELISTED_BASE_URLS` to a comma separated list of urls. The body of the request also accepts a `base_url`, `client_id`, and `client_secret` key that will override these settings. See example [`gcloud` command](#example-gcloud-command)
+3. For the command and arguments use:
+   - command: `lkr`
+   - args: `tools` `user-attribute-updater`
+4. Deploy the cloud run
+5. Retrieve the URL of the cloud run
+6. Create the user attribute 
    - Name: cloud_run_access_token 
    - Data Type: String
    - User Access: None
@@ -250,6 +231,23 @@ This can also be used to stress test your Looker environment as it serves an API
 9. Check the logs of the cloud run to see if there was a 200 response
 
 
+### Example `gcloud` command
+```bash
+export REGION=<your region>
+export PROJECT=<your project id>
+
+gcloud run deploy lkr-access-token-updater \
+  --image us-central1-docker.pkg.dev/lkr-dev-production/lkr-cli/cli:latest \
+  --command lkr \
+  --args tools,user-attribute-updater \
+  --platform managed \
+  --region $REGION \
+  --project $PROJECT \
+  --cpu 1 \
+  --memory 2Gi \
+  --set-env-vars LOOKERSDK_CLIENT_ID=<your client id>,LOOKERSDK_CLIENT_SECRET=<your client secret>,LOOKERSDK_BASE_URL=<your instance url>,LOOKER_WHITELISTED_BASE_URLS=<your instance url>
+  ```
+
 ## UserAttributeUpdater `lkr-dev-cli`
 
 Exported from the `lkr-dev-cli` package is the `UserAttributeUpdater` pydantic class. This class has all the necessary logic to update a user attribute value. 
@@ -301,12 +299,12 @@ from lkr import UserAttributeUpdater
 def request_authorization(request: Request):
     body = await request.json()
     updater = UserAttributeUpdater.model_validate(body)
-    updater.get_request_authorization_for_value(request)
+    updater.get_request_authorization_for_value(request.headers.items())
     updater.update_user_attribute_value()
 
 @app.post("/as_body")
 def as_body(request: Request, body: UserAttributeUpdater):
-    body.get_request_authorization_for_value(request)
+    body.get_request_authorization_for_value(request.headers.items())
     body.update_user_attribute_value()
 
 @app.post("/assigning_value")
@@ -317,4 +315,64 @@ def assigning_value(request: Request):
     )
     updater.value = request.headers.get("my_custom_header")
     updater.update_user_attribute_value()
+
+@app.delete("/:user_attribute_name/:email")
+def delete_user_attribute(user_attribute_name: str, email: str):
+    updater = UserAttributeUpdater(
+      user_attribute=user_attribute_name,
+      update_type="user",
+      email=email,
+    )
+    updater.delete_user_attribute_value()
+
+## Optional Dependencies
+
+The `lkr` CLI supports optional dependencies that enable additional functionality. You can install these individually or all at once.
+
+### Available Extras
+
+- **`mcp`**: Enables the MCP (Model Context Protocol) server functionality
+  - Includes: `mcp[cli]>=1.9.2`, `duckdb>=1.2.2`
+- **`embed-observability`**: Enables the observability embed monitoring features
+  - Includes: `fastapi>=0.115.12`, `selenium>=4.32.0`
+- **`user-attribute-updater`**: Enables the user attribute updater functionality
+  - Includes: `fastapi>=0.115.12`
+
+### Installing Optional Dependencies
+
+**Install all optional dependencies:**
+```bash
+uv sync --extra all
 ```
+
+**Install specific extras:**
+```bash
+# Install MCP functionality
+uv sync --extra mcp
+
+# Install observability features
+uv sync --extra embed-observability
+
+# Install user attribute updater
+uv sync --extra user-attribute-updater
+
+# Install multiple extras
+uv sync --extra mcp --extra embed-observability
+```
+
+**Using pip:**
+```bash
+# Install all optional dependencies
+pip install lkr-dev-cli[all]
+
+# Install specific extras
+pip install lkr-dev-cli[mcp,embed-observability,user-attribute-updater]
+```
+
+### What Each Extra Enables
+
+- **`mcp`**: Use the MCP server with tools like Cursor for enhanced IDE integration
+- **`embed-observability`**: Run the observability embed server for monitoring Looker dashboard performance
+- **`user-attribute-updater`**: Deploy the user attribute updater service for OIDC token management
+
+All extras are designed to work together seamlessly, and installing `all` is equivalent to installing all individual extras.

{lkr_dev_cli-0.0.30 → lkr_dev_cli-0.0.31}/lkr/tools/classes.py

@@ -1,6 +1,5 @@
 from typing import Literal, Optional, Self, cast
 
-from fastapi import Request
 from looker_sdk.sdk.api40.methods import Looker40SDK
 from looker_sdk.sdk.api40.models import (
     UserAttributeGroupValue,
@@ -46,10 +45,12 @@ class UserAttributeUpdater(BaseModel):
                 )
         return self
 
-    def get_request_authorization_for_value(self, request: Request):
-        authorization_token = request.headers.get("Authorization")
+    def get_request_authorization_for_value(self, headers: list[tuple[str, str]]):
+        authorization_token = next(
+            (header for header in headers if header[0] == "Authorization"), None
+        )
         if authorization_token:
-            self.value = authorization_token
+            self.value = authorization_token[1]
         else:
             logger.error("No authorization token found")
 

{lkr_dev_cli-0.0.30 → lkr_dev_cli-0.0.31}/lkr/tools/main.py

@@ -22,7 +22,7 @@ def user_attribute_updater(
     @api.post("/identity_token")
     def identity_token(request: Request, body: UserAttributeUpdater):
         try:
-            body.get_request_authorization_for_value(request)
+            body.get_request_authorization_for_value(request.headers.items())
             body.update_user_attribute_value()
             raw_urls = os.getenv("LOOKER_WHITELISTED_BASE_URLS", "")
             whitelisted_base_urls = (

{lkr_dev_cli-0.0.30 → lkr_dev_cli-0.0.31}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "lkr-dev-cli"
-version = "0.0.30"
+version = "0.0.31"
 description = "lkr: a command line interface for looker"
 readme = "README.md"
 license = "MIT"
@@ -17,10 +17,25 @@ dependencies = [
     "pydash>=8.0.5",
     "structlog>=25.3.0",
     "questionary>=2.1.0",
-    "duckdb>=1.2.2",
+]
+
+[project.optional-dependencies]
+mcp = [
+    "mcp[cli]>=1.9.2",
+    "duckdb>=1.2.2"
+]
+embed-observability = [
     "fastapi>=0.115.12",
-    "selenium>=4.32.0",
+    "selenium>=4.32.0"
+]
+user-attribute-updater = [
+    "fastapi>=0.115.12"
+]
+all = [
     "mcp[cli]>=1.9.2",
+    "fastapi>=0.115.12",
+    "selenium>=4.32.0",
+    "duckdb>=1.2.2"
 ]
 
 [project.scripts]

lkr_dev_cli-0.0.31/tests/TESTING.md

@@ -0,0 +1,96 @@
+# Testing Dependency Resolution
+
+This project includes tests to ensure that all dependency combinations resolve to the same lock file, maintaining consistency in the dependency tree.
+
+## What the tests verify
+
+The tests ensure that these two commands produce identical lock files:
+
+1. `uv sync --extra all`
+2. `uv sync --extra [all individual extras]`
+
+Where "all individual extras" are dynamically discovered from `pyproject.toml` (excluding the `all` extra itself).
+
+This is important because the `all` extra should be equivalent to installing all individual extras together.
+
+## Running the tests
+
+### Option 1: Shell script (recommended for quick testing)
+
+```bash
+./tests/test_deps.sh
+```
+
+This script will:
+- Dynamically discover all individual extras from `pyproject.toml`
+- Create temporary directories
+- Run both dependency resolution commands
+- Compare the resulting lock files
+- Clean up automatically
+
+### Option 2: Python test (for CI/CD integration)
+
+```bash
+# Run directly
+python tests/test_dependency_resolution.py
+
+# Run with pytest
+uv run pytest tests/test_dependency_resolution.py -v
+```
+
+### Option 3: Makefile target
+
+```bash
+make test-deps
+```
+
+## What the tests check
+
+1. **Dynamic Extra Discovery**: Automatically discovers all individual extras from `pyproject.toml`
+2. **Dependency Resolution Consistency**: Ensures that `--extra all` and `--extra [individual extras]` resolve to the same set of packages
+3. **Configuration Validation**: Verifies that all required extras are properly defined in `pyproject.toml`
+4. **Lock File Integrity**: Compares SHA256 hashes of generated lock files
+
+## Expected output
+
+When the tests pass, you should see:
+
+```
+🔍 Discovering individual extras...
+📦 Found individual extras: mcp embed-observability user-attribute-updater
+🎉 SUCCESS: All dependency combinations resolve to the same lock file!
+✅ Dependency resolution is consistent
+```
+
+## Adding new extras
+
+When you add a new extra to `pyproject.toml`, the tests will automatically:
+
+1. Discover the new extra
+2. Include it in the dependency resolution test
+3. Verify that `--extra all` still includes all dependencies from the new extra
+
+No manual test updates are required!
+
+## Troubleshooting
+
+If the tests fail, it usually means:
+
+1. **Missing dependencies**: The `all` extra doesn't include all the dependencies from individual extras
+2. **Version conflicts**: Different dependency combinations resolve to different versions
+3. **Configuration issues**: The `pyproject.toml` file has inconsistencies
+
+### Common fixes
+
+1. **Update the `all` extra**: Make sure it includes all dependencies from individual extras
+2. **Check for version conflicts**: Ensure that all extras use compatible versions
+3. **Verify dependency definitions**: Make sure all extras are properly defined
+
+## CI/CD Integration
+
+The tests are automatically run in GitHub Actions on:
+- Push to `main` or `develop` branches
+- Pull requests to `main` or `develop` branches
+- Manual workflow dispatch
+
+See `.github/workflows/test-dependencies.yml` for the CI configuration.