check_point.mgmt.cp_mgmt_resource_tcp module – Manages resource-tcp objects on Checkpoint over Web Services API
Note
This module is part of the check_point.mgmt collection (version 6.5.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 check_point.mgmt.
To use it in a playbook, specify: check_point.mgmt.cp_mgmt_resource_tcp.
New in check_point.mgmt 6.5.0
Synopsis
- Manages resource-tcp objects on Checkpoint devices including creating, updating and removing objects. 
- All operations are performed over Web Services API. 
- Available from R82 JHF management version. 
Parameters
| Parameter | Comments | 
|---|---|
| Publish the current session if changes have been performed after task completes. Choices: 
 | |
| Color of the object. Should be one of existing colors. Choices: 
 | |
| Comments string. | |
| CVP settings. | |
| Configures the CVP server to inspect but not modify content. Choices: 
 | |
| Designates when the CVP server returns data to the Security Gateway security server. Choices: 
 | |
| CVP server identified by name or UID. The CVP server must already be defined as an OPSEC Application. | |
| The level of detail for some of the fields in the response can vary from showing only the UID value of the object to a fully detailed representation of the object. Choices: 
 | |
| Indicates which domains to process the commands on. It cannot be used with the details-level full, must be run from the System Domain only and with ignore-warnings true. Valid values are, CURRENT_DOMAIN, ALL_DOMAINS_ON_THIS_SERVER. | |
| Configures how to track connections that match this rule but fail the content security checks. An example of an exception is a connection with an unsupported scheme or method. Choices: 
 | |
| Apply changes ignoring errors. You won’t be able to publish such a changes. If ignore-warnings flag was omitted - warnings will also be ignored. Choices: 
 | |
| Apply changes ignoring warnings. Choices: 
 | |
| Object name. | |
| The type of the TCP resource. Choices: 
 | |
| State of the access rule (present or absent). Choices: 
 | |
| Collection of tag identifiers. | |
| UFP settings. | |
| Specifies if and how caching is to be enabled. Choices: 
 | |
| The UFP server will be ignored after numerous UFP server connections were unsuccessful. Choices: 
 | |
| Signifies at what point the UFP server should be ignored, Applicable only if ‘ignore after fail’ is enabled. | |
| UFP server identified by name or UID. The UFP server must already be defined as an OPSEC Application. | |
| The amount of time, in seconds, that must pass before a UFP server connection should be attempted, Applicable only if ‘ignore after fail’ is enabled. | |
| Version of checkpoint. If not given one, the latest version taken. | |
| Wait for the task to end. Such as publish task. Choices: 
 | |
| How many minutes to wait until throwing a timeout error. Default:  | 
Examples
- name: add-resource-tcp
  cp_mgmt_resource_tcp:
    name: newTcpResource
    state: present
    ufp_settings:
      caching_control: security_gateway_one_request
      ignore_ufp_server_after_failure: true
      number_of_failures_before_ignore: 3
      server: ufpServer
- name: set-resource-tcp
  cp_mgmt_resource_tcp:
    cvp_settings:
      server: cvpServer
    name: newTcpResource
    state: present
    ufp_settings:
      caching_control: ufp_server
      ignore_ufp_server_after_failure: false
      number_of_failures_before_ignore: 0
- name: delete-resource-tcp
  cp_mgmt_resource_tcp:
    name: tcpResource
    state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
| Key | Description | 
|---|---|
| The checkpoint object created or updated. Returned: always, except when deleting the object. | 
