paloaltonetworks.panos.panos_application_filter module – Manage application filters on PAN-OS devices.
Note
This module is part of the paloaltonetworks.panos collection (version 2.21.2).
To install it, use: ansible-galaxy collection install paloaltonetworks.panos
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: paloaltonetworks.panos.panos_application_filter
.
New in paloaltonetworks.panos 2.1.0
Synopsis
Manage application filters on PAN-OS devices.
Requirements
The below requirements are needed on the host that executes this module.
pan-python can be obtained from PyPI https://pypi.python.org/pypi/pan-python
pandevice can be obtained from PyPI https://pypi.python.org/pypi/pandevice
Parameters
Parameter |
Comments |
---|---|
Deprecated Use provider to specify PAN-OS connectivity instead. The API key to use instead of generating it using username / password. |
|
Application category |
|
(Panorama only) The device group the operation should target. Default: :ansible-option-default:`"shared"` |
|
If the applications are evasive Choices: |
|
If the applications use excessive bandwidth Choices: |
|
When state=gathered. An advanced filtering option to filter results returned from PAN-OS. Refer to the guide discussing gathered_filter for more information. |
|
If the applications have known vulnerabilities Choices: |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The IP address or hostname of the PAN-OS device being configured. |
|
If the applications are SaaS Choices: |
|
Name of the object. |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The password to use for authentication. This is ignored if api_key is specified. |
|
If the applications are used pervasively Choices: |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The port number to connect to the PAN-OS device on. Default: :ansible-option-default:`443` |
|
If the applications are prone to misuse Choices: |
|
A dict object containing connection details. |
|
The API key to use instead of generating it using username / password. |
|
The IP address or hostname of the PAN-OS device being configured. |
|
The password to use for authentication. This is ignored if api_key is specified. |
|
The port number to connect to the PAN-OS device on. Default: :ansible-option-default:`443` |
|
The serial number of a firewall to use for targeted commands. If ip_address is not a Panorama PAN-OS device, then this param is ignored. |
|
The username to use for authentication. This is ignored if api_key is specified. Default: :ansible-option-default:`"admin"` |
|
Application subcategory |
|
Administrative tags |
|
Application technology |
|
If the applications transfer files Choices: |
|
If the applications tunnel other applications Choices: |
|
If the applications are used by malware Choices: |
|
Deprecated Use provider to specify PAN-OS connectivity instead. The username to use for authentication. This is ignored if api_key is specified. Default: :ansible-option-default:`"admin"` |
|
The vsys this object belongs to. Default: :ansible-option-default:`"vsys1"` |
Notes
Note
Panorama is supported.
Check mode is supported.
PAN-OS connectivity should be specified using provider or the classic PAN-OS connectivity params (ip_address, username, password, api_key, and port). If both are present, then the classic params are ignored.
Examples
- name: Create application filter
paloaltonetworks.panos.panos_application_filter:
provider: '{{ provider }}'
name: 'custom-apps'
category: ['business-systems']
subcategory: ['auth-service']
technology: ['client-server']
risk: ['1']
- name: Remove custom application
paloaltonetworks.panos.panos_application_filter:
provider: '{{ provider }}'
name: 'custom-apps'
state: 'absent'