v0.1.12

Summary

• pdt run APP --deployed --follow starts a run and prints its log until the run ends.
• pdt logs APP --list lists each run log, and pdt storage APP ls shows the number of files and the size of each folder.
• --open on pdt logs, pdt runs, and pdt storage opens the folder, the log file, or Task Scheduler on Windows, and the console page on AWS, Azure, and Google Cloud, signed in to the right account or tenant.
• Each Windows Task Scheduler run writes a success or failure event to the Windows Application log.
• Alerts can go to Microsoft Teams, and console alerts print as one [alert] line.
• On Azure, following the first run after a deploy no longer prints a 404 warning.
• Google Cloud jobs no longer log a 403 warning for each storage call, and --follow prints Google Cloud lines in time order.
• Yes/no questions ask again until the answer is y or n, and the verify workflow builds again.

It includes #208, #209, #210, #227, #229, #237, #238, #257, #259, #260 and #261.

Features

• feat: add --open, logs --list, run --follow, and storage sizes (#257)
• feat(alerts): print console alerts as one [alert] sentence (#227)
• feat(alerts): name webhook entries by webhook ID, not a typed channel (#210)
• feat(alerts): add a Microsoft Teams alerts type (#209)
• feat(cli): suggest pdt logs --follow after pdt run --deployed (#237)

Fixes

• fix(gcloud): stop the 403 storage warnings and order live log lines (#260)
• fix(deploy): build an app that installs a local wheel (#261)
• fix(alerts): start setup from pdt.yml, ask before the test, add console (#208)
• fix(logs): follow a new Azure run's live log without a 404 (#229), by @visch
• fix: ask yes/no questions again until the answer is y or n (#238)

Tests

• test(cli): make the pdt health order test independent of thread timing (#259)

CI and release

• chore(release): 0.1.12 (#262)

Full changelog: v0.1.11...v0.1.12