:source: faz_eventmgmt_config_correlationhandler.py :orphan: .. _faz_eventmgmt_config_correlationhandler: faz_eventmgmt_config_correlationhandler -- Config correlation-handler. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ .. versionadded:: 1.8.0 .. warning:: Starting in version 2.0.0, all variables will be named in the underscore naming convention. - Possible variable names before 2.0.0: ``variable-name``, ``variable name``, ``variable.name`` - Corresponding variable names since 2.0.0: ``variable_name`` FortiAnalyzer Ansible v1.4+ supports both previous argument name and new underscore name. You will receive deprecation warnings if you keep using the previous argument name. You can ignore the warning by setting deprecation_warnings=False in ansible.cfg. .. contents:: :local: :depth: 1 Synopsis -------- - This module is able to configure a FortiAnalyzer device. - Examples include all parameters and values need to be adjusted to data sources before usage. - This module supports check mode and diff mode. Requirements ------------ The below requirements are needed on the host that executes this module. - ansible>=2.16.0 FortiAnalyzer Version Compatibility ------------------------------------ .. raw:: html

Supported Version Ranges: v7.2.2 -> latest

Parameters ---------- .. raw:: html Notes ----- .. note:: - To create or update an object, use state: present directive. - To delete an object, use state: absent directive - Normally, running one module can fail when a non-zero rc is returned. you can also override the conditions to fail or succeed with parameters rc_failed and rc_succeeded Examples -------- .. code-block:: yaml+jinja - name: Example playbook hosts: fortianalyzers connection: httpapi gather_facts: false vars: ansible_network_os: fortinet.fortianalyzer.fortianalyzer ansible_httpapi_port: 443 ansible_httpapi_use_ssl: true ansible_httpapi_validate_certs: false tasks: - name: Config correlation-handler. fortinet.fortianalyzer.faz_eventmgmt_config_correlationhandler: # bypass_validation: false # rc_succeeded: [0, -2, -3, ...] # rc_failed: [-2, -3, ...] adom: state: present # eventmgmt_config_correlationhandler: handler_id: "your value" # Required variable, string # content_pack_id: # content_pack_uuid: # indicator: # name: # rule: # uuid: # version: # automation_stitch: # creation_time: # data_selector: # description_: # enable: # enable_time: # eventstatus: # eventtype: # extrainfo: # extrainfo_type: # mitre_info: # notification: # rule_relation: # rule_relation_constraint: # severity: # subject: # tags: # template_url: # update_time: Return Values ------------- Common return values are documented: https://docs.ansible.com/ansible/latest/reference_appendices/common_return_values.html#common-return-values, the following are the fields unique to this module: .. raw:: html
  • meta The result of the request. returned: always type: dict
    • request_url The full url requested. returned: always type: str sample: /sys/login/user
    • response_code The status of api request. returned: always type: int sample: 0
    • response_data The data body of the api response. returned: optional type: list or dict
    • response_message The descriptive message of the api response. returned: always type: str sample: OK
    • system_information The information of the target system. returned: always type: dict
  • rc The status the request. returned: always type: int sample: 0
  • version_check_warning Warning if the parameters used in the playbook are not supported by the current fortianalyzer version. returned: if params are not supported in the current version type: list
Status ------ - This module is not guaranteed to have a backwards compatible interface. Authors ------- - Xinwei Du (@dux-fortinet) - Maxx Liu (@MaxxLiu22) - Link Zheng (@chillancezen) - Jie Xue (@JieX19) - Frank Shen (@fshen01) - Hongbin Lu (@fgtdev-hblu)