netscaler.adc.cachecontentgroup module – Configuration for Integrated Cache content group resource.
Note
This module is part of the netscaler.adc collection (version 2.6.0).
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 netscaler.adc
.
To use it in a playbook, specify: netscaler.adc.cachecontentgroup
.
New in netscaler.adc 2.0.0
Synopsis
Configuration for Integrated Cache content group resource.
Parameters
Parameter |
Comments |
---|---|
Local time, up to 4 times a day, at which all objects in the content group must expire. CLI Users: For example, to specify that the objects in the content group should expire by 11:00 PM, type the following command: add cache contentgroup <contentgroup name> -absexpiry 23:00 To specify that the objects in the content group should expire at 10:00 AM, 3 PM, 6 PM, and 11:00 PM, type: add cache contentgroup <contentgroup name> -absexpiry 10:00 15:00 18:00 23:00 |
|
Coordinated Universal Time (GMT), up to 4 times a day, when all objects in the content group must expire. |
|
Force policy evaluation for each response arriving from the origin server. Cannot be set to Choices:
|
|
Base NITRO API path. Define only in case of an ADM service proxy call Default: |
|
Insert a Cache-Control header into the response. |
|
Force expiration of the content immediately after the response is downloaded (upon receipt of the last byte of the response body). Applicable only to positive responses. Choices:
|
|
Perform flash cache. Mutually exclusive with Poll Every Time (PET) on the same content group. Choices:
|
|
Heuristic expiry time, in percent of the duration, since the object was last modified. |
|
Parameters to use for parameterized hit evaluation of an object. Up to 128 parameters can be specified. Mutually exclusive with the Hit Selector parameter. |
|
Selector for evaluating whether an object gets stored in a particular content group. A selector is an abstraction for a collection of PIXL expressions. |
|
Flush only objects that belong to the specified host. Do not use except with parameterized invalidation. Also, the Invalidation Restricted to Host parameter for the group must be set to YES. |
|
Ignore case when comparing parameter values during parameterized hit evaluation. (Parameter value case is ignored by default during parameterized invalidation.) Choices:
|
|
Ignore any request to reload a cached object from the origin server. To guard against Denial of Service attacks, set this parameter to Choices:
|
|
Ignore Cache-Control and Pragma headers in the incoming request. Choices:
|
|
Insert an Age header into the response. An Age header contains information about the age of the object, in seconds, as calculated by the integrated cache. Choices:
|
|
Insert an ETag header in the response. With ETag header insertion, the integrated cache does not serve full responses on repeat requests. Choices:
|
|
Insert a Via header into the response. Choices:
|
|
Parameters for parameterized invalidation of an object. You can specify up to 8 parameters. Mutually exclusive with invalSelector. |
|
Take the host header into account during parameterized invalidation. Choices:
|
|
Selector for invalidating objects in the content group. A selector is an abstraction for a collection of PIXL expressions. |
|
Perform DNS resolution for responses only if the destination IP address in the request does not match the destination IP address of the cached response. Choices:
|
|
The ID of the managed NetScaler instance to which NetScaler Console has to configure as a proxy server. Define only in case of an ADM service proxy call |
|
The IP of the managed NetScaler instance to which NetScaler Console has to configure as a proxy server. Define only in case of an ADM service proxy call |
|
The name of the managed NetScaler instance to which NetScaler Console has to configure as a proxy server. Define only in case of an ADM service proxy call |
|
The password of the managed NetScaler instance. Define only in case of an ADM service proxy call In Settings > Administration > System Configurations > Basic Settings, if you select Prompt Credentials for Instance Login, ensure to configure username and password of a managed instance. |
|
The username of the managed NetScaler instance. Define only in case of an ADM service proxy call In Settings > Administration > System Configurations > Basic Settings, if you select Prompt Credentials for Instance Login, ensure to configure username and password of a managed instance. |
|
Evaluate for parameters in the cookie header also. Choices:
|
|
Maximum size of a response that can be cached in this content group. |
|
Maximum amount of memory that the cache can use. The effective limit is based on the available memory of the Citrix ADC. |
|
Number of hits that qualifies a response for storage in this content group. |
|
Minimum size of a response that can be cached in this content group.
|
|
Name for the content group. Must begin with an ASCII alphabetic or underscore (_) character, and must contain only ASCII alphanumeric, underscore, hash (#), period (.), space, colon (:), at (@), equals (=), and hyphen (-) characters. Cannot be changed after the content group is created. |
|
The IP address of the NetScaler ADC appliance acting as a proxy server. Define only in case of an ADM service proxy call Choices:
|
|
The authentication token provided by a login operation. |
|
The password with which to authenticate to the NetScaler ADC node. |
|
Which protocol to use when accessing the nitro API objects. Choices:
|
|
The username with which to authenticate to the NetScaler ADC node. |
|
The ip address of the NetScaler ADC appliance where the nitro API calls will be made. The port can be specified with the colon (:). E.g. 192.168.1.1:555. |
|
Setting persistHA to Choices:
|
|
Do not flush objects from this content group under memory pressure. Choices:
|
|
Always poll for the objects in this content group. That is, retrieve the objects from the origin server whenever they are requested. Choices:
|
|
Attempt to refresh objects that are about to go stale. Choices:
|
|
Maximum number of outstanding prefetches that can be queued for the content group. |
|
Time period, in seconds before an object’s calculated expiry time, during which to attempt prefetch. |
|
Time period, in milliseconds before an object’s calculated expiry time, during which to attempt prefetch. |
|
Query string specifying individual objects to flush from this group by using parameterized invalidation. If this parameter is not set, all objects are flushed from the group. |
|
If the size of an object that is being downloaded is less than or equal to the quick abort value, and a client aborts during the download, the cache stops downloading the response. If the object is larger than the quick abort size, the cache continues to download the response. |
|
Relative expiry time, in seconds, after which to expire an object cached in this content group. |
|
Relative expiry time, in milliseconds, after which to expire an object cached in this content group. |
|
Remove cookies from responses. Choices:
|
|
If The module will not save the configuration on the NetScaler ADC node if it made no changes. Choices:
|
|
Value of the selector to be used for flushing objects from the content group. Requires that an invalidation selector be configured for the content group. |
|
The state of the resource being configured by the module on the NetScaler ADC node. When When When When Choices:
|
|
content group whose objects are to be sent to secondary. Choices:
|
|
The type of the content group. Choices:
|
|
If Choices:
|
|
Relative expiry time, in seconds, for expiring negative responses. This value is used only if the expiry time cannot be determined from any other source. It is applicable only to the following status codes: 307, 403, 404, and 410. |
|
Relative expiry time, in seconds, for expiring positive responses with response codes between 200 and 399. Cannot be used in combination with other Expiry attributes. Similar to -relExpiry but has lower precedence. |
Notes
Note
For more information on using Ansible to manage NetScaler ADC Network devices see https://www.ansible.com/integrations/networks/citrixadc.
Examples
---
- name: Sample Playbook
hosts: localhost
gather_facts: false
tasks:
- name: Sample Task | cachecontentgroup
delegate_to: localhost
netscaler.adc.cachecontentgroup:
state: present
name: DEFAULT
- name: Sample Task | cachecontentgroup | 2
delegate_to: localhost
netscaler.adc.cachecontentgroup:
state: present
name: BASEFILE
relexpiry: 86000
weaknegrelexpiry: 600
maxressize: 256
memlimit: 2
- name: Sample Task | cachecontentgroup | 3
delegate_to: localhost
netscaler.adc.cachecontentgroup:
state: present
name: DELTAJS
relexpiry: 86000
weaknegrelexpiry: 600
insertage: 'NO'
maxressize: 256
memlimit: 1
pinned: 'YES'
- name: Sample Task | cachecontentgroup | 4
delegate_to: localhost
netscaler.adc.cachecontentgroup:
state: present
name: NSFEO
maxressize: 1994752
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Indicates if any change is made by the module Returned: always Sample: |
|
Dictionary of before and after changes Returned: always Sample: |
|
List of differences between the actual configured object and the configuration specified in the module Returned: when changed Sample: |
|
Indicates if the module failed or not Returned: always Sample: |
|
list of logged messages by the module Returned: always Sample: |