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

{lkr_dev_cli-0.0.31 → lkr_dev_cli-0.0.33}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lkr-dev-cli
-Version: 0.0.31
+Version: 0.0.33
 Summary: lkr: a command line interface for looker
 Author: bwebs
 License-Expression: MIT
@@ -16,17 +16,18 @@ 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: fastapi[standard]>=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: fastapi[standard]>=0.115.12; 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'
+Provides-Extra: observability
+Requires-Dist: fastapi[standard]>=0.115.12; extra == 'observability'
+Requires-Dist: selenium>=4.32.0; extra == 'observability'
+Provides-Extra: tools
+Requires-Dist: fastapi[standard]>=0.115.12; extra == 'tools'
 Description-Content-Type: text/markdown
 
 # lkr cli
@@ -35,9 +36,9 @@ The `lkr` cli is a tool for interacting with Looker. It combines Looker's SDK an
 
 ## Usage
 
-`uv` makes everyone's life easier. Go [install it](https://docs.astral.sh/uv/getting-started/installation/). You can start using `lkr` by running `uv run --with lkr-dev-cli lkr --help`.
+`uv` makes everyone's life easier. Go [install it](https://docs.astral.sh/uv/getting-started/installation/). You can start using `lkr` by running `uvx --from lkr-dev-cli[all] lkr --help`.
 
-Alternatively, you can install `lkr` with `pip install lkr-dev-cli` and use commands directly like `lkr <command>`.
+Alternatively, you can install `lkr` with `pip install lkr-dev-cli[all]` and use commands directly like `lkr <command>`.
 
 We also have a public docker image that you can use to run `lkr` commands.
 
@@ -55,7 +56,7 @@ See the [prerequisites section](#oauth2-prerequisites)
 Login to `lkr`
 
 ```bash
-uv run --with lkr-dev-cli lkr auth login
+uvx --from lkr-dev-cli[all] lkr auth login
 ```
 
 - Select a new instance
@@ -63,12 +64,12 @@ uv run --with lkr-dev-cli lkr auth login
 - Choose whether you want this login to use production or development mode
 - Give it a name
 
-You will be redirected to the Looker OAuth authorization page, click Allow. If you do not see an allow button, the [prerequisites](#prerequisites) were not done properly.
+You will be redirected to the Looker OAuth authorization page, click Allow. If you do not see an allow button, the [prerequisites](#oauth2-prerequisites) were not done properly.
 
 If everything is successful, you will see `Successfully authenticated!`. Test it with
 
 ```bash
-uv run --with lkr-dev-cli lkr auth whoami
+uvx --from lkr-dev-cli[all] lkr auth whoami
 ```
 
 ### Using API Key
@@ -76,7 +77,7 @@ uv run --with lkr-dev-cli lkr auth whoami
 If you provide environment variables for `LOOKERSDK_CLIENT_ID`, `LOOKERSDK_CLIENT_SECRET`, and `LOOKERSDK_BASE_URL`, `lkr` will use the API key to authenticate and the commands.  We also support command line arguments to pass in the client id, client secret, and base url.
 
 ```bash
-uv run --with lkr-dev-cli  lkr --client-id <your client id> --client-secret <your client secret> --base-url <your instance url> auth whoami
+uvx --from lkr-dev-cli[all]  lkr --client-id <your client id> --client-secret <your client secret> --base-url <your instance url> auth whoami
 ```
 
 
@@ -112,7 +113,7 @@ Built into the `lkr` is an MCP server. Right now its tools are based on helping
   "mcpServers": {
     "lkr-mcp": {
       "command": "uv",
-      "args": ["run", "--with", "lkr-dev-cli", "lkr", "mcp", "run"]
+      "args": ["run", "--with", "lkr-dev-cli[all]", "lkr", "mcp", "run"]
     },
     "lkr-mcp-docker": {
       "command": "docker",
@@ -356,18 +357,39 @@ def delete_user_attribute(user_attribute_name: str, email: str):
     )
     updater.delete_user_attribute_value()
 
+## Permission Deprecation Tool
+
+The `schedule-download-deprecation` tool helps Looker admins ensure that users do not lose access to models they already have when Looker moves towards more granular model-specific permissions for scheduling and downloading.
+
+### How it helps
+Currently, some permissions in Looker can be granted instance-wide. In the future, these permissions may need to be explicitly granted at the model level (via Model Sets). This tool audits all active users and identifies those who:
+- Have "target permissions" (like `download_with_limit`, `schedule_look_emails`, etc.) instance-wide.
+- Do **not** have those same permissions for specific models they otherwise have access to.
+
+By running this tool, an admin can proactively identify and fix permission gaps before any deprecation takes effect, ensuring a seamless experience for end-users.
+
+### Usage
+This command should be run by a **Looker Admin**.
+
+```bash
+uvx --from lkr-dev-cli[all] lkr tools schedule-download-deprecation
+```
+
+Options:
+- `--csv`: Export the results to a CSV file for easier analysis of large instances.
+- `--unfiltered`: Show all users, including those who have all required permissions across all models.
+- `--model-offset`: Slice the table output to show different sets of models (the table shows 5 models at a time).
+
+
 ## 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`
+- **`mcp`**: Enables the MCP (Model Context Protocol) server functionality and `lkr mcp` commands
+- **`observability`**: Enables the observability embed monitoring features and `lkr observability` commands
+- **`tools`**: Enables the user attribute updater functionality and `lkr tools` commands
 
 ### Installing Optional Dependencies
 
@@ -399,11 +421,3 @@ 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.31 → lkr_dev_cli-0.0.33}/README.md

@@ -4,9 +4,9 @@ The `lkr` cli is a tool for interacting with Looker. It combines Looker's SDK an
 
 ## Usage
 
-`uv` makes everyone's life easier. Go [install it](https://docs.astral.sh/uv/getting-started/installation/). You can start using `lkr` by running `uv run --with lkr-dev-cli lkr --help`.
+`uv` makes everyone's life easier. Go [install it](https://docs.astral.sh/uv/getting-started/installation/). You can start using `lkr` by running `uvx --from lkr-dev-cli[all] lkr --help`.
 
-Alternatively, you can install `lkr` with `pip install lkr-dev-cli` and use commands directly like `lkr <command>`.
+Alternatively, you can install `lkr` with `pip install lkr-dev-cli[all]` and use commands directly like `lkr <command>`.
 
 We also have a public docker image that you can use to run `lkr` commands.
 
@@ -24,7 +24,7 @@ See the [prerequisites section](#oauth2-prerequisites)
 Login to `lkr`
 
 ```bash
-uv run --with lkr-dev-cli lkr auth login
+uvx --from lkr-dev-cli[all] lkr auth login
 ```
 
 - Select a new instance
@@ -32,12 +32,12 @@ uv run --with lkr-dev-cli lkr auth login
 - Choose whether you want this login to use production or development mode
 - Give it a name
 
-You will be redirected to the Looker OAuth authorization page, click Allow. If you do not see an allow button, the [prerequisites](#prerequisites) were not done properly.
+You will be redirected to the Looker OAuth authorization page, click Allow. If you do not see an allow button, the [prerequisites](#oauth2-prerequisites) were not done properly.
 
 If everything is successful, you will see `Successfully authenticated!`. Test it with
 
 ```bash
-uv run --with lkr-dev-cli lkr auth whoami
+uvx --from lkr-dev-cli[all] lkr auth whoami
 ```
 
 ### Using API Key
@@ -45,7 +45,7 @@ uv run --with lkr-dev-cli lkr auth whoami
 If you provide environment variables for `LOOKERSDK_CLIENT_ID`, `LOOKERSDK_CLIENT_SECRET`, and `LOOKERSDK_BASE_URL`, `lkr` will use the API key to authenticate and the commands.  We also support command line arguments to pass in the client id, client secret, and base url.
 
 ```bash
-uv run --with lkr-dev-cli  lkr --client-id <your client id> --client-secret <your client secret> --base-url <your instance url> auth whoami
+uvx --from lkr-dev-cli[all]  lkr --client-id <your client id> --client-secret <your client secret> --base-url <your instance url> auth whoami
 ```
 
 
@@ -81,7 +81,7 @@ Built into the `lkr` is an MCP server. Right now its tools are based on helping
   "mcpServers": {
     "lkr-mcp": {
       "command": "uv",
-      "args": ["run", "--with", "lkr-dev-cli", "lkr", "mcp", "run"]
+      "args": ["run", "--with", "lkr-dev-cli[all]", "lkr", "mcp", "run"]
     },
     "lkr-mcp-docker": {
       "command": "docker",
@@ -325,18 +325,39 @@ def delete_user_attribute(user_attribute_name: str, email: str):
     )
     updater.delete_user_attribute_value()
 
+## Permission Deprecation Tool
+
+The `schedule-download-deprecation` tool helps Looker admins ensure that users do not lose access to models they already have when Looker moves towards more granular model-specific permissions for scheduling and downloading.
+
+### How it helps
+Currently, some permissions in Looker can be granted instance-wide. In the future, these permissions may need to be explicitly granted at the model level (via Model Sets). This tool audits all active users and identifies those who:
+- Have "target permissions" (like `download_with_limit`, `schedule_look_emails`, etc.) instance-wide.
+- Do **not** have those same permissions for specific models they otherwise have access to.
+
+By running this tool, an admin can proactively identify and fix permission gaps before any deprecation takes effect, ensuring a seamless experience for end-users.
+
+### Usage
+This command should be run by a **Looker Admin**.
+
+```bash
+uvx --from lkr-dev-cli[all] lkr tools schedule-download-deprecation
+```
+
+Options:
+- `--csv`: Export the results to a CSV file for easier analysis of large instances.
+- `--unfiltered`: Show all users, including those who have all required permissions across all models.
+- `--model-offset`: Slice the table output to show different sets of models (the table shows 5 models at a time).
+
+
 ## 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`
+- **`mcp`**: Enables the MCP (Model Context Protocol) server functionality and `lkr mcp` commands
+- **`observability`**: Enables the observability embed monitoring features and `lkr observability` commands
+- **`tools`**: Enables the user attribute updater functionality and `lkr tools` commands
 
 ### Installing Optional Dependencies
 
@@ -368,11 +389,3 @@ 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.31 → lkr_dev_cli-0.0.33}/lkr/auth/main.py

@@ -1,16 +1,25 @@
 import urllib.parse
 from typing import Annotated, List, Union
 
-import questionary
 import typer
 from looker_sdk.rtl.auth_token import AccessToken, AuthToken
-from rich.console import Console
-from rich.table import Table
 
 from lkr.auth.oauth import OAuth2PKCE
 from lkr.auth_service import get_auth
 from lkr.logger import logger
 
+QUESTIONARY_AVAILABLE = True
+RICH_AVAILABLE = True
+try:
+    import questionary
+except ModuleNotFoundError:
+    QUESTIONARY_AVAILABLE = False
+try:
+    from rich.console import Console
+    from rich.table import Table
+except ModuleNotFoundError:
+    RICH_AVAILABLE = False
+
 __all__ = ["group"]
 
 group = typer.Typer(name="auth", help="Authentication commands for LookML Repository")
@@ -199,7 +208,7 @@ def list(ctx: typer.Context):
     """
     List all authenticated Looker instances
     """
-    console = Console()
+    console = Console() if RICH_AVAILABLE else None
     auth = get_auth(ctx)
     all_instances = auth.list_auth()
     if not all_instances:
@@ -213,7 +222,10 @@ def list(ctx: typer.Context):
             instance[1],
             "Yes" if instance[3] else "No",
         )
-    console.print(table)
+    if console:
+        console.print(table)
+    else:
+        print(table)
 
 
 if __name__ == "__main__":

{lkr_dev_cli-0.0.31 → lkr_dev_cli-0.0.33}/lkr/auth_service.py

@@ -3,10 +3,11 @@ import os
 import sqlite3
 import types
 from datetime import datetime, timedelta, timezone
-from typing import List, Self, Tuple, Union
+from typing import List, Self, Tuple, Union, TYPE_CHECKING
 
 import requests
-import typer
+if TYPE_CHECKING:
+    import typer
 from looker_sdk.rtl import serialize
 from looker_sdk.rtl.api_settings import ApiSettings, SettingsConfig
 from looker_sdk.rtl.auth_session import AuthSession, CryptoHash, OAuthSession
@@ -25,7 +26,7 @@ from lkr.logger import logger
 __all__ = ["get_auth", "ApiKeyAuthSession", "DbOAuthSession"]
 
 
-def get_auth(ctx: typer.Context | LkrCtxObj) -> Union["SqlLiteAuth", "ApiKeyAuth"]:
+def get_auth(ctx: Union["typer.Context", LkrCtxObj]) -> Union["SqlLiteAuth", "ApiKeyAuth"]:
     if isinstance(ctx, LkrCtxObj):
         lkr_ctx = ctx
     else:

{lkr_dev_cli-0.0.31 → lkr_dev_cli-0.0.33}/lkr/logger.py

@@ -1,19 +1,28 @@
 import logging
 import os
+from lkr.custom_types import LogLevel
 
-import structlog
-from rich.console import Console
-from rich.logging import RichHandler
-from rich.theme import Theme
+STRUCT_LOG_AVAILABLE = True
+RICH_AVAILABLE = True
+try:
+    import structlog
+except ModuleNotFoundError:
+    STRUCT_LOG_AVAILABLE = False
+try:
+    from rich.console import Console
+    from rich.logging import RichHandler
+    from rich.theme import Theme
+except ModuleNotFoundError:
+    RICH_AVAILABLE = False
 
-from lkr.custom_types import LogLevel
 
-structlog.configure(
-    processors=[
-        structlog.processors.TimeStamper(fmt="iso"),
-        structlog.processors.JSONRenderer(),
-    ]
-)
+if STRUCT_LOG_AVAILABLE:
+    structlog.configure(
+        processors=[
+            structlog.processors.TimeStamper(fmt="iso"),
+            structlog.processors.JSONRenderer(),
+        ]
+    )
 
 # Define a custom theme for our logging
 theme = Theme(
@@ -24,10 +33,10 @@ theme = Theme(
         "logging.level.error": "bold red",
         "logging.level.critical": "bold white on red",
     }
-)
+) if RICH_AVAILABLE else None
 
 # Create a console for logging
-console = Console(theme=theme)
+console = Console(theme=theme) if RICH_AVAILABLE else None
 
 # Configure the logging handler
 handler = RichHandler(
@@ -37,7 +46,7 @@ handler = RichHandler(
     markup=True,
     rich_tracebacks=True,
     tracebacks_show_locals=True,
-)
+) if RICH_AVAILABLE else None
 
 # Get log level from environment variable, defaulting to INFO
 DEFAULT_LOG_LEVEL = "INFO"
@@ -50,25 +59,27 @@ logging.basicConfig(
     ),  # Fallback to INFO if invalid level
     format="%(message)s",
     datefmt="[%X]",
-    handlers=[handler],
+    handlers=[handler] if handler else [],
 )
 
 # Create a logger for the application
 logger = logging.getLogger("lkr")
-structured_logger = structlog.get_logger("lkr.structured")
+structured_logger = structlog.get_logger("lkr.structured") if STRUCT_LOG_AVAILABLE else None
 
 
 # Configure the requests_transport logger to only show debug messages when LOG_LEVEL is DEBUG
-requests_logger = logging.getLogger("looker_sdk.rtl.requests_transport")
-if log_level != "DEBUG":
+requests_logger = logging.getLogger("looker_sdk.rtl.requests_transport") if RICH_AVAILABLE else None
+if log_level != "DEBUG" and requests_logger:
     requests_logger.setLevel(logging.WARNING)
 
 
 def set_log_level(level: LogLevel):
     """Set the logging level for the application."""
     logger.setLevel(getattr(logging, level.value))
-    logging.getLogger("lkr.structured").setLevel(getattr(logging, level.value))
+    if structured_logger:
+        structured_logger.setLevel(getattr(logging, level.value))
     # Update requests_transport logger level based on the new level
-    requests_logger.setLevel(
-        logging.DEBUG if level == LogLevel.DEBUG else logging.WARNING
-    )
+    if requests_logger:
+        requests_logger.setLevel(
+            logging.DEBUG if level == LogLevel.DEBUG else logging.WARNING
+        )

{lkr_dev_cli-0.0.31 → lkr_dev_cli-0.0.33}/lkr/main.py

@@ -7,9 +7,6 @@ from lkr.auth.main import group as auth_group
 from lkr.classes import LkrCtxObj
 from lkr.custom_types import LogLevel
 from lkr.logger import logger
-from lkr.mcp.main import group as mcp_group
-from lkr.observability.main import group as observability_group
-from lkr.tools.main import group as tools_group
 
 app = typer.Typer(
     name="lkr",
@@ -19,10 +16,32 @@ app = typer.Typer(
 )
 
 app.add_typer(auth_group, name="auth")
-app.add_typer(mcp_group, name="mcp")
-app.add_typer(observability_group, name="observability")
-app.add_typer(tools_group, name="tools")
 
+IMPORT_ERROR = None
+
+def add_optional_typer_group(app, import_path, group_name, extra_message=None):
+    try:
+        module_path, attr = import_path.rsplit(".", 1)
+        mod = __import__(module_path, fromlist=[attr])
+        group = getattr(mod, attr)
+        app.add_typer(group, name=group_name)
+    except ModuleNotFoundError as import_error:
+        @app.command(
+            name=group_name,
+            add_help_option=False,
+            context_settings={"allow_extra_args": True, "ignore_unknown_options": True},
+        )
+        def fallback(import_error=import_error):
+            msg = f"{group_name} tools (dependencies not available, try installing optional dependencies: lkr-dev-cli\\[{group_name}])"
+            if extra_message:
+                msg += f" {extra_message}"
+            logger.error(msg)
+            logger.error(import_error)
+            raise typer.Exit(1)
+
+add_optional_typer_group(app, "lkr.mcp.main.group", "mcp")
+add_optional_typer_group(app, "lkr.observability.main.group", "observability")
+add_optional_typer_group(app, "lkr.tools.main.group", "tools")
 
 @app.callback()
 def callback(

{lkr_dev_cli-0.0.31 → lkr_dev_cli-0.0.33}/lkr/observability/main.py

@@ -39,6 +39,8 @@ DEFAULT_PERMISSIONS = set(
 
 observability_ctx = ObservabilityCtxObj()
 
+if not structured_logger:
+    raise Exception("Structured logger is not available")
 
 def get_embed_sdk_obj(
     dashboard_id: str = Query(...),