From d2eb7a6cc17d08bfd9083b2be04cc41fae36e413 Mon Sep 17 00:00:00 2001 From: Richlv Date: Sat, 26 Jan 2019 14:17:39 +0200 Subject: [PATCH] Document trigger_severity values (#51331) * Document the valid values for trigger_severity. * Minor typo fix. +label: docsite_pr --- lib/ansible/modules/monitoring/zabbix/zabbix_action.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/lib/ansible/modules/monitoring/zabbix/zabbix_action.py b/lib/ansible/modules/monitoring/zabbix/zabbix_action.py index 79764ca8fc..85fe3f8007 100644 --- a/lib/ansible/modules/monitoring/zabbix/zabbix_action.py +++ b/lib/ansible/modules/monitoring/zabbix/zabbix_action.py @@ -112,6 +112,9 @@ options: are C(item in not supported state), C(item in normal state), C(LLD rule in not supported state), C(LLD rule in normal state), C(trigger in unknown state), C(trigger in normal state). + - When I(type) is set to C(trigger_severity), the choices + are (case-insensitive) C(not classified), C(information), C(warning), C(average), C(high), C(disaster) + irrespective of user-visible names being changed in Zabbix. Defaults to C(not classified) if omitted. - Besides the above options, this is usualy either the name of the object or a string to compare with. operator: @@ -1436,7 +1439,7 @@ class Filter(object): except Exception as e: self._module.fail_json( msg="""Unsupported value '%s' for specified condition type. - Check out Zabbix API documetation for supported values for + Check out Zabbix API documentation for supported values for condition type '%s' at https://www.zabbix.com/documentation/3.4/manual/api/reference/action/object#action_filter_condition""" % (value, conditiontype) )