fortinet.fortimanager.fmgr_dynamic_interface – no description

Note

This plugin is part of the fortinet.fortimanager collection (version 2.1.3).

To install it use: ansible-galaxy collection install fortinet.fortimanager.

To use it in a playbook, specify: fortinet.fortimanager.fmgr_dynamic_interface.

New in version 2.10: of fortinet.fortimanager

Synopsis

  • This module is able to configure a FortiManager device.

  • Examples include all parameters and values which need to be adjusted to data sources before usage.

Parameters

Parameter Choices/Defaults Comments
adom
string / required
the parameter (adom) in requested url
bypass_validation
boolean
    Choices:
  • no ←
  • yes
only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters
dynamic_interface
dictionary
the top level parameters set
color
integer
no description
default-mapping
string
    Choices:
  • disable
  • enable
no description
defmap-intf
string
no description
defmap-intrazone-deny
string
    Choices:
  • disable
  • enable
no description
defmap-zonemember
string
no description
description
string
no description
dynamic_mapping
list / elements=string
no description
_scope
list / elements=string
no description
name
string
no description
vdom
string
no description
egress-shaping-profile
string
no description
ingress-shaping-profile
string
no description
intrazone-deny
string
    Choices:
  • disable
  • enable
no description
local-intf
string
no description
egress-shaping-profile
string
no description
ingress-shaping-profile
string
no description
name
string
no description
platform_mapping
list / elements=string
no description
egress-shaping-profile
string
no description
ingress-shaping-profile
string
no description
intf-zone
string
no description
intrazone-deny
string
    Choices:
  • disable
  • enable
no description
name
string
no description
single-intf
string
    Choices:
  • disable
  • enable ←
no description
enable_log
boolean
    Choices:
  • no ←
  • yes
Enable/Disable logging for task
proposed_method
string
    Choices:
  • update
  • set
  • add
The overridden method for the underlying Json RPC request
rc_failed
list / elements=string
the rc codes list with which the conditions to fail will be overriden
rc_succeeded
list / elements=string
the rc codes list with which the conditions to succeed will be overriden
state
string / required
    Choices:
  • present
  • absent
the directive to create, update or delete an object
workspace_locking_adom
string
the adom to lock for FortiManager running in workspace mode, the value can be global and others including root
workspace_locking_timeout
integer
Default:
300
the maximum time in seconds to wait for other user to release the workspace lock

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: no description
     fmgr_dynamic_interface:
        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, ...]
        adom: <your own value>
        state: <value in [present, absent]>
        dynamic_interface:
           color: <value of integer>
           default-mapping: <value in [disable, enable]>
           defmap-intf: <value of string>
           defmap-intrazone-deny: <value in [disable, enable]>
           defmap-zonemember: <value of string>
           description: <value of string>
           dynamic_mapping:
             -
                 _scope:
                   -
                       name: <value of string>
                       vdom: <value of string>
                 egress-shaping-profile: <value of string>
                 intrazone-deny: <value in [disable, enable]>
                 local-intf: <value of string>
                 ingress-shaping-profile: <value of string>
           egress-shaping-profile: <value of string>
           name: <value of string>
           single-intf: <value in [disable, enable]>
           ingress-shaping-profile: <value of string>
           platform_mapping:
             -
                 egress-shaping-profile: <value of string>
                 ingress-shaping-profile: <value of string>
                 intf-zone: <value of string>
                 intrazone-deny: <value in [disable, enable]>
                 name: <value of string>

Return Values

Common return values are documented here, the following are the fields unique to this module:

Key Returned Description
request_url
string
always
The full url requested

Sample:
/sys/login/user
response_code
integer
always
The status of api request

response_message
string
always
The descriptive message of the api response

Sample:
OK.


Authors

  • Link Zheng (@chillancezen)

  • Jie Xue (@JieX19)

  • Frank Shen (@fshen01)

  • Hongbin Lu (@fgtdev-hblu)