fmgr_dvmdb_adom – ADOM table, most attributes are read-only and can only be changed internally.

New in version 2.10.

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.0.0.

Requirements

The below requirements are needed on the host that executes this module.

  • ansible>=2.9.0

Parameters

  • 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
  • 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
  • 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
  • state - The directive to create, update or delete an object type: str required: true choices: present, absent
  • dvmdb_adom - ADOM table, most attributes are read-only and can only be changed internally. type: dict
    • desc - No description for the parameter type: str
    • flags - No description for the parameter type: array choices: [migration, db_export, no_vpn_console, backup, other_devices, central_sdwan, is_autosync, per_device_wtp, policy_check_on_install, install_on_policy_check_fail, auto_push_cfg]
    • log_db_retention_hours - No description for the parameter type: int default: 1440
    • log_disk_quota - No description for the parameter type: int
    • log_disk_quota_alert_thres - No description for the parameter type: int default: 90
    • log_disk_quota_split_ratio - No description for the parameter type: int default: 70
    • log_file_retention_hours - No description for the parameter type: int default: 8760
    • meta fields - No description for the parameter type: dict
    • mig_mr - No description for the parameter type: int default: 2
    • mig_os_ver - No description for the parameter type: str choices: [unknown, 0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0] default: 6.0
    • mode - ems - (Value no longer used as of 4. type: str choices: [ems, gms, provider] default: gms
    • mr - No description for the parameter type: int default: 2
    • name - No description for the parameter type: str
    • os_ver - No description for the parameter type: str choices: [unknown, 0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0] default: 6.0
    • restricted_prds - No description for the parameter type: array choices: [fos, foc, fml, fch, fwb, log, fct, faz, fsa, fsw, fmg, fdd, fac, fpx]
    • state - No description for the parameter type: int default: 1
    • uuid - No description for the parameter type: str

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

- hosts: fortimanager-inventory
  collections:
    - fortinet.fortimanager
  connection: httpapi
  vars:
     ansible_httpapi_use_ssl: True
     ansible_httpapi_validate_certs: False
     ansible_httpapi_port: 443
  tasks:
   - name: ADOM table, most attributes are read-only and can only be changed internally.
     fmgr_dvmdb_adom:
        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, ...]
        state: <value in [present, absent]>
        dvmdb_adom:
           desc: <value of string>
           flags:
             - migration
             - db_export
             - no_vpn_console
             - backup
             - other_devices
             - central_sdwan
             - is_autosync
             - per_device_wtp
             - policy_check_on_install
             - install_on_policy_check_fail
             - auto_push_cfg
           log_db_retention_hours: <value of integer>
           log_disk_quota: <value of integer>
           log_disk_quota_alert_thres: <value of integer>
           log_disk_quota_split_ratio: <value of integer>
           log_file_retention_hours: <value of integer>
           meta fields: <value of dict>
           mig_mr: <value of integer>
           mig_os_ver: <value in [unknown, 0.0, 1.0, ...]>
           mode: <value in [ems, gms, provider]>
           mr: <value of integer>
           name: <value of string>
           os_ver: <value in [unknown, 0.0, 1.0, ...]>
           restricted_prds:
             - fos
             - foc
             - fml
             - fch
             - fwb
             - log
             - fct
             - faz
             - fsa
             - fsw
             - fmg
             - fdd
             - fac
             - fpx
           state: <value of integer>
           uuid: <value of string>

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:

  • 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_message - The descriptive message of the api response returned: always type: str sample: OK
  • response_data - The data body of the api response returned: optional type: list or dict

Status

  • This module is not guaranteed to have a backwards compatible interface.

Authors

  • Link Zheng (@chillancezen)
  • Jie Xue (@JieX19)
  • Frank Shen (@fshen01)
  • Hongbin Lu (@fgtdev-hblu)

Hint

If you notice any issues in this documentation, you can create a pull request to improve it.