fortinet.fortimanager.fmgr_fmg_device_blueprint module – Fmg device blueprint
Note
This module is part of the fortinet.fortimanager collection (version 2.7.0).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install fortinet.fortimanager.
To use it in a playbook, specify: fortinet.fortimanager.fmgr_fmg_device_blueprint.
New in fortinet.fortimanager 2.1.0
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 |
Comments |
|---|---|
The token to access FortiManager without using username and password. |
|
The parameter (adom) in requested url. |
|
Only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters. Choices:
|
|
Enable/Disable logging for task. Choices:
|
|
The top level parameters set. |
|
(list) Deprecated, please rename it to auth_template. Auth template. |
|
(list) Cliprofs. |
|
Description. |
|
(list) Deprecated, please rename it to dev_group. Dev group. |
|
Deprecated, please rename it to enforce_device_config. Enforce device config. Choices:
|
|
Folder. |
|
Deprecated, please rename it to ha_config. Ha config. Choices:
|
|
Deprecated, please rename it to ha_hbdev. Ha hbdev. |
|
(list) Deprecated, please rename it to ha_monitor. Ha monitor. |
|
(list) Deprecated, please rename it to ha_password. Ha password. |
|
Deprecated, please rename it to linked_to_model. Linked to model. Choices:
|
|
Name. |
|
Pkg. |
|
Platform. |
|
Deprecated, please rename it to port_provisioning. Port provisioning. |
|
Deprecated, please rename it to prefer_img_ver. Prefer img ver. |
|
(list) Deprecated, please rename it to prerun_cliprof. Prerun cliprof. |
|
Deprecated, please rename it to prov_type. Prov type. Choices:
|
|
Deprecated, please rename it to sdwan_management. Sdwan management. Choices:
|
|
Deprecated, please rename it to split_switch_port. Split switch port. Choices:
|
|
Deprecated, please rename it to template_group. Template group. |
|
(list) Templates. |
|
Authenticate Ansible client with forticloud API access token. |
|
The overridden method for the underlying Json RPC request. Choices:
|
|
The rc codes list with which the conditions to fail will be overriden. |
|
The rc codes list with which the conditions to succeed will be overriden. |
|
The directive to create, update or delete an object. Choices:
|
|
The adom to lock for FortiManager running in workspace mode, the value can be global and others including root. |
|
The maximum time in seconds to wait for other user to release the workspace lock. Default: |
Notes
Note
Starting in version 2.4.0, all input arguments are named using the underscore naming convention (snake_case). Please change the arguments such as “var-name” to “var_name”. Old argument names are still available yet you will receive deprecation warnings. You can ignore this warning by setting deprecation_warnings=False in ansible.cfg.
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: Fmg device blueprint
fortinet.fortimanager.fmgr_fmg_device_blueprint:
# 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: present # <value in [present, absent]>
fmg_device_blueprint:
cliprofs: <list or string>
description: <string>
dev_group: <list or string>
folder: <string>
name: <string>
pkg: <string>
platform: <string>
prefer_img_ver: <string>
prerun_cliprof: <list or string>
prov_type: <value in [none, templates, template-group]>
template_group: <string>
templates: <list or string>
enforce_device_config: <value in [disable, enable]>
auth_template: <list or string>
ha_config: <value in [disable, enable]>
ha_hbdev: <string>
ha_monitor: <list or string>
ha_password: <list or string>
linked_to_model: <value in [disable, enable]>
port_provisioning: <integer>
sdwan_management: <value in [disable, enable]>
split_switch_port: <value in [disable, enable]>
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
The result of the request. Returned: always |
|
The full url requested. Returned: always Sample: |
|
The status of api request. Returned: always Sample: |
|
The api response. Returned: always |
|
The descriptive message of the api response. Returned: always Sample: |
|
The information of the target system. Returned: always |
|
The status the request. Returned: always Sample: |
|
Warning if the parameters used in the playbook are not supported by the current FortiManager version. Returned: complex |