eric/narratio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 15 Wiki Activity

Bugfix for commands that list artifacts in the S3 backend

Browse Source
This commit is contained in:
Eric Rakestraw
2026-05-21 21:00:51 -05:00
parent 3752f3ed28
commit ca1ded1821
4 changed files with 166 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/cli.md
View File

@@ -132,7 +132,7 @@ Valid stage names:
- `--session <path>`
- `--session-id <value>`
- `--previous-session-id <value>`
- `--remote`: check promoted remote object availability.
- `--remote`: check remote object availability. Catalog sections use canonical source paths; the `Promoted` section checks configured archive destinations.
### `locks`
@@ -289,6 +289,7 @@ narratio artifacts list [--config <pipeline.yml>] [--campaign <campaign.yml>] [-
```
`--remote` checks promoted top-level object availability through the storage adapter.
Catalog sections report canonical source-path availability. The `Promoted` section reports each configured archive promotion destination and includes `dest=<path>` when that destination differs from the source's canonical path.
### `locks`

2
docs/operations.md
View File

@@ -253,7 +253,7 @@ Dry-run does not write restore report files.
- `status` with no config/session flags still requires explicit `--manifest`.
- `status --session-id <id>` uses normal config/session loading, including remote session fallback.
- `status --session-id <id>` includes the same source-based remote output availability view as `artifacts list --remote` when storage is configured.
- `status --session-id <id>` includes the same remote output availability view as `artifacts list --remote` when storage is configured: catalog sections use canonical source paths, and promoted outputs use configured archive destinations.
- local and S3 audio input modes are mutually exclusive.
- archive publish requires upstream stages through `analyze` to be `succeeded`.
- required promotion rules can fail when selected analyze artifacts did not generate a required file path.