Skip to content
Was this article helpful?

autoscalegroup_profile_map

Configuration for Auto-Scale Group provision details for each availability zone resource.

Properties

(click to see Operations )

Name Data Type Permissions Description
azure_resource_group_name <String> Read-write Resource group name for Azure.

Maximum length = 128
parent_name <String> Read-write Parent name of autoscale group.
provision_job_id <String> Read-write The job id generated for provisoning of failed node from provisioning service.

Maximum length = 128
is_availability_set <Boolean> Read-write Azure: If this profile belongs to availability set.
availability_zone <String> Read-write availability_zone of autoscalegroup.

Minimum length = 1

Maximum length = 128
retry_err_type <String> Read-write Enable/Disable provisioning retry.

Maximum length = 50
parent_id <String> Read-write Parent Id of autoscalegroup.
error_message <String> Read-write Provision error message.

Maximum length = 255
provision_profile_id <String> Read-write ID of provision profile.

Minimum length = 1
is_active_node_prov <Boolean> Read-write This is to refer if the provisioning inprogress/failed/success is on active/passive node.
id <String> Read-write Id is system generated key for all the profiles.
autoscalegroup_name <String> Read-write Auto-Scale Group Name.
cluster_ip_address <String> Read-only NS Cluster IP Address.

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

    The following parameters can be used in the nitro request : onerror <String_value>

    Use this parameter to set the onerror status for nitro request. Applicable only for bulk requests.

    Default value: EXIT

    Possible values = EXIT, CONTINUE

    Was this article helpful?