Skip to content

[Ford] Added the Workflow publish sample. - #167

Closed
moetemp wants to merge 8 commits into
moe/ford/w4-manifest-budgetfrom
moe/ford/w5-workflow-sample
Closed

moetemp wants to merge 8 commits into
moe/ford/w4-manifest-budgetfrom
moe/ford/w5-workflow-sample

Conversation

@moetemp

@moetemp moetemp commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

What changed?

This PR adds the Workflow publish sample and its README section.

  • path_a_workflow_publish.py publishes from the Workflow with workflow_writer, and a client reads it.
  • The README gains Path A next to the Activity path and the Workflow Activity writer. It says a record shows when the activation that published it completes, and how a rerun of a failed task reads.

Why?

A user needs a working example of each publish path in scope.

How did you test it?

Link to a test plan if any -

  • Unit Tests
  • Staging
  • End to End Tests

tests/contrib/streams/test_samples.py runs both samples against Redis and the dev server.

@moetemp moetemp added the skip-changelog Changelog entry rides another PR label Oct 13, 2026
@moetemp moetemp added the parked Parked design, not for review label Oct 14, 2026
@moetemp

moetemp commented Oct 14, 2026

Copy link
Copy Markdown
Owner Author

Closed. The Ford project (Core Workflow Task publish) is dropped. Brook now publishes from a Workflow through a local activity, with no Core change. Bridge moves onto Brook in the coming Jetty re-cut. This branch stays until then, because Bridge PRs still sit on it.

@moetemp moetemp closed this Oct 14, 2026
@moetemp
moetemp deleted the moe/ford/w5-workflow-sample branch October 14, 2026 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

parked Parked design, not for review skip-changelog Changelog entry rides another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant