Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publisher: attempt publishing both task, statusValue before returning an error #34

Merged
merged 6 commits into from
Sep 6, 2024

Conversation

joelrebel
Copy link
Member

@joelrebel joelrebel commented Sep 2, 2024

  • Ensure the task, status value updates are published regardless of a failure in either.
  • The Condition gets finalized in active-conditions as soon as status value includes a final state, this would prevent the Task from being updated since the condition is no longer active.
  • Setup the traceID, spanID from the condition payload.

Long term Status Value KV is to be replaced by the Task KV, until this this arrangement lets us work with both.

… an error

- Ensure the task, status value updates are published regardless of a
  failure in either.
- The Condition gets finalized in active-conditions as soon as status
  value includes a final state, this would prevent the Task from being
  updated since the condition is no longer active.

Long term Status Value KV is to be replaced by the Task KV,
until this this arrangement lets us work with both.
Instead of depending on it being passed through the NATS header
from a message on the stream. Not all conditions are published through
the stream and so the Condition payload now includes the trace, span IDs
for linking work across controllers
splaspood
splaspood previously approved these changes Sep 4, 2024
@joelrebel joelrebel merged commit cf7a3d0 into main Sep 6, 2024
6 checks passed
@joelrebel joelrebel deleted the task-publish branch September 6, 2024 08:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants