Updated defaults to upload only the current generated report path
This commit is contained in:
@@ -147,8 +147,8 @@ attempted report. Notification fields are `notificationStatus`,
|
||||
Distributor notification is configured with `notify.distributor` and is
|
||||
disabled by default. When enabled, weatherreporter uploads the managed Markdown
|
||||
report path recorded in the report result and metadata. That single source file
|
||||
can be mapped to multiple configured bundle paths, such as a dated archival path
|
||||
and a `latest.md` path. Extra copies written by `--out` or `--out-dir` are
|
||||
can be mapped to one or more configured bundle paths. By default, it is mapped
|
||||
to one dated report path. Extra copies written by `--out` or `--out-dir` are
|
||||
operator conveniences only.
|
||||
|
||||
The rendered pipeline ID selects the configured distributor `http_upload`
|
||||
@@ -160,9 +160,9 @@ weatherreporter.{location_id}.{report_id}
|
||||
```
|
||||
|
||||
The default idempotency key appends RunID to the rendered bundle ID so each
|
||||
report generation has a distinct retry identity. Default bundle paths use the
|
||||
valid-period start date, artifact group, and RunID, and also publish
|
||||
`latest.md` under the same dated artifact-group directory.
|
||||
report generation has a distinct retry identity. The default bundle path uses
|
||||
the valid-period start date, artifact group, and RunID. Distributor owns
|
||||
destination merge, retention, and derived snapshot behavior such as `latest`.
|
||||
|
||||
Notification happens after final metadata save. Weather API, briefing,
|
||||
data-package, render preflight, Scriptorium run, and metadata-save failures do
|
||||
|
||||
Reference in New Issue
Block a user