Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

Feature: Webhooks for workflow and task status #228

Open
wants to merge 41 commits into
base: main
Choose a base branch
from

Conversation

charybr
Copy link
Contributor

@charybr charybr commented May 24, 2023

Pull Request type

  • Bugfix
  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build related changes (Please run ./gradlew generateLock saveLock to refresh dependencies)
  • WHOSUSING.md
  • Other (please describe):

Changes in this PR

Describe the new behavior from this PR, and why it's needed
Issue #212

Webhooks for workflow and task status

Problem:
We have a requirement to publish status of workflow and task to a Webhook.

Approach:
WorkflowStatusListener and TaskStatusListener interfaces can be implemented to call webhooks when there is a change in status of workflow and task. We can add new module called 'webhook'.

This PR is originated from the changes done by @techyragu (Rahul Gupta) done on CiscoM31/conductor CiscoM31/conductor#26.

Alternatives considered

Describe alternative implementation you have considered

@charybr charybr changed the title Feature/task webhook Feature: Webhooks for workflow and task status May 24, 2023

public String workflowTaskType;
private String domainGroupMoId = "";
private String accountMoId = "";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like an application specific field. The notification should be a generic class.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you Viren for reviewing! Yes, both accountMoId and domainGroupMoId are custom fields. I will work on it and get back.

Copy link

@youngledo youngledo Jun 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, this property configuration takes effect when the conductor server is started, but there may be multiple clients using it in practice. Can I set different URLs and endpoint according to different clients?

image

for example:
image
image

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you Huang! for the comments. i will check if we can build url dynamically.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you Huang! for the comments. i will check if we can build url dynamically.

Hi, @charybr ! This is my PR regarding this issue(charybr#1). Could you consider merging?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thats great Huang! Thank you. Give me 3-4 days i will check and merge by this weekend.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Huang, i have merged your PR. thank you!

Copy link

@youngledo youngledo Aug 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, how's it going? @charybr

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

review is pending

@charybr
Copy link
Contributor Author

charybr commented Aug 24, 2023

Hi @youngledo , your changes were in branch charybr:feature/webhook. I cherry-picked your commits into branch of this PR i.e. charybr:feature/task_webhook.

So please review below commits:
20a609d
42c7ae2

@youngledo
Copy link

Hi @youngledo , your changes were in branch charybr:feature/webhook. I cherry-picked your commits into branch of this PR i.e. charybr:feature/task_webhook.

So please review below commits: 20a609d 42c7ae2

OK, I've already reviewed it.

@charybr charybr mentioned this pull request Sep 28, 2023
6 tasks
@manan164
Copy link
Contributor

manan164 commented Oct 3, 2023

Hi @charybr , Please make the below changes,

  1. Remove usage of webhook as it is conflicting with system task webhooks in workflow
  2. Make workflow publisher part of workflow-status-event-listerner module
  3. Add new module task-status-listener and move task status related changes there.

Copy link

This PR is stale, because it has been open for 45 days with no activity. Remove the stale label or comment, or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Nov 18, 2023
@charybr
Copy link
Contributor Author

charybr commented Nov 20, 2023

Commenting so that Stale label gets removed. Will work on the review comments in Dec.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants