pdt-cli 0.1.2__tar.gz → 0.1.3__tar.gz

{pdt_cli-0.1.2 → pdt_cli-0.1.3}/.gitignore

@@ -16,6 +16,7 @@ dist/
 .pytest_cache/
 .uv-cache/
 claude-task-report/
+winget/rendered/
 
 # OS / editor noise
 .DS_Store

pdt_cli-0.1.3/LICENSE

@@ -0,0 +1,9 @@
+MIT License
+
+Copyright (c) 2026 AutoIDM
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

{pdt_cli-0.1.2 → pdt_cli-0.1.3}/PKG-INFO

@@ -1,8 +1,9 @@
 Metadata-Version: 2.5
 Name: pdt-cli
-Version: 0.1.2
+Version: 0.1.3
 Summary: Easily deploy your process to AWS, Azure, Google Cloud, or Windows.
 License-Expression: MIT
+License-File: LICENSE
 Requires-Python: >=3.12
 Requires-Dist: argcomplete
 Requires-Dist: backoff
@@ -26,7 +27,7 @@ Requires-Dist: gcsfs; extra == 'apps'
 Requires-Dist: google-cloud-secret-manager; extra == 'apps'
 Requires-Dist: google-cloud-storage; extra == 'apps'
 Requires-Dist: pyjwt; extra == 'apps'
-Requires-Dist: s3fs; extra == 'apps'
+Requires-Dist: s3fs>=2024; extra == 'apps'
 Description-Content-Type: text/markdown
 
 # pdt
@@ -41,7 +42,7 @@ uv tool install pdt-cli
 
 That puts a `pdt` command on your PATH. To update it later, run `uv tool upgrade pdt-cli`.
 
-The first interactive `pdt` command turns on tab completion without a prompt. It works in every new terminal: Tab finishes pdt commands, their options, your app names, and example names for `new --from`. It supports bash, zsh, fish, and PowerShell. `pdt completion [SHELL]` sets up a second shell, and `pdt completion --script bash` prints the script instead of writing it, if you keep your own dotfiles.
+On Windows you can run `winget install AutoIDM.pdt` instead, which also installs `uv` if you do not have it and puts the same `pdt` command on your PATH. `winget upgrade AutoIDM.pdt` moves pdt to the latest release, and the first `pdt` command after an install or upgrade finishes setting up that version.
 
 You can also clone this repository and run `./pdt` (or `.\pdt.bat` on Windows) instead. It installs `uv` for you if you do not have it. Both ways give you the same commands.
 
@@ -121,6 +122,7 @@ pdt login my-report
 | `pdt validate` | check the config files and the required env vars |
 | `pdt run APP` | run an app on this machine |
 | `pdt deploy APP` | deploy an app to its configured platform |
+| `pdt deploy --all` | deploy every enabled app, in order; asks whether to skip and disable an app that fails; add `--yes --skip-failures` to run unattended |
 | `pdt destroy APP` | remove everything deploy created |
 | `pdt secrets APP` | show which `.env` values differ from the deployed app |
 | `pdt secrets APP save` | send your `.env` values to the deployed app; the next run uses them |
@@ -128,6 +130,9 @@ pdt login my-report
 | `pdt secrets APP set NAME` | put one value, read from stdin, into the deployed app's secrets |
 | `pdt login APP` | sign in again to the app's cloud provider |
 | `pdt storage APP ls|get|query|destroy` | look at, fetch, query, or delete the app's stored files |
+| `pdt runs APP` | list the deployed app's runs with each run's exit code: the 10 newest, or with `--since 3d` (or `12h`, `2w`, `2026-09-20`, `2026-09-20T14:00`) every run since then, `--span 1d` keeping only the runs within that long after `--since` and `--count N` keeping only the N newest; a run's number is its place among every run pdt can still find, so it stays the same whichever runs print |
+| `pdt logs APP [N]` | read the log of run N as `pdt runs` numbers it; with no N, the newest run, and `--failed` picks the newest failed run instead; `--since`, `--span`, and `--count` limit which runs those two choose from, `--errors` leaves out DEBUG and INFO lines; the last 20 lines print, `--lines N` prints N instead, `--head` prints the first lines instead of the last, and `--full` prints every line |
+| `pdt health [APP]` | show whether each app's last run succeeded; exits 1 when one failed |
 | `pdt az ...` | run the Azure CLI that pdt installs |
 | `pdt gcloud ...` | run the Google Cloud CLI that pdt installs |
 | `pdt completion [SHELL]` | turn on tab completion for a shell |
@@ -140,7 +145,7 @@ Leave `APP` off `run`, `deploy`, `destroy`, `secrets`, or `login`, or mistype it
 
 Your app runs, writes some files, and stops. Then the computer it ran on is thrown away, and the files go with it. So pdt gives every app a folder in your cloud account that stays. Deploy the app, destroy it, deploy it again: the folder and everything in it is still there.
 
-pdt creates one bucket per cloud account, named `pdt-data-` plus a short code, and gives each app its own folder inside it. When your app runs in the cloud, `PDT_STORAGE_URL` points at that folder. When you run `pdt run APP` on your own computer, it points at `.pdt/storage/APP/` inside your project instead. The app code is the same in both places.
+pdt creates one bucket per cloud account, named `pdt-data-` plus a short code, and gives each app its own folder inside it. When your app runs in the cloud, `PDT_STORAGE_URL` points at that folder. A Windows scheduled task points it at `%ProgramData%\pdt\APP\storage\`. When you run `pdt run APP` on your own computer, it points at `.pdt/storage/APP/` inside your project instead. The app code is the same in every place.
 
 Write and read files with `pdt.utils.storage`:
 
@@ -183,7 +188,7 @@ Every command reads its values from the environment it runs in. A build server s
 
 ## Choosing where jobs run
 
-Set `platform:` in `pdt.yml` for every app, or in an app's own `config.yml` for one app. An app's own file wins.
+Set `platform:` in `pdt.yml` for every app, or in an app's own `config.yml` for one app. An app's own file wins. `timezone` may live under `platform:` as the default for every app, and an app's own `timezone` overrides it.
 
 ### Azure
 
@@ -228,7 +233,7 @@ platform:
 
 ### Bringing your own Dockerfile
 
-Every cloud provider runs a job as a container: AWS on Fargate, Azure on Container Apps Jobs, Google Cloud on Cloud Run Jobs. The deploy builds an image for each app from a generated Dockerfile. It copies the app folder and `pdt.yml` into `/workspace`, installs the script-header dependencies of `run.py` with `uv sync --script`, and runs `run.py` as the entrypoint.
+Every cloud provider runs a job as a container: AWS on Batch (Fargate), Azure on Container Apps Jobs, Google Cloud on Cloud Run Jobs. The deploy builds an image for each app from a generated Dockerfile. It copies the app folder and `pdt.yml` into `/workspace`, installs the script-header dependencies of `run.py` with `uv sync --script`, and runs `run.py` as the entrypoint.
 
 Put a `Dockerfile` in the app folder to build the image your own way, for example to add system packages or to install a heavy tool at build time instead of on every run. The build context is the same as the generated one: the app folder under its own name, next to `pdt.yml`. Start from the generated file:
 
@@ -236,7 +241,7 @@ Put a `Dockerfile` in the app folder to build the image your own way, for exampl
 FROM ghcr.io/astral-sh/uv:python3.12-bookworm-slim
 COPY . /workspace
 WORKDIR /workspace/my-app
-ENV PDT_PROJECT=/workspace
+ENV PDT_PROJECT=/workspace NO_COLOR=1 DBT_USE_COLORS=false
 RUN uv sync --script run.py
 ENTRYPOINT ["uv", "run", "--script", "run.py"]
 ```
@@ -253,10 +258,11 @@ platform:
 
 apps:
   - name: my-report
-    timezone: local
     schedule: daily
 ```
 
+The Windows provider runs each job on the PC's local time, so `timezone` defaults to `local` there, the only value it accepts.
+
 The job runs as the SYSTEM account. Windows accepts these schedules:
 
 - `hourly`, `daily`, `weekly`, `monthly`, and `yearly`
@@ -267,6 +273,8 @@ The job runs as the SYSTEM account. Windows accepts these schedules:
 
 Other cron forms are rejected, because they do not translate to Windows Task Scheduler.
 
+Each app keeps its run data in `%ProgramData%\pdt\<app>\`. The task writes one log file per run to the `logs\` folder in it, named by the run's UTC start time, and `pdt runs <app>` and `pdt logs <app>` read those files. The app's own files (see [Keeping files between runs](#keeping-files-between-runs)) live in the `storage\` folder next to it. Deploy creates the folder and gives the SYSTEM account full control and you modify rights, so `pdt storage <app> destroy` works without an administrator. `pdt destroy <app>` removes the task and the `logs\` folder and keeps `storage\`. A run is stopped after 30 minutes, the same limit as the cloud providers, and a run that is still going when the next one is due is left alone; the new start is skipped.
+
 ## The bundled examples
 
 Run `pdt examples` to list them, then `pdt new <name> --from <example>` to copy one.
@@ -290,9 +298,11 @@ Reports active Monday users whose email address does not match the `userPrincipa
 | Item | Where |
 | --- | --- |
 | the `pdt` command and its code | the tool's own environment, from `uv tool install` |
+| the `pdt` launcher from winget | `%LOCALAPPDATA%\Microsoft\WinGet\Packages`, linked from `%LOCALAPPDATA%\Microsoft\WinGet\Links` |
 | the example apps | inside the pdt package, copied out by `pdt new` |
 | your apps, `pdt.yml`, `.env` | your project folder, under version control |
 | the Google Cloud CLI pdt downloads | `~/.local/share/pdt/gcloud`, or `%LOCALAPPDATA%\pdt\gcloud` |
+| a Windows scheduled task's run logs and files | `%ProgramData%\pdt\<app>\logs` and `%ProgramData%\pdt\<app>\storage` |
 | cloud sign-in state | `~/.azure` and `~/.config/gcloud`, as usual |
 
 Set `PDT_PROJECT` to name the project folder directly, instead of letting pdt search upward. Deployed jobs get it set for them.
@@ -304,7 +314,7 @@ An app is a folder with a `run.py` that has a `main()` function. It declares its
 ```python
 # /// script
 # requires-python = ">=3.12"
-# dependencies = ["pdt-cli[apps]==0.1.2"]
+# dependencies = ["pdt-cli[apps]==0.1.3"]
 # ///
 from pathlib import Path
 

{pdt_cli-0.1.2 → pdt_cli-0.1.3}/README.md

@@ -10,7 +10,7 @@ uv tool install pdt-cli
 
 That puts a `pdt` command on your PATH. To update it later, run `uv tool upgrade pdt-cli`.
 
-The first interactive `pdt` command turns on tab completion without a prompt. It works in every new terminal: Tab finishes pdt commands, their options, your app names, and example names for `new --from`. It supports bash, zsh, fish, and PowerShell. `pdt completion [SHELL]` sets up a second shell, and `pdt completion --script bash` prints the script instead of writing it, if you keep your own dotfiles.
+On Windows you can run `winget install AutoIDM.pdt` instead, which also installs `uv` if you do not have it and puts the same `pdt` command on your PATH. `winget upgrade AutoIDM.pdt` moves pdt to the latest release, and the first `pdt` command after an install or upgrade finishes setting up that version.
 
 You can also clone this repository and run `./pdt` (or `.\pdt.bat` on Windows) instead. It installs `uv` for you if you do not have it. Both ways give you the same commands.
 
@@ -90,6 +90,7 @@ pdt login my-report
 | `pdt validate` | check the config files and the required env vars |
 | `pdt run APP` | run an app on this machine |
 | `pdt deploy APP` | deploy an app to its configured platform |
+| `pdt deploy --all` | deploy every enabled app, in order; asks whether to skip and disable an app that fails; add `--yes --skip-failures` to run unattended |
 | `pdt destroy APP` | remove everything deploy created |
 | `pdt secrets APP` | show which `.env` values differ from the deployed app |
 | `pdt secrets APP save` | send your `.env` values to the deployed app; the next run uses them |
@@ -97,6 +98,9 @@ pdt login my-report
 | `pdt secrets APP set NAME` | put one value, read from stdin, into the deployed app's secrets |
 | `pdt login APP` | sign in again to the app's cloud provider |
 | `pdt storage APP ls|get|query|destroy` | look at, fetch, query, or delete the app's stored files |
+| `pdt runs APP` | list the deployed app's runs with each run's exit code: the 10 newest, or with `--since 3d` (or `12h`, `2w`, `2026-09-20`, `2026-09-20T14:00`) every run since then, `--span 1d` keeping only the runs within that long after `--since` and `--count N` keeping only the N newest; a run's number is its place among every run pdt can still find, so it stays the same whichever runs print |
+| `pdt logs APP [N]` | read the log of run N as `pdt runs` numbers it; with no N, the newest run, and `--failed` picks the newest failed run instead; `--since`, `--span`, and `--count` limit which runs those two choose from, `--errors` leaves out DEBUG and INFO lines; the last 20 lines print, `--lines N` prints N instead, `--head` prints the first lines instead of the last, and `--full` prints every line |
+| `pdt health [APP]` | show whether each app's last run succeeded; exits 1 when one failed |
 | `pdt az ...` | run the Azure CLI that pdt installs |
 | `pdt gcloud ...` | run the Google Cloud CLI that pdt installs |
 | `pdt completion [SHELL]` | turn on tab completion for a shell |
@@ -109,7 +113,7 @@ Leave `APP` off `run`, `deploy`, `destroy`, `secrets`, or `login`, or mistype it
 
 Your app runs, writes some files, and stops. Then the computer it ran on is thrown away, and the files go with it. So pdt gives every app a folder in your cloud account that stays. Deploy the app, destroy it, deploy it again: the folder and everything in it is still there.
 
-pdt creates one bucket per cloud account, named `pdt-data-` plus a short code, and gives each app its own folder inside it. When your app runs in the cloud, `PDT_STORAGE_URL` points at that folder. When you run `pdt run APP` on your own computer, it points at `.pdt/storage/APP/` inside your project instead. The app code is the same in both places.
+pdt creates one bucket per cloud account, named `pdt-data-` plus a short code, and gives each app its own folder inside it. When your app runs in the cloud, `PDT_STORAGE_URL` points at that folder. A Windows scheduled task points it at `%ProgramData%\pdt\APP\storage\`. When you run `pdt run APP` on your own computer, it points at `.pdt/storage/APP/` inside your project instead. The app code is the same in every place.
 
 Write and read files with `pdt.utils.storage`:
 
@@ -152,7 +156,7 @@ Every command reads its values from the environment it runs in. A build server s
 
 ## Choosing where jobs run
 
-Set `platform:` in `pdt.yml` for every app, or in an app's own `config.yml` for one app. An app's own file wins.
+Set `platform:` in `pdt.yml` for every app, or in an app's own `config.yml` for one app. An app's own file wins. `timezone` may live under `platform:` as the default for every app, and an app's own `timezone` overrides it.
 
 ### Azure
 
@@ -197,7 +201,7 @@ platform:
 
 ### Bringing your own Dockerfile
 
-Every cloud provider runs a job as a container: AWS on Fargate, Azure on Container Apps Jobs, Google Cloud on Cloud Run Jobs. The deploy builds an image for each app from a generated Dockerfile. It copies the app folder and `pdt.yml` into `/workspace`, installs the script-header dependencies of `run.py` with `uv sync --script`, and runs `run.py` as the entrypoint.
+Every cloud provider runs a job as a container: AWS on Batch (Fargate), Azure on Container Apps Jobs, Google Cloud on Cloud Run Jobs. The deploy builds an image for each app from a generated Dockerfile. It copies the app folder and `pdt.yml` into `/workspace`, installs the script-header dependencies of `run.py` with `uv sync --script`, and runs `run.py` as the entrypoint.
 
 Put a `Dockerfile` in the app folder to build the image your own way, for example to add system packages or to install a heavy tool at build time instead of on every run. The build context is the same as the generated one: the app folder under its own name, next to `pdt.yml`. Start from the generated file:
 
@@ -205,7 +209,7 @@ Put a `Dockerfile` in the app folder to build the image your own way, for exampl
 FROM ghcr.io/astral-sh/uv:python3.12-bookworm-slim
 COPY . /workspace
 WORKDIR /workspace/my-app
-ENV PDT_PROJECT=/workspace
+ENV PDT_PROJECT=/workspace NO_COLOR=1 DBT_USE_COLORS=false
 RUN uv sync --script run.py
 ENTRYPOINT ["uv", "run", "--script", "run.py"]
 ```
@@ -222,10 +226,11 @@ platform:
 
 apps:
   - name: my-report
-    timezone: local
     schedule: daily
 ```
 
+The Windows provider runs each job on the PC's local time, so `timezone` defaults to `local` there, the only value it accepts.
+
 The job runs as the SYSTEM account. Windows accepts these schedules:
 
 - `hourly`, `daily`, `weekly`, `monthly`, and `yearly`
@@ -236,6 +241,8 @@ The job runs as the SYSTEM account. Windows accepts these schedules:
 
 Other cron forms are rejected, because they do not translate to Windows Task Scheduler.
 
+Each app keeps its run data in `%ProgramData%\pdt\<app>\`. The task writes one log file per run to the `logs\` folder in it, named by the run's UTC start time, and `pdt runs <app>` and `pdt logs <app>` read those files. The app's own files (see [Keeping files between runs](#keeping-files-between-runs)) live in the `storage\` folder next to it. Deploy creates the folder and gives the SYSTEM account full control and you modify rights, so `pdt storage <app> destroy` works without an administrator. `pdt destroy <app>` removes the task and the `logs\` folder and keeps `storage\`. A run is stopped after 30 minutes, the same limit as the cloud providers, and a run that is still going when the next one is due is left alone; the new start is skipped.
+
 ## The bundled examples
 
 Run `pdt examples` to list them, then `pdt new <name> --from <example>` to copy one.
@@ -259,9 +266,11 @@ Reports active Monday users whose email address does not match the `userPrincipa
 | Item | Where |
 | --- | --- |
 | the `pdt` command and its code | the tool's own environment, from `uv tool install` |
+| the `pdt` launcher from winget | `%LOCALAPPDATA%\Microsoft\WinGet\Packages`, linked from `%LOCALAPPDATA%\Microsoft\WinGet\Links` |
 | the example apps | inside the pdt package, copied out by `pdt new` |
 | your apps, `pdt.yml`, `.env` | your project folder, under version control |
 | the Google Cloud CLI pdt downloads | `~/.local/share/pdt/gcloud`, or `%LOCALAPPDATA%\pdt\gcloud` |
+| a Windows scheduled task's run logs and files | `%ProgramData%\pdt\<app>\logs` and `%ProgramData%\pdt\<app>\storage` |
 | cloud sign-in state | `~/.azure` and `~/.config/gcloud`, as usual |
 
 Set `PDT_PROJECT` to name the project folder directly, instead of letting pdt search upward. Deployed jobs get it set for them.
@@ -273,7 +282,7 @@ An app is a folder with a `run.py` that has a `main()` function. It declares its
 ```python
 # /// script
 # requires-python = ">=3.12"
-# dependencies = ["pdt-cli[apps]==0.1.2"]
+# dependencies = ["pdt-cli[apps]==0.1.3"]
 # ///
 from pathlib import Path
 

{pdt_cli-0.1.2 → pdt_cli-0.1.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "pdt-cli"
-version = "0.1.2"
+version = "0.1.3"
 description = "Easily deploy your process to AWS, Azure, Google Cloud, or Windows."
 readme = "README.md"
 requires-python = ">=3.12"
@@ -25,7 +25,7 @@ apps = [
     "boto3",
     "google-cloud-secret-manager",
     "fsspec",
-    "s3fs",
+    "s3fs>=2024",
     "gcsfs",
     "adlfs",
     "google-cloud-storage",
@@ -58,7 +58,7 @@ include = ["src/**/*.py"]
 extend-exclude = ["src/pdt/examples"]
 
 [tool.ruff.lint]
-select = ["T20"]
+select = ["T20", "F821"]
 
 [tool.ruff.lint.per-file-ignores]
 "src/pdt/utils/log.py" = ["T20"]

{pdt_cli-0.1.2 → pdt_cli-0.1.3}/src/pdt/cli.py

@@ -18,6 +18,7 @@ import rich_argparse
 
 from pdt import __version__, completion, config, console, deploy, deploy_common, scaffold
 from pdt.config import ConfigError
+from pdt.utils.email_auth import can_prompt
 from pdt.utils.send_email import auth_env_file, email_problems, prepare_email_auth
 
 CLOUD_CLIS = {
@@ -52,8 +53,17 @@ APP_QUESTIONS = {
     "login": "Which app's cloud provider do you want to sign in to?",
     "destroy": "Which app do you want to destroy?",
     "secrets": "Which app's secrets?",
+    "storage": "Which app's files do you want to manage?",
+    "runs": "Which app's runs do you want to see?",
+    "logs": "Which app's log do you want to read?",
+    "health": "Which app do you want to check?",
 }
 
+SINCE_HELP = ("show every run that started at or after this: 12h, 3d, 2w, 2026-09-20, "
+              "or 2026-09-20T14:00 (default: the 10 newest runs)")
+SPAN_HELP = "with --since, show only the runs that started within this long after it: 12h, 3d, 2w"
+COUNT_HELP = "show at most this many runs (default: 10 without --since, else every run)"
+
 
 def choose_app(name: str | None, command: str) -> str | None:
     """Return the app `pdt <command>` should act on, or None after guiding the user.
@@ -156,12 +166,51 @@ def cmd_run(args) -> int:
 
 
 def cmd_deploy(args) -> int:
+    if args.skip_failures and not args.all:
+        console.error("--skip-failures only works with --all")
+        return 1
+    if args.all:
+        if args.app is not None:
+            console.error("pick an app or --all, not both")
+            return 1
+        return deploy_all(args.yes, args.skip_failures)
     name = choose_app(args.app, "deploy")
     if name is None:
         return 1
     return deploy.deploy(name, assume_yes=args.yes)
 
 
+def deploy_all(assume_yes: bool, skip_failures: bool) -> int:
+    names = config.find_apps()
+    if not names:
+        say_no_apps()
+        return 1
+    ask = not skip_failures and can_prompt(None)
+    failed: list[str] = []
+    for index, name in enumerate(names, 1):
+        console.heading(f"Deploying {name} ({index} of {len(names)})")
+        code = deploy.deploy(name, assume_yes=assume_yes)
+        if code == 0:
+            continue
+        failed.append(name)
+        console.error(f"{name} did not deploy.")
+        if index < len(names) and not skip_failures and not (
+                ask and console.confirm(
+                    f"Skip the failing app {name} and deploy the rest?")):
+            console.say("Fix the problem above and run pdt deploy --all again, "
+                        "or add --skip-failures to go on past it.")
+            return code
+        if ask and not assume_yes and console.confirm(
+                f"Disable the failing app {name}?"):
+            path = config.set_app_enabled(name, False)
+            console.done(f"Disabled {name} in {path.relative_to(config.find_project())}. "
+                         "Set enabled: true there to bring it back.")
+    if failed:
+        console.warn(f"Not deployed: {', '.join(failed)}")
+        return 1
+    return 0
+
+
 def cmd_login(args) -> int:
     name = choose_app(args.app, "login")
     if name is None:
@@ -184,7 +233,48 @@ def cmd_secrets(args) -> int:
 
 
 def cmd_storage(args) -> int:
-    return deploy.storage(args.app, args.rest)
+    name = choose_app(args.app, "storage")
+    if name is None:
+        return 1
+    return deploy.storage(name, args.rest)
+
+
+def window_options(args) -> list[str]:
+    return [part for option, value in (("--since", args.since), ("--span", args.span),
+                                       ("--count", args.count)) if value is not None
+            for part in (option, str(value))]
+
+
+def cmd_runs(args) -> int:
+    name = choose_app(args.app, "runs")
+    if name is None:
+        return 1
+    return deploy.runs(name, [*window_options(args), *(["--json"] if args.json else [])])
+
+
+def cmd_logs(args) -> int:
+    name = choose_app(args.app, "logs")
+    if name is None:
+        return 1
+    flags = [flag for flag, on in (("--failed", args.failed), ("--errors", args.errors),
+                                   ("--head", args.head), ("--full", args.full),
+                                   ("--json", args.json)) if on]
+    lines = [] if args.lines is None else ["--lines", str(args.lines)]
+    return deploy.logs(name, [str(args.number), *window_options(args), *lines, *flags])
+
+
+def cmd_health(args) -> int:
+    if args.app is None:
+        names = config.find_apps()
+        if not names:
+            say_no_apps()
+            return 0
+    else:
+        name = choose_app(args.app, "health")
+        if name is None:
+            return 1
+        names = [name]
+    return deploy.health(names, args.json)
 
 
 def cmd_completion(args) -> int:
@@ -232,6 +322,9 @@ def build_parser() -> argparse.ArgumentParser:
                          help="the app's folder name; omit to see the choices")
     app.completer = completion.apps
     p.add_argument("--yes", action="store_true", help="skip the confirmation prompt")
+    p.add_argument("--all", action="store_true", help="deploy every enabled app, in order")
+    p.add_argument("--skip-failures", action="store_true",
+                   help="with --all, go on past an app that fails to deploy instead of asking")
     p.set_defaults(func=cmd_deploy)
     p = add_parser("login", help="sign in again to an app's cloud provider")
     app = p.add_argument("app", nargs="?",
@@ -257,10 +350,44 @@ def build_parser() -> argparse.ArgumentParser:
     p.add_argument("--yes", action="store_true", help="skip the confirmation prompt")
     p.set_defaults(func=cmd_secrets)
     p = add_parser("storage", help="read or manage an app's data store")
-    app = p.add_argument("app", help="the app's folder name")
+    app = p.add_argument("app", nargs="?",
+                         help="the app's folder name; omit to see the choices")
     app.completer = completion.apps
     p.add_argument("rest", nargs=argparse.REMAINDER, help="ls|get|query|destroy [args...]")
     p.set_defaults(func=cmd_storage)
+    p = add_parser("runs", help="list a deployed app's recent runs")
+    app = p.add_argument("app", nargs="?",
+                         help="the app's folder name; omit to see the choices")
+    app.completer = completion.apps
+    p.add_argument("--since", help=SINCE_HELP)
+    p.add_argument("--span", help=SPAN_HELP)
+    p.add_argument("--count", type=int, help=COUNT_HELP)
+    p.add_argument("--json", action="store_true", help="print JSON for a script or an agent")
+    p.set_defaults(func=cmd_runs)
+    p = add_parser("logs", help="read the log of one of a deployed app's runs")
+    app = p.add_argument("app", nargs="?",
+                         help="the app's folder name; omit to see the choices")
+    app.completer = completion.apps
+    p.add_argument("number", nargs="?", type=int, default=1,
+                   help="which run, as `pdt runs` numbers them (default: 1, the newest)")
+    p.add_argument("--since", help=SINCE_HELP)
+    p.add_argument("--span", help=SPAN_HELP)
+    p.add_argument("--count", type=int, help=COUNT_HELP)
+    p.add_argument("--failed", action="store_true", help="read the newest failed run")
+    p.add_argument("--errors", action="store_true",
+                   help="leave out DEBUG and INFO lines")
+    p.add_argument("--lines", type=int, help="print this many lines (default: 20)")
+    p.add_argument("--head", action="store_true",
+                   help="print the first lines, not the last")
+    p.add_argument("--full", action="store_true",
+                   help="print every line, not only the last 20")
+    p.add_argument("--json", action="store_true", help="print JSON for a script or an agent")
+    p.set_defaults(func=cmd_logs)
+    p = add_parser("health", help="show whether each deployed app's last run succeeded")
+    app = p.add_argument("app", nargs="?", help="one app's folder name; omit to check every app")
+    app.completer = completion.apps
+    p.add_argument("--json", action="store_true", help="print JSON for a script or an agent")
+    p.set_defaults(func=cmd_health)
     p = add_parser("completion", help="turn on tab completion in your shell")
     p.add_argument("shell", nargs="?", choices=completion.SHELLS,
                    help="which shell; pdt works it out when left off")
@@ -277,10 +404,12 @@ def main() -> int:
     parser = build_parser()
     completion.configure(parser)
     if len(sys.argv) > 1 and sys.argv[1] in CLOUD_CLIS:
-        # Before argparse, so the cloud CLI parses its own flags.
+        # Before argparse, so the cloud CLI parses its own flags. --project keeps
+        # `uvx pdt aws` working; deploy.provider_command explains why.
         script = Path(__file__).with_name(CLOUD_CLIS[sys.argv[1]])
         return subprocess.run(
-            ["uv", "run", "--script", str(script), *sys.argv[1:]]).returncode
+            ["uv", "run", "--project", str(Path.cwd()), "--script", str(script),
+             *sys.argv[1:]]).returncode
     args = parser.parse_args()
     if args.command is None:
         parser.print_help()

{pdt_cli-0.1.2 → pdt_cli-0.1.3}/src/pdt/completion.py

@@ -132,7 +132,7 @@ def setup(shell: str | None = None) -> None:
 
 
 def configure(parser) -> None:
-    argcomplete.autocomplete(parser)
+    argcomplete.autocomplete(parser, always_complete_options=False)
     if not (sys.stdin.isatty() and sys.stderr.isatty()):
         return
     try: