From b32b5930b264740b20b8c94c9da3f4890175a267 Mon Sep 17 00:00:00 2001 From: licanwei Date: Fri, 14 Feb 2020 10:59:34 +0800 Subject: [PATCH] Add config option enable_webhooks_auth Partially Implements: blueprint event-driven-optimization-based Change-Id: Id88fa1d7c7fa49ccdfbeb011a4acca8626727b4d --- specs/ussuri/approved/event-driven-optimization-based.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/specs/ussuri/approved/event-driven-optimization-based.rst b/specs/ussuri/approved/event-driven-optimization-based.rst index daae1ac1..d64c3890 100644 --- a/specs/ussuri/approved/event-driven-optimization-based.rst +++ b/specs/ussuri/approved/event-driven-optimization-based.rst @@ -31,6 +31,10 @@ Proposed change Many monitor system, such as `aodh`_, can set `webhook`_ as alarm action, a POST request will be sent if the alarm is trigered. +About the authentication of the POST request, Aodh's `alarm action`_ +can set prefix ``trust`` to add a ``X-Auth-Token`` header to the request url. +Watcher add a new config option ``enable_webhooks_auth`` to decide whether +to enable webhook authentication, the default is True. Watcher add the mechanism for receiving and handling alarm events. Here is the summary processing: @@ -42,6 +46,7 @@ Watcher executes the audit and creates actionplan. .. _aodh: https://docs.openstack.org/aodh/latest/admin/telemetry-alarms.html#event-based-alarm .. _webhook: https://en.wikipedia.org/wiki/Webhook +.. _alarm action: https://docs.openstack.org/aodh/latest/admin/telemetry-alarms.html Alternatives ------------