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

Customizable webhooks for status updates #735

Closed
johnSchnake opened this issue May 31, 2019 · 3 comments
Closed

Customizable webhooks for status updates #735

johnSchnake opened this issue May 31, 2019 · 3 comments

Comments

@johnSchnake
Copy link
Contributor

Describe the solution you'd like
Allow the user to specify a series of webhooks/subscriptions which certain events will post back too. Examples:

Anything else you would like to add:
Webhooks we be a pretty generic way to allow other tools to be built in/around Sonobuoy without having to vendor Sonobuoy itself and use the internal methods.

It would be great to do something like:

  • launch a run in CI
  • the results automatically get put into S3
  • the final status gets passed to a slackbot and posted into a team channel

Implementing 1 webhook isn't much easier than supporting multiple, we just have to allow the user to specify them and then fire off the info as we get it.

johnSchnake added a commit that referenced this issue Sep 9, 2019
In preparation of supporting status updates, I want to clarify
the meaning of the MASTER_URL env var on the worker.

Up until now the only URL of importance was the results URL so
that is what the MASTER_URL was set to. Soon, we will have results
and status updates, so it makes sense to have the MASTER_URL simply
be the hostname and add the path on the fly depending on which
endpoint we are trying to hit.

ref #735

Signed-off-by: John Schnake <[email protected]>
@stale
Copy link

stale bot commented Nov 4, 2020

There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days.

@stale stale bot added the misc/wontfix label Nov 4, 2020
@vladimirvivien
Copy link
Contributor

cc @wilsonehusin this maybe worth revisiting as well.

@stale
Copy link

stale bot commented Jan 19, 2021

There has not been much activity here. We'll be closing this issue if there are no follow-ups within 15 days.

@stale stale bot closed this as completed Feb 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants