Implement the distributor v0.5 PipelineID update
This commit is contained in:
@@ -150,16 +150,18 @@ successfully generated report: the managed Markdown report path recorded in the
|
||||
report result and metadata. Extra copies written by `--out` or `--out-dir` are
|
||||
operator conveniences only.
|
||||
|
||||
The default bundle ID is derived from producer name, location ID, report ID, and
|
||||
RunID:
|
||||
The rendered pipeline ID selects the configured distributor `http_upload`
|
||||
workflow. The default bundle ID is a stable logical source identity derived from
|
||||
producer name, location ID, and report ID:
|
||||
|
||||
```text
|
||||
weatherreporter.{location_id}.{report_id}.{run_id}
|
||||
weatherreporter.{location_id}.{report_id}
|
||||
```
|
||||
|
||||
The default idempotency key is the rendered bundle ID. The default bundle path
|
||||
for the Markdown file is the report definition's batch output name, such as
|
||||
`daily.md`, `tomorrow.md`, `three-day.md`, or `weekend.md`.
|
||||
The default idempotency key appends RunID to the rendered bundle ID so each
|
||||
report generation has a distinct retry identity. The default bundle path for the
|
||||
Markdown file is the report definition's batch output name, such as `daily.md`,
|
||||
`tomorrow.md`, `three-day.md`, or `weekend.md`.
|
||||
|
||||
Notification happens after final metadata save. Weather API, briefing,
|
||||
data-package, render preflight, Scriptorium run, and metadata-save failures do
|
||||
@@ -168,14 +170,14 @@ other reports continue, the failed report includes notification fields in the
|
||||
JSON summary, and the batch returns nonzero.
|
||||
|
||||
Each notification attempt writes a debug artifact under `notifications/`. The
|
||||
artifact records the rendered bundle ID, idempotency key, managed source path,
|
||||
bundle-relative path, bundle created timestamp, accepted upload response, and
|
||||
the latest distributor run status response when available. Weatherreporter polls
|
||||
status until distributor reports `succeeded` or `failed`, or until the configured
|
||||
notification timeout expires. The run status includes the distributor status,
|
||||
error text, and raw run report JSON, which can show actions such as
|
||||
`replace_older`, `skip_same`, `skip_destination_newer`, or `failed`. Token values
|
||||
are not written.
|
||||
artifact records the rendered pipeline ID, bundle ID, idempotency key, managed
|
||||
source path, bundle-relative path, bundle created timestamp, accepted upload
|
||||
response, and the latest distributor run status response when available.
|
||||
Weatherreporter polls status until distributor reports `succeeded` or `failed`,
|
||||
or until the configured notification timeout expires. The run status includes
|
||||
the distributor status, error text, and raw run report JSON, which can show
|
||||
actions such as `replace_older`, `skip_same`, `skip_destination_newer`, or
|
||||
`failed`. Token values are not written.
|
||||
|
||||
Weatherreporter is responsible for selecting the managed Markdown report,
|
||||
constructing a source bundle, and submitting it to the configured distributor
|
||||
|
||||
Reference in New Issue
Block a user