fmgr_system_connector – Configure connector.
Added in version 2.0.0.
Warning
Starting in version 3.0.0, all input arguments will be named using the underscore naming convention (snake_case).
Argument name before 3.0.0:
var-name,var name,var.nameNew argument name starting in 3.0.0:
var_name
FortiManager Ansible v2.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.
Synopsis
This module is able to configure a FortiManager device.
Examples include all parameters and values need to be adjusted to data sources before usage.
Tested with FortiManager v6.x and v7.x.
Requirements
The below requirements are needed on the host that executes this module.
ansible>=2.15.0
FortiManager Version Compatibility
Supported Version Ranges: v6.0.0 -> latest
Parameters
- access_token -The token to access FortiManager without using username and password. type: str required: false
- bypass_validation - Only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters. type: bool required: false default: False
- enable_log - Enable/Disable logging for task. type: bool required: false default: False
- forticloud_access_token - Access token of forticloud managed API users, this option is available with FortiManager later than 6.4.0. type: str required: false
- proposed_method - The overridden method for the underlying Json RPC request. type: str required: false choices: set, update, add
- rc_succeeded - The rc codes list with which the conditions to succeed will be overriden. type: list required: false
- rc_failed - The rc codes list with which the conditions to fail will be overriden. type: list required: false
- workspace_locking_adom - Acquire the workspace lock if FortiManager is running in workspace mode. type: str required: false choices: global, custom adom including root
- workspace_locking_timeout - The maximum time in seconds to wait for other users to release workspace lock. type: integer required: false default: 300
- system_connector - Configure connector. type: dict
- fsso_refresh_interval (Alias name: fsso-refresh-interval) Fsso refresh interval (60 - 1800 seconds). type: int default: 180 more...
- fsso_sess_timeout (Alias name: fsso-sess-timeout) Fsso session timeout (30 - 600 seconds). type: int default: 300 more...
- px_refresh_interval (Alias name: px-refresh-interval) Pxgrid refresh interval (60 - 1800 seconds). type: int default: 300 more...
- px_svr_timeout (Alias name: px-svr-timeout) Pxgrid server timeout (30 - 600 seconds). type: int default: 900 more...
- conn_refresh_interval (Alias name: conn-refresh-interval) Connector refresh interval (60 - 1800 seconds). type: int default: 300 more...
- cloud_orchest_refresh_interval (Alias name: cloud-orchest-refresh-interval) Cloud orchestration refresh interval (300 - 1800 seconds). type: int default: 300 more...
- faznotify_msg_queue_max (Alias name: faznotify-msg-queue-max) Faznotify max queued message per connector (10 - 10000). type: int default: 1000 more...
- faznotify_msg_timeout (Alias name: faznotify-msg-timeout) Faznotify message timeout (1 - 720 hours). type: int default: 72 more...
Notes
Note
Running in workspace locking mode is supported in this FortiManager module, the top level parameters workspace_locking_adom and workspace_locking_timeout help do the work.
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
- name: Example playbook (generated based on argument schema)
hosts: fortimanagers
connection: httpapi
vars:
ansible_httpapi_use_ssl: true
ansible_httpapi_validate_certs: false
ansible_httpapi_port: 443
tasks:
- name: Configure connector.
fortinet.fortimanager.fmgr_system_connector:
# bypass_validation: false
workspace_locking_adom: <value in [global, custom adom including root]>
workspace_locking_timeout: 300
# rc_succeeded: [0, -2, -3, ...]
# rc_failed: [-2, -3, ...]
system_connector:
fsso_refresh_interval: <integer>
fsso_sess_timeout: <integer>
px_refresh_interval: <integer>
px_svr_timeout: <integer>
conn_refresh_interval: <integer>
cloud_orchest_refresh_interval: <integer>
faznotify_msg_queue_max: <integer>
faznotify_msg_timeout: <integer>
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:
- 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 FortiManager version. returned: if at least one parameter not supported by the current FortiManager version type: list
Status
This module is not guaranteed to have a backwards compatible interface.