Project

General

Profile

Refactor #30707

Refactor webhook model

Added by Lukas Zapletal over 1 year ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Webhook needs to be associated with a template and it needs the following fields:

  • Name - A unique name for the webhook.
  • Event - Foreman Subscription API event name.
  • Enabled - If unchecked, the webhook will be inactive.
  • HTTP method - The type of HTTP request to send. Options include GET, POST, PUT, PATCH, and DELETE.
  • URL - The fuly-qualified URL of the request to be sent. This may specify a destination port number if needed.
  • HTTP content type - The value of the request’s Content-Type header.
  • Additional headers - Any additional headers to include with the request (optional). If this supports templating (ERB) it is a bonus.
  • SSL verification - True (default) to check HTTPS, false skips certification check.
  • CA - String (textbox) with CA or concatenated CA chain to check server cert against, similarily we do in Compute Resources.

Related issues

Related to Foreman - Tracker #30290: Foreman webhooks integration storyNew

History

#1 Updated by Lukas Zapletal over 1 year ago

#2 Updated by Lukas Zapletal over 1 year ago

  • Project changed from Foreman to Webhooks

#3 Updated by Oleh Fedorenko 10 months ago

  • Status changed from New to Closed

Closing this one as it was resolved within other issues.

Also available in: Atom PDF