shots capture: signed-in web apps (shots.capture.auth request with ${cred:}/${env:} references or storageState), shots login saves a demo sign-in to .storebound/auth.json (0600), expired-session warning, secrets and cookies masked
This commit is contained in:
parent
3949ff1531
commit
e1e4e05237
15 changed files with 545 additions and 9 deletions
|
|
@ -2,6 +2,13 @@
|
|||
|
||||
## Unreleased
|
||||
|
||||
- `shots capture --source web` can sign in first: `shots.capture.auth` is a sign-in request (run once per browser
|
||||
context, cookies kept; body and headers use `${cred:NAME}` from `.storebound/credentials.json` or `${env:NAME}`,
|
||||
literal secrets are refused, a failed status stops with the status only) or a `storageState` file. `storebound shots
|
||||
login` opens a fresh visible browser for a demo sign-in by hand and saves `.storebound/auth.json` (0600, counts
|
||||
only). A shot that lands on a sign-in page warns "session expired? run storebound shots login again". Secrets and
|
||||
cookie values are masked in logs and the capture report.
|
||||
|
||||
## 0.8.16 · 2026-10-20
|
||||
|
||||
- `apps folders add [<folder>]` adds the folder (it listed and added nothing); a template config is added with a note,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue