-
Notifications
You must be signed in to change notification settings - Fork 356
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
Webhooks #1836
Milestone
Comments
dvsrepo
added
area: server
Indicates that an issue or pull request is related to the server
client
labels
Mar 2, 2022
frascuchon
removed
client
area: server
Indicates that an issue or pull request is related to the server
labels
Jul 12, 2022
This issue is stale because it has been open for 30 days with no activity. |
github-actions
bot
added
the
status: stale
Indicates that there is no activity on an issue or pull request
label
Dec 28, 2022
frascuchon
removed
the
status: stale
Indicates that there is no activity on an issue or pull request
label
Jan 9, 2023
1 task
This was referenced Sep 16, 2024
jfcalvo
added a commit
that referenced
this issue
Sep 16, 2024
# Description As discussed this PR is moving `webhooks` folder outside `api` folder. Now that we have specific schemas for webhooks it does not have much sense to have this code inside the `api` folder. Refs #1836 **Type of change** - Refactor (change restructuring the codebase without changing functionality) **How Has This Been Tested** - [x] Running test suite. **Checklist** - I added relevant documentation - I followed the style guidelines of this project - I did a self-review of my code - I made corresponding changes to the documentation - I confirm My changes generate no new warnings - I have added tests that prove my fix is effective or that my feature works - I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
jfcalvo
added a commit
that referenced
this issue
Sep 16, 2024
# Description As discussed we want to stop using `response.upserted` webhook event and instead use `response.created` or `response.updated` when a response is upserted. Refs #1836 **Type of change** - New feature (non-breaking change which adds functionality) **How Has This Been Tested** - [x] Running test suite. **Checklist** - I added relevant documentation - I followed the style guidelines of this project - I did a self-review of my code - I made corresponding changes to the documentation - I confirm My changes generate no new warnings - I have added tests that prove my fix is effective or that my feature works - I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a user I want to have the ability to register webhooks so I can trigger certain actions when specific events happen.
One could have triggers for at least:
Dataset events would add the most value for automation
The text was updated successfully, but these errors were encountered: