fortinet / fortinet.fortianalyzer / 1.4.0 / module / faz_cli_system_connector Configure connector. | "added in version" 1.0.0 of fortinet.fortianalyzer" Authors: Xinwei Du (@dux-fortinet), Link Zheng (@chillancezen), Jie Xue (@JieX19), Frank Shen (@fshen01), Hongbin Lu (@fgtdev-hblu) preview | supported by communityfortinet.fortianalyzer.faz_cli_system_connector (1.4.0) — module
Install with ansible-galaxy collection install fortinet.fortianalyzer:==1.4.0
collections: - name: fortinet.fortianalyzer version: 1.4.0
This module is able to configure a FortiAnalyzer device.
Examples include all parameters and values which need to be adjusted to data sources before usage.
- name: Example playbook connection: httpapi hosts: fortianalyzers tasks: - name: Configure connector. fortinet.fortianalyzer.faz_cli_system_connector: cli_system_connector: fsso_refresh_interval: 180 fsso_sess_timeout: 300 px_refresh_interval: 300 px_svr_timeout: 900 vars: ansible_httpapi_port: 443 ansible_httpapi_use_ssl: true ansible_httpapi_validate_certs: false
log_path: default: /tmp/fortianalyzer.ansible.log description: - The path to save log. Used if enable_log is true. - Please use absolute path instead of relative path. - If the log_path setting is incorrect, the log will be saved in /tmp/fortianalyzer.ansible.log required: false type: str rc_failed: description: the rc codes list with which the conditions to fail will be overriden elements: int required: false type: list enable_log: default: false description: Enable/Disable logging for task required: false type: bool access_token: description: The token to access FortiManager without using username and password. required: false type: str rc_succeeded: description: the rc codes list with which the conditions to succeed will be overriden elements: int required: false type: list proposed_method: choices: - set - update - add description: The overridden method for the underlying Json RPC request required: false type: str bypass_validation: default: false description: only set to True when module schema diffs with FortiAnalyzer API structure, module continues to execute without validating parameters required: false type: bool cli_system_connector: description: The top level parameters set. required: false suboptions: cloud-orchest-refresh-interval: description: Cloud Orchestration refresh interval (300 - 1800 seconds). type: int conn-refresh-interval: description: connector refresh interval (60 - 1800 seconds). type: int faznotify-msg-queue-max: description: faznotify max queued message per connector (10 - 10000). type: int faznotify-msg-timeout: description: faznotify message timeout (1 - 720 hours). type: int fsso-refresh-interval: description: FSSO refresh interval (60 - 600 seconds). type: int fsso-sess-timeout: description: FSSO session timeout (60 - 600 seconds). type: int px-refresh-interval: description: pxGrid refresh interval (60 - 1800 seconds). type: int px-svr-timeout: description: pxGrid server timeout (30 - 600 seconds). type: int type: dict forticloud_access_token: description: Authenticate Ansible client with forticloud API access token. required: false type: str
meta: contains: request_url: description: The full url requested returned: always sample: /sys/login/user type: str response_code: description: The status of api request returned: always sample: 0 type: int response_data: description: The api response returned: always type: list response_message: description: The descriptive message of the api response returned: always sample: OK. type: str system_information: description: The information of the target system. returned: always type: dict description: The result of the request. returned: always type: dict rc: description: The status the request. returned: always sample: 0 type: int version_check_warning: description: Warning if the parameters used in the playbook are not supported by the current fortianalyzer version. returned: complex type: list