PyPI - lkr-dev-cli - Versions diffs - 0.0.43__tar.gz → 0.0.44__tar.gz - Mend

lkr-dev-cli 0.0.43tar.gz → 0.0.44tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (63) hide show

lkr_dev_cli-0.0.44/.github/workflows/website.yml ADDED Viewed

@@ -0,0 +1,18 @@
+name: Deploy Website
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - "**.md"
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Trigger Website Deploy
+        run: |
+          curl -fSL "$DEPLOY_URL"
+        env:
+          DEPLOY_URL: ${{ secrets.DEPLOY_URL }}

{lkr_dev_cli-0.0.43 → lkr_dev_cli-0.0.44}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lkr-dev-cli
-Version: 0.0.43
+Version: 0.0.44
 Summary: lkr: a command line interface for looker
 Author: bwebs
 License-Expression: MIT
@@ -40,7 +40,7 @@ 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 `uvx --from lkr-dev-cli[all] 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 lkr-dev-cli --help`.
 Alternatively, you can install `lkr` with `pip install lkr-dev-cli[all]` and use commands directly like `lkr <command>`.
@@ -60,7 +60,7 @@ See the [prerequisites section](#oauth2-prerequisites)
 Login to `lkr`
 ```bash
-uvx --from lkr-dev-cli[all] lkr auth login
+uvx lkr-dev-cli auth login
 ```
 - Select a new instance
@@ -73,7 +73,7 @@ You will be redirected to the Looker OAuth authorization page, click Allow. If y
 If everything is successful, you will see `Successfully authenticated!`. Test it with
 ```bash
-uvx --from lkr-dev-cli[all] lkr auth whoami
+uvx lkr-dev-cli auth whoami
 ```
 ### Using API Key
@@ -81,7 +81,7 @@ uvx --from lkr-dev-cli[all] 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
-uvx --from lkr-dev-cli[all]  lkr --client-id <your client id> --client-secret <your client secret> --base-url <your instance url> auth whoami
+uvx lkr-dev-cli --client-id <your client id> --client-secret <your client secret> --base-url <your instance url> auth whoami
 ```
@@ -120,8 +120,8 @@ 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[all]", "lkr", "mcp", "run"]
+      "command": "uvx",
+      "args": ["lkr-dev-cli[all]", "mcp", "run"]
     },
     "lkr-mcp-docker": {
       "command": "docker",
@@ -422,7 +422,7 @@ By running this tool, an admin can proactively identify and fix permission gaps
 This command should be run by a **Looker Admin**.
 ```bash
-uvx --from lkr-dev-cli[all] lkr tools schedule-download-deprecation
+uvx lkr-dev-cli[all] tools schedule-download-deprecation
 ```
 Options:

{lkr_dev_cli-0.0.43 → lkr_dev_cli-0.0.44}/README.md RENAMED Viewed

@@ -4,7 +4,7 @@ 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 `uvx --from lkr-dev-cli[all] 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 lkr-dev-cli --help`.
 Alternatively, you can install `lkr` with `pip install lkr-dev-cli[all]` and use commands directly like `lkr <command>`.
@@ -24,7 +24,7 @@ See the [prerequisites section](#oauth2-prerequisites)
 Login to `lkr`
 ```bash
-uvx --from lkr-dev-cli[all] lkr auth login
+uvx lkr-dev-cli auth login
 ```
 - Select a new instance
@@ -37,7 +37,7 @@ You will be redirected to the Looker OAuth authorization page, click Allow. If y
 If everything is successful, you will see `Successfully authenticated!`. Test it with
 ```bash
-uvx --from lkr-dev-cli[all] lkr auth whoami
+uvx lkr-dev-cli auth whoami
 ```
 ### Using API Key
@@ -45,7 +45,7 @@ uvx --from lkr-dev-cli[all] 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
-uvx --from lkr-dev-cli[all]  lkr --client-id <your client id> --client-secret <your client secret> --base-url <your instance url> auth whoami
+uvx lkr-dev-cli --client-id <your client id> --client-secret <your client secret> --base-url <your instance url> auth whoami
 ```
@@ -84,8 +84,8 @@ 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[all]", "lkr", "mcp", "run"]
+      "command": "uvx",
+      "args": ["lkr-dev-cli[all]", "mcp", "run"]
     },
     "lkr-mcp-docker": {
       "command": "docker",
@@ -386,7 +386,7 @@ By running this tool, an admin can proactively identify and fix permission gaps
 This command should be run by a **Looker Admin**.
 ```bash
-uvx --from lkr-dev-cli[all] lkr tools schedule-download-deprecation
+uvx lkr-dev-cli[all] tools schedule-download-deprecation
 ```
 Options:

{lkr_dev_cli-0.0.43 → lkr_dev_cli-0.0.44}/codemode.md RENAMED Viewed

@@ -19,7 +19,7 @@ The tool instantiates Looker SDK natively, searches all bound methods, and passe
 ### 1. Starting the Server
 To immediately trigger the stdio listener, use:
 ```bash
-uvx -q --from lkr-dev-cli[codemode] lkr code-mode run
+uvx -q lkr-dev-cli[codemode] code-mode run
 ```
 ### 2. Client Configuration
@@ -30,7 +30,7 @@ To hook this server into Cursor or Claude Desktop natively over stdio, append th
   "mcpServers": {
     "lkr_codemode": {
       "command": "uvx",
-      "args": ["-q", "--from", "lkr-dev-cli[codemode]", "lkr", "code-mode", "run"],
+      "args": ["-q", "lkr-dev-cli[codemode]", "code-mode", "run"],
       "env": {
         "LOOKERSDK_BASE_URL": "https://your.looker.instance",
         "LOOKERSDK_CLIENT_ID": "your-client-id",
@@ -44,7 +44,7 @@ To hook this server into Cursor or Claude Desktop natively over stdio, append th
 ### 3. Visual Inspector
 To check things out on a web panel:
 ```bash
-npx @modelcontextprotocol/inspector uvx -q --from lkr-dev-cli[codemode] lkr code-mode run
+npx @modelcontextprotocol/inspector uvx -q lkr-dev-cli[codemode] code-mode run
 ```
 ## Architectural & Troubleshooting Notes

{lkr_dev_cli-0.0.43 → lkr_dev_cli-0.0.44}/pyproject.toml RENAMED Viewed

@@ -1,6 +1,6 @@
 [project]
 name = "lkr-dev-cli"
-version = "0.0.43"
+version = "0.0.44"
 description = "lkr: a command line interface for looker"
 readme = "README.md"
 license = "MIT"