cisco.ise.filter_policy module – Resource module for Filter Policy
Note
This module is part of the cisco.ise collection (version 2.4.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 cisco.ise
.
To use it in a playbook, specify: cisco.ise.filter_policy
.
New in version 1.0.0: of cisco.ise
Synopsis
Manage operations create, update and delete of the resource Filter Policy.
This API creates a filter policy.
This API deletes a filter policy.
This API allows the client to update a filter policy.
Note
This module has a corresponding action plugin.
Requirements
The below requirements are needed on the host that executes this module.
ciscoisesdk >= 2.0.1
python >= 3.5
Parameters
Parameter |
Comments |
---|---|
List of SXP Domains, separated with comma. |
|
Id path parameter. |
|
Flag for Identity Services Engine SDK to enable debugging. Choices:
|
|
The Identity Services Engine hostname. |
|
The Identity Services Engine password to authenticate. |
|
The Identity Services Engine username to authenticate. |
|
Flag that informs the SDK whether to use the Identity Services Engine’s API Gateway to send requests. If it is true, it uses the ISE’s API Gateway and sends requests to https://{{ise_hostname}}. If it is false, it sends the requests to https://{{ise_hostname}}:{{port}}, where the port value depends on the Service used (ERS, Mnt, UI, PxGrid). Choices:
|
|
Flag that informs the SDK whether we send the CSRF token to ISE’s ERS APIs. If it is True, the SDK assumes that your ISE CSRF Check is enabled. If it is True, it assumes you need the SDK to manage the CSRF token automatically for you. Choices:
|
|
Flag to enable or disable SSL certificate verification. Choices:
|
|
Informs the SDK which version of Identity Services Engine to use. Default: “3.1.1” |
|
Flag for Identity Services Engine SDK to enable automatic rate-limit handling. Choices:
|
|
SGT name or ID. At least one of subnet or sgt or vn should be defined. |
|
Subnet for filter policy (hostname is not supported). At least one of subnet or sgt or vn should be defined. |
|
Virtual Network. At least one of subnet or sgt or vn should be defined. |
Notes
Note
SDK Method used are filter_policy.FilterPolicy.create_filter_policy, filter_policy.FilterPolicy.delete_filter_policy_by_id, filter_policy.FilterPolicy.update_filter_policy_by_id,
Paths used are post /ers/config/filterpolicy, delete /ers/config/filterpolicy/{id}, put /ers/config/filterpolicy/{id},
Does not support
check_mode
The plugin runs on the control node and does not use any ansible connection plugins, but instead the embedded connection manager from Cisco ISE SDK
The parameters starting with ise_ are used by the Cisco ISE Python SDK to establish the connection
Examples
- name: Update by id
cisco.ise.filter_policy:
ise_hostname: "{{ise_hostname}}"
ise_username: "{{ise_username}}"
ise_password: "{{ise_password}}"
ise_verify: "{{ise_verify}}"
state: present
domains: string
id: string
sgt: string
subnet: string
vn: string
- name: Delete by id
cisco.ise.filter_policy:
ise_hostname: "{{ise_hostname}}"
ise_username: "{{ise_username}}"
ise_password: "{{ise_password}}"
ise_verify: "{{ise_verify}}"
state: absent
id: string
- name: Create
cisco.ise.filter_policy:
ise_hostname: "{{ise_hostname}}"
ise_username: "{{ise_username}}"
ise_password: "{{ise_password}}"
ise_verify: "{{ise_verify}}"
state: present
domains: string
sgt: string
subnet: string
vn: string
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
A dictionary or list with the response returned by the Cisco ISE Python SDK Returned: always Sample: “{\n \”subnet\”: \”string\”,\n \”domains\”: \”string\”,\n \”sgt\”: \”string\”,\n \”vn\”: \”string\”\n}\n” |
|
A dictionary or list with the response returned by the Cisco ISE Python SDK Returned: always Sample: “{\n \”UpdatedFieldsList\”: {\n \”updatedField\”: [\n {\n \”field\”: \”string\”,\n \”oldValue\”: \”string\”,\n \”newValue\”: \”string\”\n }\n ],\n \”field\”: \”string\”,\n \”oldValue\”: \”string\”,\n \”newValue\”: \”string\”\n }\n}\n” |