Note
This plugin is part of the fortinet.fortios collection (version 1.1.8).
To install it use: ansible-galaxy collection install fortinet.fortios
.
To use it in a playbook, specify: fortinet.fortios.fortios_application_name
.
New in version 2.8: of fortinet.fortios
The below requirements are needed on the host that executes this module.
Parameter | Choices/Defaults | Comments | ||
---|---|---|---|---|
access_token string | Token-based authentication. Generated from GUI of Fortigate. | |||
application_name dictionary | Configure application signatures. | |||
behavior string | Application behavior. | |||
category integer | Application category ID. | |||
id integer | Application ID. | |||
metadata list / elements=string | Meta data. | |||
id integer / required | ID. | |||
metaid integer | Meta ID. | |||
valueid integer | Value ID. | |||
name string / required | Application name. | |||
parameter string | Application parameter name. | |||
popularity integer | Application popularity. | |||
protocol string | Application protocol. | |||
risk integer | Application risk. | |||
state string |
| Deprecated Starting with Ansible 2.9 we recommend using the top-level 'state' parameter. Indicates whether to create or remove the object. | ||
sub_category integer | Application sub-category ID. | |||
technology string | Application technology. | |||
vendor string | Application vendor. | |||
weight integer | Application weight. | |||
state string added in 2.9 of fortinet.fortios |
| Indicates whether to create or remove the object. This attribute was present already in previous version in a deeper level. It has been moved out to this outer level. | ||
vdom string | Default: "root" | Virtual domain, among those defined previously. A vdom is a virtual instance of the FortiGate that can be configured and used as a different unit. |
Note
- hosts: fortigates collections: - fortinet.fortios connection: httpapi vars: vdom: "root" ansible_httpapi_use_ssl: yes ansible_httpapi_validate_certs: no ansible_httpapi_port: 443 tasks: - name: Configure application signatures. fortios_application_name: vdom: "{{ vdom }}" state: "present" access_token: "<your_own_value>" application_name: behavior: "<your_own_value>" category: "4" id: "5" metadata: - id: "7" metaid: "8" valueid: "9" name: "default_name_10" parameter: "<your_own_value>" popularity: "12" protocol: "<your_own_value>" risk: "14" sub_category: "15" technology: "<your_own_value>" vendor: "<your_own_value>" weight: "18"
Common return values are documented here, the following are the fields unique to this module:
Key | Returned | Description |
---|---|---|
build string | always | Build number of the fortigate image Sample: 1547 |
http_method string | always | Last method used to provision the content into FortiGate Sample: PUT |
http_status string | always | Last result given by FortiGate on last operation applied Sample: 200 |
mkey string | success | Master key (id) used in the last call to FortiGate Sample: id |
name string | always | Name of the table used to fulfill the request Sample: urlfilter |
path string | always | Path of the table used to fulfill the request Sample: webfilter |
revision string | always | Internal revision number Sample: 17.0.2.10658 |
serial string | always | Serial number of the unit Sample: FGVMEVYYQT3AB5352 |
status string | always | Indication of the operation's result Sample: success |
vdom string | always | Virtual domain used Sample: root |
version string | always | Version of the FortiGate Sample: v5.6.3 |
© 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.11/collections/fortinet/fortios/fortios_application_name_module.html