Skip to content

eventrule_configuration_template

Configuration for eventruleConfiguration Template resource.

(click to see Operations)

Properties

(click to see Operations)

NameData TypePermissionsDescription
device_family<String>Read-writeFamily of Devices for which config template is defined..
Minimum length = 1
Maximum length = 64
parent_name<String>Read-write.
commands<eventrule_config_command[]>Read-writeArray of commands part of the configuration template.
name<String>Read-writeName of configuration template.
Minimum length = 1
Maximum length = 128
variables<eventrule_config_variable[]>Read-writeArray of variables used in commands of the configuration template.
description<String>Read-writeDescription of configuration template.
Minimum length = 1
Maximum length = 1024
parent_id<String>Read-write.
tenant_id<String>Read-writeTenant Id.
Minimum length = 1
Maximum length = 128
id<String>Read-writeId is system generated key for all the configuration templates.
category<String>Read-writeCategory of configuration template.
Minimum length = 1
Maximum length = 128
is_visible<Boolean>Read-onlytrue, if this template is visible.
is_inbuilt<Boolean>Read-onlytrue, if this template is in built.

Operations

(click to see Properties)

Some options that you can use for each operations:

  • Getting warnings in response:NITRO allows you to get warnings in an operation by specifying the "warning" query parameter as "yes". For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

    http://<netscaler-ip-address>/nitro/v1/config/login?warning=yes

    If any, the warnings are displayed in the response payload with the HTTP code "209 X-NITRO-WARNING".

  • Authenticated access for individual NITRO operations:NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:

    X-NITRO-USER:<username>

    X-NITRO-PASS:<password>

    Note: In such cases, make sure that the request header DOES not include the following:

    Cookie:NITRO_AUTH_TOKEN=<tokenvalue>

Note:

Mandatory parameters are marked in red and placeholder content is marked in <green>.