@azure-rest/batch 1.0.0-beta.1 → 1.0.0-beta.2

package/dist/esm/models.js.map

@@ -1 +1 @@
-{"version":3,"file":"models.js","sourceRoot":"","sources":["../../src/models.ts"],"names":[],"mappings":"AAAA,uCAAuC;AACvC,kCAAkC","sourcesContent":["// Copyright (c) Microsoft Corporation.\n// Licensed under the MIT license.\n\n/** Parameters for creating an Azure Batch Pool. */\nexport interface BatchPoolCreateContent {\n  /** A string that uniquely identifies the Pool within the Account. The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two Pool IDs within an Account that differ only by case). */\n  id: string;\n  /** The display name for the Pool. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** The size of virtual machines in the Pool. All virtual machines in a Pool are the same size. For information about available VM sizes for Pools using Images from the Virtual Machines Marketplace (pools created with virtualMachineConfiguration), see Sizes for Virtual Machines (Linux) (https://azure.microsoft.com/documentation/articles/virtual-machines-linux-sizes/) or Sizes for Virtual Machines (Windows) (https://azure.microsoft.com/documentation/articles/virtual-machines-windows-sizes/). Batch supports all Azure VM sizes except STANDARD_A0 and those with premium storage (STANDARD_GS, STANDARD_DS, and STANDARD_DSV2 series). */\n  vmSize: string;\n  /** The virtual machine configuration for the Pool. This property must be specified. */\n  virtualMachineConfiguration?: VirtualMachineConfiguration;\n  /** The timeout for allocation of Compute Nodes to the Pool. This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  resizeTimeout?: string;\n  /** The user-specified tags associated with the pool. The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. */\n  resourceTags?: Record<string, string>;\n  /** The desired number of dedicated Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. */\n  targetDedicatedNodes?: number;\n  /** The desired number of Spot/Low-priority Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. */\n  targetLowPriorityNodes?: number;\n  /** Whether the Pool size should automatically adjust over time. If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula property is required and the Pool automatically resizes according to the formula. The default value is false. */\n  enableAutoScale?: boolean;\n  /** A formula for the desired number of Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. For more information about specifying this formula, see 'Automatically scale Compute Nodes in an Azure Batch Pool' (https://azure.microsoft.com/documentation/articles/batch-automatic-scaling/). */\n  autoScaleFormula?: string;\n  /** The time interval at which to automatically adjust the Pool size according to the autoscale formula. The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  autoScaleEvaluationInterval?: string;\n  /** Whether the Pool permits direct communication between Compute Nodes. Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. */\n  enableInterNodeCommunication?: boolean;\n  /** The network configuration for the Pool. */\n  networkConfiguration?: NetworkConfiguration;\n  /** A Task specified to run on each Compute Node as it joins the Pool. The Task runs when the Compute Node is added to the Pool or when the Compute Node is restarted. */\n  startTask?: BatchStartTask;\n  /** The list of Packages to be installed on each Compute Node in the Pool. When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** The number of task slots that can be used to run concurrent tasks on a single compute node in the pool. The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. */\n  taskSlotsPerNode?: number;\n  /** How Tasks are distributed across Compute Nodes in a Pool. If not specified, the default is spread. */\n  taskSchedulingPolicy?: BatchTaskSchedulingPolicy;\n  /** The list of user Accounts to be created on each Compute Node in the Pool. */\n  userAccounts?: Array<UserAccount>;\n  /** A list of name-value pairs associated with the Pool as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n  /** Mount storage using specified file system for the entire lifetime of the pool. Mount the storage using Azure fileshare, NFS, CIFS or Blobfuse based file system. */\n  mountConfiguration?: Array<MountConfiguration>;\n  /** The desired node communication mode for the pool. If omitted, the default value is Default. */\n  targetNodeCommunicationMode?: BatchNodeCommunicationMode;\n  /** The upgrade policy for the Pool. Describes an upgrade policy - automatic, manual, or rolling. */\n  upgradePolicy?: UpgradePolicy;\n}\n\n/**\n * The configuration for Compute Nodes in a Pool based on the Azure Virtual\n * Machines infrastructure.\n */\nexport interface VirtualMachineConfiguration {\n  /** A reference to the Azure Virtual Machines Marketplace Image or the custom Virtual Machine Image to use. */\n  imageReference: ImageReference;\n  /** The SKU of the Batch Compute Node agent to be provisioned on Compute Nodes in the Pool. The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. */\n  nodeAgentSKUId: string;\n  /** Windows operating system settings on the virtual machine. This property must not be specified if the imageReference property specifies a Linux OS Image. */\n  windowsConfiguration?: WindowsConfiguration;\n  /** The configuration for data disks attached to the Compute Nodes in the Pool. This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://docs.microsoft.com/en-us/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://docs.microsoft.com/en-us/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. */\n  dataDisks?: Array<DataDisk>;\n  /**\n   * This only applies to Images that contain the Windows operating system, and\n   * should only be used when you hold valid on-premises licenses for the Compute\n   * Nodes which will be deployed. If omitted, no on-premises licensing discount is\n   * applied. Values are:\n   *\n   *  Windows_Server - The on-premises license is for Windows\n   * Server.\n   *  Windows_Client - The on-premises license is for Windows Client.\n   *\n   */\n  licenseType?: string;\n  /** The container configuration for the Pool. If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. */\n  containerConfiguration?: ContainerConfiguration;\n  /** The disk encryption configuration for the pool. If specified, encryption is performed on each node in the pool during node provisioning. */\n  diskEncryptionConfiguration?: DiskEncryptionConfiguration;\n  /** The node placement configuration for the pool. This configuration will specify rules on how nodes in the pool will be physically allocated. */\n  nodePlacementConfiguration?: BatchNodePlacementConfiguration;\n  /** The virtual machine extension for the pool. If specified, the extensions mentioned in this configuration will be installed on each node. */\n  extensions?: Array<VMExtension>;\n  /** Settings for the operating system disk of the Virtual Machine. */\n  osDisk?: OSDisk;\n  /** Specifies the security profile settings for the virtual machine or virtual machine scale set. */\n  securityProfile?: SecurityProfile;\n  /** Specifies the service artifact reference id used to set same image version for all virtual machines in the scale set when using 'latest' image version. The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} */\n  serviceArtifactReference?: ServiceArtifactReference;\n}\n\n/**\n * A reference to an Azure Virtual Machines Marketplace Image or a Azure Compute Gallery Image.\n * To get the list of all Azure Marketplace Image references verified by Azure Batch, see the\n * ' List Supported Images ' operation.\n */\nexport interface ImageReference {\n  /** The publisher of the Azure Virtual Machines Marketplace Image. For example, Canonical or MicrosoftWindowsServer. */\n  publisher?: string;\n  /** The offer type of the Azure Virtual Machines Marketplace Image. For example, UbuntuServer or WindowsServer. */\n  offer?: string;\n  /** The SKU of the Azure Virtual Machines Marketplace Image. For example, 18.04-LTS or 2019-Datacenter. */\n  sku?: string;\n  /** The version of the Azure Virtual Machines Marketplace Image. A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. */\n  version?: string;\n  /** The ARM resource identifier of the Azure Compute Gallery Image. Compute Nodes in the Pool will be created using this Image Id. This is of the form /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/images/{imageDefinitionName}/versions/{VersionId} or /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/images/{imageDefinitionName} for always defaulting to the latest image version. This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */\n  virtualMachineImageId?: string;\n}\n\n/** Windows operating system settings to apply to the virtual machine. */\nexport interface WindowsConfiguration {\n  /** Whether automatic updates are enabled on the virtual machine. If omitted, the default value is true. */\n  enableAutomaticUpdates?: boolean;\n}\n\n/**\n * Settings which will be used by the data disks associated to Compute Nodes in\n * the Pool. When using attached data disks, you need to mount and format the\n * disks from within a VM to use them.\n */\nexport interface DataDisk {\n  /** The logical unit number. The logicalUnitNumber is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct logicalUnitNumber. The value must be between 0 and 63, inclusive. */\n  lun: number;\n  /** The type of caching to be enabled for the data disks. The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. */\n  caching?: CachingType;\n  /** The initial disk size in gigabytes. */\n  diskSizeGB: number;\n  /** The storage Account type to be used for the data disk. If omitted, the default is \"standard_lrs\". */\n  storageAccountType?: StorageAccountType;\n}\n\n/** The configuration for container-enabled Pools. */\nexport interface ContainerConfiguration {\n  /** The container technology to be used. */\n  type: ContainerType;\n  /** The collection of container Image names. This is the full Image reference, as would be specified to \"docker pull\". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. */\n  containerImageNames?: string[];\n  /** Additional private registries from which containers can be pulled. If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. */\n  containerRegistries?: Array<ContainerRegistryReference>;\n}\n\n/** A private container registry. */\nexport interface ContainerRegistryReference {\n  /** The user name to log into the registry server. */\n  username?: string;\n  /** The password to log into the registry server. */\n  password?: string;\n  /** The registry URL. If omitted, the default is \"docker.io\". */\n  registryServer?: string;\n  /** The reference to the user assigned identity to use to access an Azure Container Registry instead of username and password. */\n  identityReference?: BatchNodeIdentityReference;\n}\n\n/**\n * The reference to a user assigned identity associated with the Batch pool which\n * a compute node will use.\n */\nexport interface BatchNodeIdentityReference {\n  /** The ARM resource id of the user assigned identity. */\n  resourceId?: string;\n}\n\n/**\n * The disk encryption configuration applied on compute nodes in the pool.\n * Disk encryption configuration is not supported on Linux pool created with\n * Azure Compute Gallery Image.\n */\nexport interface DiskEncryptionConfiguration {\n  /** The list of disk targets Batch Service will encrypt on the compute node. If omitted, no disks on the compute nodes in the pool will be encrypted. On Linux pool, only \"TemporaryDisk\" is supported; on Windows pool, \"OsDisk\" and \"TemporaryDisk\" must be specified. */\n  targets?: DiskEncryptionTarget[];\n}\n\n/**\n * For regional placement, nodes in the pool will be allocated in the same region.\n * For zonal placement, nodes in the pool will be spread across different zones\n * with best effort balancing.\n */\nexport interface BatchNodePlacementConfiguration {\n  /** Node placement Policy type on Batch Pools. Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. */\n  policy?: BatchNodePlacementPolicyType;\n}\n\n/** The configuration for virtual machine extensions. */\nexport interface VMExtension {\n  /** The name of the virtual machine extension. */\n  name: string;\n  /** The name of the extension handler publisher. */\n  publisher: string;\n  /** The type of the extension. */\n  type: string;\n  /** The version of script handler. */\n  typeHandlerVersion?: string;\n  /** Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. */\n  autoUpgradeMinorVersion?: boolean;\n  /** Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. */\n  enableAutomaticUpgrade?: boolean;\n  /** JSON formatted public settings for the extension. */\n  settings?: Record<string, string>;\n  /** The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. */\n  protectedSettings?: Record<string, string>;\n  /** The collection of extension names. Collection of extension names after which this extension needs to be provisioned. */\n  provisionAfterExtensions?: string[];\n}\n\n/** Settings for the operating system disk of the compute node (VM). */\nexport interface OSDisk {\n  /** Specifies the ephemeral Disk Settings for the operating system disk used by the compute node (VM). */\n  ephemeralOSDiskSettings?: DiffDiskSettings;\n  /** Specifies the caching requirements. Possible values are: None, ReadOnly, ReadWrite. The default values are: None for Standard storage. ReadOnly for Premium storage. */\n  caching?: CachingType;\n  /** The initial disk size in GB when creating new OS disk. */\n  diskSizeGB?: number;\n  /** The managed disk parameters. */\n  managedDisk?: ManagedDisk;\n  /** Specifies whether writeAccelerator should be enabled or disabled on the disk. */\n  writeAcceleratorEnabled?: boolean;\n}\n\n/**\n * Specifies the ephemeral Disk Settings for the operating system disk used by the\n * compute node (VM).\n */\nexport interface DiffDiskSettings {\n  /** Specifies the ephemeral disk placement for operating system disk for all VMs in the pool. This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://docs.microsoft.com/en-us/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. */\n  placement?: DiffDiskPlacement;\n}\n\n/** The managed disk parameters. */\nexport interface ManagedDisk {\n  /** The storage account type for managed disk. */\n  storageAccountType: StorageAccountType;\n}\n\n/** Specifies the security profile settings for the virtual machine or virtual machine scale set. */\nexport interface SecurityProfile {\n  /** This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. */\n  encryptionAtHost: boolean;\n  /** Specifies the SecurityType of the virtual machine. It has to be set to any specified value to enable UefiSettings. */\n  securityType: SecurityTypes;\n  /** Specifies the security settings like secure boot and vTPM used while creating the virtual machine. Specifies the security settings like secure boot and vTPM used while creating the virtual machine. */\n  uefiSettings: UefiSettings;\n}\n\n/** Specifies the security settings like secure boot and vTPM used while creating the virtual machine. */\nexport interface UefiSettings {\n  /** Specifies whether secure boot should be enabled on the virtual machine. */\n  secureBootEnabled?: boolean;\n  /** Specifies whether vTPM should be enabled on the virtual machine. */\n  vTpmEnabled?: boolean;\n}\n\n/**\n * Specifies the service artifact reference id used to set same image version\n * for all virtual machines in the scale set when using 'latest' image version.\n */\nexport interface ServiceArtifactReference {\n  /** The service artifact reference id of ServiceArtifactReference. The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} */\n  id: string;\n}\n\n/** The network configuration for a Pool. */\nexport interface NetworkConfiguration {\n  /** The ARM resource identifier of the virtual network subnet which the Compute Nodes of the Pool will join. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. For Pools created with virtualMachineConfiguration only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication. For Pools created with a virtual machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Also enable outbound connections to Azure Storage on port 443. For more details see: https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */\n  subnetId?: string;\n  /** The scope of dynamic vnet assignment. */\n  dynamicVNetAssignmentScope?: DynamicVNetAssignmentScope;\n  /** The configuration for endpoints on Compute Nodes in the Batch Pool. Pool endpoint configuration is only supported on Pools with the virtualMachineConfiguration property. */\n  endpointConfiguration?: BatchPoolEndpointConfiguration;\n  /** The Public IPAddress configuration for Compute Nodes in the Batch Pool. Public IP configuration property is only supported on Pools with the virtualMachineConfiguration property. */\n  publicIPAddressConfiguration?: PublicIpAddressConfiguration;\n  /** Whether this pool should enable accelerated networking. Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. */\n  enableAcceleratedNetworking?: boolean;\n}\n\n/** The endpoint configuration for a Pool. */\nexport interface BatchPoolEndpointConfiguration {\n  /** A list of inbound NAT Pools that can be used to address specific ports on an individual Compute Node externally. The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. */\n  inboundNATPools: Array<InboundNatPool>;\n}\n\n/**\n * A inbound NAT Pool that can be used to address specific ports on Compute Nodes\n * in a Batch Pool externally.\n */\nexport interface InboundNatPool {\n  /** The name of the endpoint. The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters.  If any invalid values are provided the request fails with HTTP status code 400. */\n  name: string;\n  /** The protocol of the endpoint. */\n  protocol: InboundEndpointProtocol;\n  /** The port number on the Compute Node. This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 22, 3389, 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. */\n  backendPort: number;\n  /** The first port number in the range of external ports that will be used to provide inbound access to the backendPort on individual Compute Nodes. Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. */\n  frontendPortRangeStart: number;\n  /** The last port number in the range of external ports that will be used to provide inbound access to the backendPort on individual Compute Nodes. Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. */\n  frontendPortRangeEnd: number;\n  /** A list of network security group rules that will be applied to the endpoint. The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. */\n  networkSecurityGroupRules?: Array<NetworkSecurityGroupRule>;\n}\n\n/** A network security group rule to apply to an inbound endpoint. */\nexport interface NetworkSecurityGroupRule {\n  /** The priority for this rule. Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. */\n  priority: number;\n  /** The action that should be taken for a specified IP address, subnet range or tag. */\n  access: NetworkSecurityGroupRuleAccess;\n  /** The source address prefix or tag to match for the rule. Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses).  If any other values are provided the request fails with HTTP status code 400. */\n  sourceAddressPrefix: string;\n  /** The source port ranges to match for the rule. Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. */\n  sourcePortRanges?: string[];\n}\n\n/** The public IP Address configuration of the networking configuration of a Pool. */\nexport interface PublicIpAddressConfiguration {\n  /** The provisioning type for Public IP Addresses for the Pool. The default value is BatchManaged. */\n  provision?: IpAddressProvisioningType;\n  /** The list of public IPs which the Batch service will use when provisioning Compute Nodes. The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. */\n  ipAddressIds?: string[];\n}\n\n/**\n * Batch will retry Tasks when a recovery operation is triggered on a Node.\n * Examples of recovery operations include (but are not limited to) when an\n * unhealthy Node is rebooted or a Compute Node disappeared due to host failure.\n * Retries due to recovery operations are independent of and are not counted\n * against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal\n * retry due to a recovery operation may occur. Because of this, all Tasks should\n * be idempotent. This means Tasks need to tolerate being interrupted and\n * restarted without causing any corruption or duplicate data. The best practice\n * for long running Tasks is to use some form of checkpointing. In some cases the\n * StartTask may be re-run even though the Compute Node was not rebooted. Special\n * care should be taken to avoid StartTasks which create breakaway process or\n * install/launch services from the StartTask working directory, as this will\n * block Batch from being able to re-run the StartTask.\n */\nexport interface BatchStartTask {\n  /** The command line of the StartTask. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the StartTask runs. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line.  There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. Files listed under this element are located in the Task's working directory. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of environment variable settings for the StartTask. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** The user identity under which the StartTask runs. If omitted, the Task runs as a non-administrative user unique to the Task. */\n  userIdentity?: UserIdentity;\n  /** The maximum number of times the Task may be retried. The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). */\n  maxTaskRetryCount?: number;\n  /** Whether the Batch service should wait for the StartTask to complete successfully (that is, to exit with exit code 0) before scheduling any Tasks on the Compute Node. If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. */\n  waitForSuccess?: boolean;\n}\n\n/** The container settings for a Task. */\nexport interface BatchTaskContainerSettings {\n  /** Additional options to the container create command. These additional options are supplied as arguments to the \"docker create\" command, in addition to those controlled by the Batch Service. */\n  containerRunOptions?: string;\n  /** The Image to use to create the container in which the Task will run. This is the full Image reference, as would be specified to \"docker pull\". If no tag is provided as part of the Image name, the tag \":latest\" is used as a default. */\n  imageName: string;\n  /** The private registry which contains the container Image. This setting can be omitted if was already provided at Pool creation. */\n  registry?: ContainerRegistryReference;\n  /** The location of the container Task working directory. The default is 'taskWorkingDirectory'. */\n  workingDirectory?: ContainerWorkingDirectory;\n}\n\n/** A single file or multiple files to be downloaded to a Compute Node. */\nexport interface ResourceFile {\n  /** The storage container name in the auto storage Account. The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. */\n  autoStorageContainerName?: string;\n  /** The URL of the blob container within Azure Blob Storage. The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. */\n  storageContainerUrl?: string;\n  /** The URL of the file to download. The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. */\n  httpUrl?: string;\n  /** The blob prefix to use when downloading blobs from an Azure Storage container. Only the blobs whose names begin with the specified prefix will be downloaded. The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. */\n  blobPrefix?: string;\n  /** The location on the Compute Node to which to download the file(s), relative to the Task's working directory. If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). */\n  filePath?: string;\n  /** The file permission mode attribute in octal format. This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. */\n  fileMode?: string;\n  /** The reference to the user assigned identity to use to access Azure Blob Storage specified by storageContainerUrl or httpUrl. */\n  identityReference?: BatchNodeIdentityReference;\n}\n\n/** An environment variable to be set on a Task process. */\nexport interface EnvironmentSetting {\n  /** The name of the environment variable. */\n  name: string;\n  /** The value of the environment variable. */\n  value?: string;\n}\n\n/** The definition of the user identity under which the Task is run. Specify either the userName or autoUser property, but not both. */\nexport interface UserIdentity {\n  /** The name of the user identity under which the Task is run. The userName and autoUser properties are mutually exclusive; you must specify one but not both. */\n  username?: string;\n  /** The auto user under which the Task is run. The userName and autoUser properties are mutually exclusive; you must specify one but not both. */\n  autoUser?: AutoUserSpecification;\n}\n\n/** Specifies the options for the auto user that runs an Azure Batch Task. */\nexport interface AutoUserSpecification {\n  /** The scope for the auto user. The default value is pool. If the pool is running Windows, a value of Task should be specified if stricter isolation between tasks is required, such as if the task mutates the registry in a way which could impact other tasks. */\n  scope?: AutoUserScope;\n  /** The elevation level of the auto user. The default value is nonAdmin. */\n  elevationLevel?: ElevationLevel;\n}\n\n/** A reference to an Package to be deployed to Compute Nodes. */\nexport interface BatchApplicationPackageReference {\n  /** The ID of the application to deploy. When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). */\n  applicationId: string;\n  /** The version of the application to deploy. If omitted, the default version is deployed. If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. */\n  version?: string;\n}\n\n/** Specifies how Tasks should be distributed across Compute Nodes. */\nexport interface BatchTaskSchedulingPolicy {\n  /** How Tasks are distributed across Compute Nodes in a Pool. If not specified, the default is spread. */\n  nodeFillType: BatchNodeFillType;\n}\n\n/**\n * Properties used to create a user used to execute Tasks on an Azure Batch\n * Compute Node.\n */\nexport interface UserAccount {\n  /** The name of the user Account. Names can contain any Unicode characters up to a maximum length of 20. */\n  name: string;\n  /** The password for the user Account. */\n  password: string;\n  /** The elevation level of the user Account. The default value is nonAdmin. */\n  elevationLevel?: ElevationLevel;\n  /** The Linux-specific user configuration for the user Account. This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. */\n  linuxUserConfiguration?: LinuxUserConfiguration;\n  /** The Windows-specific user configuration for the user Account. This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. */\n  windowsUserConfiguration?: WindowsUserConfiguration;\n}\n\n/** Properties used to create a user Account on a Linux Compute Node. */\nexport interface LinuxUserConfiguration {\n  /** The user ID of the user Account. The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. */\n  uid?: number;\n  /** The group ID for the user Account. The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. */\n  gid?: number;\n  /** The SSH private key for the user Account. The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). */\n  sshPrivateKey?: string;\n}\n\n/** Properties used to create a user Account on a Windows Compute Node. */\nexport interface WindowsUserConfiguration {\n  /** The login mode for the user. The default value for VirtualMachineConfiguration Pools is 'batch'. */\n  loginMode?: LoginMode;\n}\n\n/**\n * The Batch service does not assign any meaning to this metadata; it is solely\n * for the use of user code.\n */\nexport interface MetadataItem {\n  /** The name of the metadata item. */\n  name: string;\n  /** The value of the metadata item. */\n  value: string;\n}\n\n/** The file system to mount on each node. */\nexport interface MountConfiguration {\n  /** The Azure Storage Container to mount using blob FUSE on each node. This property is mutually exclusive with all other properties. */\n  azureBlobFileSystemConfiguration?: AzureBlobFileSystemConfiguration;\n  /** The NFS file system to mount on each node. This property is mutually exclusive with all other properties. */\n  nfsMountConfiguration?: NfsMountConfiguration;\n  /** The CIFS/SMB file system to mount on each node. This property is mutually exclusive with all other properties. */\n  cifsMountConfiguration?: CifsMountConfiguration;\n  /** The Azure File Share to mount on each node. This property is mutually exclusive with all other properties. */\n  azureFileShareConfiguration?: AzureFileShareConfiguration;\n}\n\n/** Information used to connect to an Azure Storage Container using Blobfuse. */\nexport interface AzureBlobFileSystemConfiguration {\n  /** The Azure Storage Account name. */\n  accountName: string;\n  /** The Azure Blob Storage Container name. */\n  containerName: string;\n  /** The Azure Storage Account key. This property is mutually exclusive with both sasKey and identity; exactly one must be specified. */\n  accountKey?: string;\n  /** The Azure Storage SAS token. This property is mutually exclusive with both accountKey and identity; exactly one must be specified. */\n  sasKey?: string;\n  /** Additional command line options to pass to the mount command. These are 'net use' options in Windows and 'mount' options in Linux. */\n  blobfuseOptions?: string;\n  /** The relative path on the compute node where the file system will be mounted. All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. */\n  relativeMountPath: string;\n  /** The reference to the user assigned identity to use to access containerName. This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. */\n  identityReference?: BatchNodeIdentityReference;\n}\n\n/** Information used to connect to an NFS file system. */\nexport interface NfsMountConfiguration {\n  /** The URI of the file system to mount. */\n  source: string;\n  /** The relative path on the compute node where the file system will be mounted. All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. */\n  relativeMountPath: string;\n  /** Additional command line options to pass to the mount command. These are 'net use' options in Windows and 'mount' options in Linux. */\n  mountOptions?: string;\n}\n\n/** Information used to connect to a CIFS file system. */\nexport interface CifsMountConfiguration {\n  /** The user to use for authentication against the CIFS file system. */\n  username: string;\n  /** The URI of the file system to mount. */\n  source: string;\n  /** The relative path on the compute node where the file system will be mounted. All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. */\n  relativeMountPath: string;\n  /** Additional command line options to pass to the mount command. These are 'net use' options in Windows and 'mount' options in Linux. */\n  mountOptions?: string;\n  /** The password to use for authentication against the CIFS file system. */\n  password: string;\n}\n\n/** Information used to connect to an Azure Fileshare. */\nexport interface AzureFileShareConfiguration {\n  /** The Azure Storage account name. */\n  accountName: string;\n  /** The Azure Files URL. This is of the form 'https://{account}.file.core.windows.net/'. */\n  azureFileUrl: string;\n  /** The Azure Storage account key. */\n  accountKey: string;\n  /** The relative path on the compute node where the file system will be mounted. All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. */\n  relativeMountPath: string;\n  /** Additional command line options to pass to the mount command. These are 'net use' options in Windows and 'mount' options in Linux. */\n  mountOptions?: string;\n}\n\n/** Describes an upgrade policy - automatic, manual, or rolling. */\nexport interface UpgradePolicy {\n  /** Specifies the mode of an upgrade to virtual machines in the scale set.<br /><br /> Possible values are:<br /><br /> **Manual** - You  control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action.<br /><br /> **Automatic** - All virtual machines in the scale set are automatically updated at the same time.<br /><br /> **Rolling** - Scale set performs updates in batches with an optional pause time in between. */\n  mode: UpgradeMode;\n  /** Configuration parameters used for performing automatic OS Upgrade. The configuration parameters used for performing automatic OS upgrade. */\n  automaticOSUpgradePolicy?: AutomaticOsUpgradePolicy;\n  /** The configuration parameters used while performing a rolling upgrade. This property is only supported on Pools with the virtualMachineConfiguration property. */\n  rollingUpgradePolicy?: RollingUpgradePolicy;\n}\n\n/** The configuration parameters used for performing automatic OS upgrade. */\nexport interface AutomaticOsUpgradePolicy {\n  /** Whether OS image rollback feature should be disabled. */\n  disableAutomaticRollback?: boolean;\n  /** Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available. <br /><br /> If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/en-us/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. */\n  enableAutomaticOSUpgrade?: boolean;\n  /** Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. */\n  useRollingUpgradePolicy?: boolean;\n  /** Defer OS upgrades on the TVMs if they are running tasks. */\n  osRollingUpgradeDeferral?: boolean;\n}\n\n/** The configuration parameters used while performing a rolling upgrade. */\nexport interface RollingUpgradePolicy {\n  /** Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. */\n  enableCrossZoneUpgrade?: boolean;\n  /** The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. */\n  maxBatchInstancePercent?: number;\n  /** The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. */\n  maxUnhealthyInstancePercent?: number;\n  /** The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. */\n  maxUnhealthyUpgradedInstancePercent?: number;\n  /** The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format.. */\n  pauseTimeBetweenBatches?: string;\n  /** Upgrade all unhealthy instances in a scale set before any healthy instances. */\n  prioritizeUnhealthyInstances?: boolean;\n  /** Rollback failed instances to previous model if the Rolling Upgrade policy is violated. */\n  rollbackFailedInstancesOnPolicyBreach?: boolean;\n}\n\n/** Represents a name-value pair. */\nexport interface NameValuePair {\n  /** The name in the name-value pair. */\n  name?: string;\n  /** The value in the name-value pair. */\n  value?: string;\n}\n\n/** Parameters for updating an Azure Batch Pool. */\nexport interface BatchPoolUpdateContent {\n  /** A Task to run on each Compute Node as it joins the Pool. The Task runs when the Compute Node is added to the Pool or when the Compute Node is restarted. If this element is present, it overwrites any existing StartTask. If omitted, any existing StartTask is left unchanged. */\n  startTask?: BatchStartTask;\n  /** A list of Packages to be installed on each Compute Node in the Pool. Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. If this element is present, it replaces any existing Package references. If you specify an empty collection, then all Package references are removed from the Pool. If omitted, any existing Package references are left unchanged. */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** A list of name-value pairs associated with the Pool as metadata. If this element is present, it replaces any existing metadata configured on the Pool. If you specify an empty collection, any metadata is removed from the Pool. If omitted, any existing metadata is left unchanged. */\n  metadata?: Array<MetadataItem>;\n  /** The desired node communication mode for the pool. If this element is present, it replaces the existing targetNodeCommunicationMode configured on the Pool. If omitted, any existing metadata is left unchanged. */\n  targetNodeCommunicationMode?: BatchNodeCommunicationMode;\n}\n\n/** Parameters for enabling automatic scaling on an Azure Batch Pool. */\nexport interface BatchPoolEnableAutoScaleContent {\n  /** The formula for the desired number of Compute Nodes in the Pool. The formula is checked for validity before it is applied to the Pool. If the formula is not valid, the Batch service rejects the request with detailed error information. For more information about specifying this formula, see Automatically scale Compute Nodes in an Azure Batch Pool (https://azure.microsoft.com/en-us/documentation/articles/batch-automatic-scaling). */\n  autoScaleFormula?: string;\n  /** The time interval at which to automatically adjust the Pool size according to the autoscale formula. The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). If you specify a new interval, then the existing autoscale evaluation schedule will be stopped and a new autoscale evaluation schedule will be started, with its starting time being the time when this request was issued. */\n  autoScaleEvaluationInterval?: string;\n}\n\n/** Parameters for evaluating an automatic scaling formula on an Azure Batch Pool. */\nexport interface BatchPoolEvaluateAutoScaleContent {\n  /** The formula for the desired number of Compute Nodes in the Pool. The formula is validated and its results calculated, but it is not applied to the Pool. To apply the formula to the Pool, 'Enable automatic scaling on a Pool'. For more information about specifying this formula, see Automatically scale Compute Nodes in an Azure Batch Pool (https://azure.microsoft.com/en-us/documentation/articles/batch-automatic-scaling). */\n  autoScaleFormula: string;\n}\n\n/** Parameters for changing the size of an Azure Batch Pool. */\nexport interface BatchPoolResizeContent {\n  /** The desired number of dedicated Compute Nodes in the Pool. */\n  targetDedicatedNodes?: number;\n  /** The desired number of Spot/Low-priority Compute Nodes in the Pool. */\n  targetLowPriorityNodes?: number;\n  /** The timeout for allocation of Nodes to the Pool or removal of Compute Nodes from the Pool. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  resizeTimeout?: string;\n  /** Determines what to do with a Compute Node and its running task(s) if the Pool size is decreasing. The default value is requeue. */\n  nodeDeallocationOption?: BatchNodeDeallocationOption;\n}\n\n/** Parameters for replacing properties on an Azure Batch Pool. */\nexport interface BatchPoolReplaceContent {\n  /** A Task to run on each Compute Node as it joins the Pool. The Task runs when the Compute Node is added to the Pool or when the Compute Node is restarted. If this element is present, it overwrites any existing StartTask. If omitted, any existing StartTask is removed from the Pool. */\n  startTask?: BatchStartTask;\n  /** The list of Application Packages to be installed on each Compute Node in the Pool. The list replaces any existing Application Package references on the Pool. Changes to Application Package references affect all new Compute Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Application Package references on any given Pool. If omitted, or if you specify an empty collection, any existing Application Packages references are removed from the Pool. A maximum of 10 references may be specified on a given Pool. */\n  applicationPackageReferences: Array<BatchApplicationPackageReference>;\n  /** A list of name-value pairs associated with the Pool as metadata. This list replaces any existing metadata configured on the Pool. If omitted, or if you specify an empty collection, any existing metadata is removed from the Pool. */\n  metadata: Array<MetadataItem>;\n  /** The desired node communication mode for the pool. This setting replaces any existing targetNodeCommunication setting on the Pool. If omitted, the existing setting is default. */\n  targetNodeCommunicationMode?: BatchNodeCommunicationMode;\n}\n\n/** Parameters for removing nodes from an Azure Batch Pool. */\nexport interface BatchNodeRemoveContent {\n  /** A list containing the IDs of the Compute Nodes to be removed from the specified Pool. A maximum of 100 nodes may be removed per request. */\n  nodeList: string[];\n  /** The timeout for removal of Compute Nodes to the Pool. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  resizeTimeout?: string;\n  /** Determines what to do with a Compute Node and its running task(s) after it has been selected for deallocation. The default value is requeue. */\n  nodeDeallocationOption?: BatchNodeDeallocationOption;\n}\n\n/** An Azure Batch Job. */\nexport interface BatchJob {\n  /** The priority of the Job. Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. */\n  priority?: number;\n  /** Whether Tasks in this job can be preempted by other high priority jobs. If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. */\n  allowTaskPreemption?: boolean;\n  /** The maximum number of tasks that can be executed in parallel for the job. The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. */\n  maxParallelTasks?: number;\n  /** The execution constraints for the Job. */\n  constraints?: BatchJobConstraints;\n  /** The Pool settings associated with the Job. */\n  poolInfo: BatchPoolInfo;\n  /** The action the Batch service should take when all Tasks in the Job are in the completed state. The default is noaction. */\n  onAllTasksComplete?: OnAllBatchTasksComplete;\n  /** A list of name-value pairs associated with the Job as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/** The execution constraints for a Job. */\nexport interface BatchJobConstraints {\n  /** The maximum elapsed time that the Job may run, measured from the time the Job is created. If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. */\n  maxWallClockTime?: string;\n  /** The maximum number of times each Task may be retried. The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). */\n  maxTaskRetryCount?: number;\n}\n\n/**\n * Specifies details of a Job Manager Task.\n * The Job Manager Task is automatically started when the Job is created. The\n * Batch service tries to schedule the Job Manager Task before any other Tasks in\n * the Job. When shrinking a Pool, the Batch service tries to preserve Nodes where\n * Job Manager Tasks are running for as long as possible (that is, Compute Nodes\n * running 'normal' Tasks are removed before Compute Nodes running Job Manager\n * Tasks). When a Job Manager Task fails and needs to be restarted, the system\n * tries to schedule it at the highest priority. If there are no idle Compute\n * Nodes available, the system may terminate one of the running Tasks in the Pool\n * and return it to the queue in order to make room for the Job Manager Task to\n * restart. Note that a Job Manager Task in one Job does not have priority over\n * Tasks in other Jobs. Across Jobs, only Job level priorities are observed. For\n * example, if a Job Manager in a priority 0 Job needs to be restarted, it will\n * not displace Tasks of a priority 1 Job. Batch will retry Tasks when a recovery\n * operation is triggered on a Node. Examples of recovery operations include (but\n * are not limited to) when an unhealthy Node is rebooted or a Compute Node\n * disappeared due to host failure. Retries due to recovery operations are\n * independent of and are not counted against the maxTaskRetryCount. Even if the\n * maxTaskRetryCount is 0, an internal retry due to a recovery operation may\n * occur. Because of this, all Tasks should be idempotent. This means Tasks need\n * to tolerate being interrupted and restarted without causing any corruption or\n * duplicate data. The best practice for long running Tasks is to use some form of\n * checkpointing.\n */\nexport interface BatchJobManagerTask {\n  /** A string that uniquely identifies the Job Manager Task within the Job. The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. */\n  id: string;\n  /** The display name of the Job Manager Task. It need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** The command line of the Job Manager Task. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the Job Manager Task runs. If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line. Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of files that the Batch service will upload from the Compute Node after running the command line. For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. */\n  outputFiles?: Array<OutputFile>;\n  /** A list of environment variable settings for the Job Manager Task. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** Constraints that apply to the Job Manager Task. */\n  constraints?: BatchTaskConstraints;\n  /** The number of scheduling slots that the Task requires to run. The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. */\n  requiredSlots?: number;\n  /** Whether completion of the Job Manager Task signifies completion of the entire Job. If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. */\n  killJobOnCompletion?: boolean;\n  /** The user identity under which the Job Manager Task runs. If omitted, the Task runs as a non-administrative user unique to the Task. */\n  userIdentity?: UserIdentity;\n  /** Whether the Job Manager Task requires exclusive use of the Compute Node where it runs. If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. */\n  runExclusive?: boolean;\n  /**\n   * A list of Application Packages that the Batch service will deploy to the\n   * Compute Node before running the command line.Application Packages are\n   * downloaded and deployed to a shared directory, not the Task working\n   * directory. Therefore, if a referenced Application Package is already\n   * on the Compute Node, and is up to date, then it is not re-downloaded;\n   * the existing copy on the Compute Node is used. If a referenced Application\n   * Package cannot be installed, for example because the package has been deleted\n   * or because download failed, the Task fails.\n   */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** The settings for an authentication token that the Task can use to perform Batch service operations. If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job. */\n  authenticationTokenSettings?: AuthenticationTokenSettings;\n  /** Whether the Job Manager Task may run on a Spot/Low-priority Compute Node. The default value is true. */\n  allowLowPriorityNode?: boolean;\n}\n\n/** On every file uploads, Batch service writes two log files to the compute node, 'fileuploadout.txt' and 'fileuploaderr.txt'. These log files are used to learn more about a specific failure. */\nexport interface OutputFile {\n  /** A pattern indicating which file(s) to upload. Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with \".\" it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \\ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. */\n  filePattern: string;\n  /** The destination for the output file(s). */\n  destination: OutputFileDestination;\n  /** Additional options for the upload operation, including under what conditions to perform the upload. */\n  uploadOptions: OutputFileUploadConfig;\n}\n\n/** The destination to which a file should be uploaded. */\nexport interface OutputFileDestination {\n  /** A location in Azure blob storage to which files are uploaded. */\n  container?: OutputFileBlobContainerDestination;\n}\n\n/** Specifies a file upload destination within an Azure blob storage container. */\nexport interface OutputFileBlobContainerDestination {\n  /** The destination blob or virtual directory within the Azure Storage container. If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. */\n  path?: string;\n  /** The URL of the container within Azure Blob Storage to which to upload the file(s). If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. */\n  containerUrl: string;\n  /** The reference to the user assigned identity to use to access Azure Blob Storage specified by containerUrl. The identity must have write access to the Azure Blob Storage container. */\n  identityReference?: BatchNodeIdentityReference;\n  /** A list of name-value pairs for headers to be used in uploading output files. These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://docs.microsoft.com/en-us/rest/api/storageservices/put-blob#request-headers-all-blob-types. */\n  uploadHeaders?: Array<HttpHeader>;\n}\n\n/** An HTTP header name-value pair */\nexport interface HttpHeader {\n  /** The case-insensitive name of the header to be used while uploading output files. */\n  name: string;\n  /** The value of the header to be used while uploading output files. */\n  value?: string;\n}\n\n/**\n * Options for an output file upload operation, including under what conditions\n * to perform the upload.\n */\nexport interface OutputFileUploadConfig {\n  /** The conditions under which the Task output file or set of files should be uploaded. The default is taskcompletion. */\n  uploadCondition: OutputFileUploadCondition;\n}\n\n/** Execution constraints to apply to a Task. */\nexport interface BatchTaskConstraints {\n  /** The maximum elapsed time that the Task may run, measured from the time the Task starts. If the Task does not complete within the time limit, the Batch service terminates it. If this is not specified, there is no time limit on how long the Task may run. */\n  maxWallClockTime?: string;\n  /** The minimum time to retain the Task directory on the Compute Node where it ran, from the time it completes execution. After this time, the Batch service may delete the Task directory and all its contents. The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. */\n  retentionTime?: string;\n  /** The maximum number of times the Task may be retried. The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). */\n  maxTaskRetryCount?: number;\n}\n\n/**\n * The settings for an authentication token that the Task can use to perform Batch\n * service operations.\n */\nexport interface AuthenticationTokenSettings {\n  /** The Batch resources to which the token grants access. The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. */\n  access?: AccessScope[];\n}\n\n/**\n * A Job Preparation Task to run before any Tasks of the Job on any given Compute Node.\n * You can use Job Preparation to prepare a Node to run Tasks for the Job.\n * Activities commonly performed in Job Preparation include: Downloading common\n * resource files used by all the Tasks in the Job. The Job Preparation Task can\n * download these common resource files to the shared location on the Node.\n * (AZ_BATCH_NODE_ROOT_DIR\\shared), or starting a local service on the Node so\n * that all Tasks of that Job can communicate with it. If the Job Preparation Task\n * fails (that is, exhausts its retry count before exiting with exit code 0),\n * Batch will not run Tasks of this Job on the Node. The Compute Node remains\n * ineligible to run Tasks of this Job until it is reimaged. The Compute Node\n * remains active and can be used for other Jobs. The Job Preparation Task can run\n * multiple times on the same Node. Therefore, you should write the Job\n * Preparation Task to handle re-execution. If the Node is rebooted, the Job\n * Preparation Task is run again on the Compute Node before scheduling any other\n * Task of the Job, if rerunOnNodeRebootAfterSuccess is true or if the Job\n * Preparation Task did not previously complete. If the Node is reimaged, the Job\n * Preparation Task is run again before scheduling any Task of the Job. Batch will\n * retry Tasks when a recovery operation is triggered on a Node. Examples of\n * recovery operations include (but are not limited to) when an unhealthy Node is\n * rebooted or a Compute Node disappeared due to host failure. Retries due to\n * recovery operations are independent of and are not counted against the\n * maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to\n * a recovery operation may occur. Because of this, all Tasks should be\n * idempotent. This means Tasks need to tolerate being interrupted and restarted\n * without causing any corruption or duplicate data. The best practice for long\n * running Tasks is to use some form of checkpointing.\n */\nexport interface BatchJobPreparationTask {\n  /** A string that uniquely identifies the Job Preparation Task within the Job. The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). */\n  id?: string;\n  /** The command line of the Job Preparation Task. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the Job Preparation Task runs. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line. Files listed under this element are located in the Task's working directory.  There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of environment variable settings for the Job Preparation Task. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** Constraints that apply to the Job Preparation Task. */\n  constraints?: BatchTaskConstraints;\n  /** Whether the Batch service should wait for the Job Preparation Task to complete successfully before scheduling any other Tasks of the Job on the Compute Node. A Job Preparation Task has completed successfully if it exits with exit code 0. If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. */\n  waitForSuccess?: boolean;\n  /** The user identity under which the Job Preparation Task runs. If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. */\n  userIdentity?: UserIdentity;\n  /** Whether the Batch service should rerun the Job Preparation Task after a Compute Node reboots. The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. */\n  rerunOnNodeRebootAfterSuccess?: boolean;\n}\n\n/**\n * A Job Release Task to run on Job completion on any Compute Node where the Job has run.\n * The Job Release Task runs when the Job ends, because of one of the following:\n * The user calls the Terminate Job API, or the Delete Job API while the Job is\n * still active, the Job's maximum wall clock time constraint is reached, and the\n * Job is still active, or the Job's Job Manager Task completed, and the Job is\n * configured to terminate when the Job Manager completes. The Job Release Task\n * runs on each Node where Tasks of the Job have run and the Job Preparation Task\n * ran and completed. If you reimage a Node after it has run the Job Preparation\n * Task, and the Job ends without any further Tasks of the Job running on that\n * Node (and hence the Job Preparation Task does not re-run), then the Job Release\n * Task does not run on that Compute Node. If a Node reboots while the Job Release\n * Task is still running, the Job Release Task runs again when the Compute Node\n * starts up. The Job is not marked as complete until all Job Release Tasks have\n * completed. The Job Release Task runs in the background. It does not occupy a\n * scheduling slot; that is, it does not count towards the taskSlotsPerNode limit\n * specified on the Pool.\n */\nexport interface BatchJobReleaseTask {\n  /** A string that uniquely identifies the Job Release Task within the Job. The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). */\n  id?: string;\n  /** The command line of the Job Release Task. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the Job Release Task runs. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line.  There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. Files listed under this element are located in the Task's working directory. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of environment variable settings for the Job Release Task. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** The maximum elapsed time that the Job Release Task may run on a given Compute Node, measured from the time the Task starts. If the Task does not complete within the time limit, the Batch service terminates it. The default value is 15 minutes. You may not specify a timeout longer than 15 minutes. If you do, the Batch service rejects it with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  maxWallClockTime?: string;\n  /** The minimum time to retain the Task directory for the Job Release Task on the Compute Node. After this time, the Batch service may delete the Task directory and all its contents. The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. */\n  retentionTime?: string;\n  /** The user identity under which the Job Release Task runs. If omitted, the Task runs as a non-administrative user unique to the Task. */\n  userIdentity?: UserIdentity;\n}\n\n/** Specifies how a Job should be assigned to a Pool. */\nexport interface BatchPoolInfo {\n  /** The ID of an existing Pool. All the Tasks of the Job will run on the specified Pool. You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. */\n  poolId?: string;\n  /** Characteristics for a temporary 'auto pool'. The Batch service will create this auto Pool when the Job is submitted. If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. */\n  autoPoolSpecification?: BatchAutoPoolSpecification;\n}\n\n/**\n * Specifies characteristics for a temporary 'auto pool'. The Batch service will\n * create this auto Pool when the Job is submitted.\n */\nexport interface BatchAutoPoolSpecification {\n  /** A prefix to be added to the unique identifier when a Pool is automatically created. The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. */\n  autoPoolIdPrefix?: string;\n  /** The minimum lifetime of created auto Pools, and how multiple Jobs on a schedule are assigned to Pools. */\n  poolLifetimeOption: BatchPoolLifetimeOption;\n  /** Whether to keep an auto Pool alive after its lifetime expires. If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. */\n  keepAlive?: boolean;\n  /** The Pool specification for the auto Pool. */\n  pool?: BatchPoolSpecification;\n}\n\n/** Specification for creating a new Pool. */\nexport interface BatchPoolSpecification {\n  /** The display name for the Pool. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** The size of the virtual machines in the Pool. All virtual machines in a Pool are the same size. For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://docs.microsoft.com/azure/batch/batch-pool-vm-sizes). */\n  vmSize: string;\n  /** The virtual machine configuration for the Pool. This property must be specified if the Pool needs to be created with Azure IaaS VMs. If it is not specified then the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  virtualMachineConfiguration?: VirtualMachineConfiguration;\n  /** The number of task slots that can be used to run concurrent tasks on a single compute node in the pool. The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. */\n  taskSlotsPerNode?: number;\n  /** How Tasks are distributed across Compute Nodes in a Pool. If not specified, the default is spread. */\n  taskSchedulingPolicy?: BatchTaskSchedulingPolicy;\n  /** The timeout for allocation of Compute Nodes to the Pool. This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  resizeTimeout?: string;\n  /** The user-specified tags associated with the pool.The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. */\n  resourceTags?: string;\n  /** The desired number of dedicated Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. */\n  targetDedicatedNodes?: number;\n  /** The desired number of Spot/Low-priority Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. */\n  targetLowPriorityNodes?: number;\n  /** Whether the Pool size should automatically adjust over time. If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. */\n  enableAutoScale?: boolean;\n  /** The formula for the desired number of Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. */\n  autoScaleFormula?: string;\n  /** The time interval at which to automatically adjust the Pool size according to the autoscale formula. The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  autoScaleEvaluationInterval?: string;\n  /** Whether the Pool permits direct communication between Compute Nodes. Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. */\n  enableInterNodeCommunication?: boolean;\n  /** The network configuration for the Pool. */\n  networkConfiguration?: NetworkConfiguration;\n  /** A Task to run on each Compute Node as it joins the Pool. The Task runs when the Compute Node is added to the Pool or when the Compute Node is restarted. */\n  startTask?: BatchStartTask;\n  /** The list of Packages to be installed on each Compute Node in the Pool. When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** The list of user Accounts to be created on each Compute Node in the Pool. */\n  userAccounts?: Array<UserAccount>;\n  /** A list of name-value pairs associated with the Pool as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n  /** A list of file systems to mount on each node in the pool. This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. */\n  mountConfiguration?: Array<MountConfiguration>;\n  /** The desired node communication mode for the pool. If omitted, the default value is Default. */\n  targetNodeCommunicationMode?: BatchNodeCommunicationMode;\n  /** The upgrade policy for the Pool. Describes an upgrade policy - automatic, manual, or rolling. */\n  upgradePolicy?: UpgradePolicy;\n}\n\n/** The network configuration for the Job. */\nexport interface BatchJobNetworkConfiguration {\n  /** The ARM resource identifier of the virtual network subnet which Compute Nodes running Tasks from the Job will join for the duration of the Task. This will only work with a VirtualMachineConfiguration Pool. The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */\n  subnetId: string;\n}\n\n/** Contains information about the execution of a Job in the Azure Batch service. */\nexport interface BatchJobExecutionInfo {\n  /** The start time of the Job. This is the time at which the Job was created. */\n  startTime: Date | string;\n  /** The completion time of the Job. This property is set only if the Job is in the completed state. */\n  endTime?: Date | string;\n  /** The ID of the Pool to which this Job is assigned. This element contains the actual Pool where the Job is assigned. When you get Job details from the service, they also contain a poolInfo element, which contains the Pool configuration data from when the Job was added or updated. That poolInfo element may also contain a poolId element. If it does, the two IDs are the same. If it does not, it means the Job ran on an auto Pool, and this property contains the ID of that auto Pool. */\n  poolId?: string;\n  /** Details of any error encountered by the service in starting the Job. This property is not set if there was no error starting the Job. */\n  schedulingError?: BatchJobSchedulingError;\n  /** A string describing the reason the Job ended. This property is set only if the Job is in the completed state. If the Batch service terminates the Job, it sets the reason as follows: JMComplete - the Job Manager Task completed, and killJobOnCompletion was set to true. MaxWallClockTimeExpiry - the Job reached its maxWallClockTime constraint. TerminateJobSchedule - the Job ran as part of a schedule, and the schedule terminated. AllTasksComplete - the Job's onAllTasksComplete attribute is set to terminatejob, and all Tasks in the Job are complete. TaskFailed - the Job's onTaskFailure attribute is set to performExitOptionsJobAction, and a Task in the Job failed with an exit condition that specified a jobAction of terminatejob. Any other string is a user-defined reason specified in a call to the 'Terminate a Job' operation. */\n  terminateReason?: string;\n}\n\n/** An error encountered by the Batch service when scheduling a Job. */\nexport interface BatchJobSchedulingError {\n  /** The category of the Job scheduling error. */\n  category: ErrorCategory;\n  /** An identifier for the Job scheduling error. Codes are invariant and are intended to be consumed programmatically. */\n  code?: string;\n  /** A message describing the Job scheduling error, intended to be suitable for display in a user interface. */\n  message?: string;\n  /** A list of additional error details related to the scheduling error. */\n  details?: Array<NameValuePair>;\n}\n\n/** Resource usage statistics for a Job. */\nexport interface BatchJobStatistics {\n  /** The URL of the statistics. */\n  url: string;\n  /** The start time of the time range covered by the statistics. */\n  startTime: Date | string;\n  /** The time at which the statistics were last updated. All statistics are limited to the range between startTime and lastUpdateTime. */\n  lastUpdateTime: Date | string;\n  /** The total user mode CPU time (summed across all cores and all Compute Nodes) consumed by all Tasks in the Job. */\n  userCPUTime: string;\n  /** The total kernel mode CPU time (summed across all cores and all Compute Nodes) consumed by all Tasks in the Job. */\n  kernelCPUTime: string;\n  /** The total wall clock time of all Tasks in the Job.  The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If a Task was retried, this includes the wall clock time of all the Task retries. */\n  wallClockTime: string;\n  /** The total number of disk read operations made by all Tasks in the Job. */\n  readIOps: number;\n  /** The total number of disk write operations made by all Tasks in the Job. */\n  writeIOps: number;\n  /** The total amount of data in GiB read from disk by all Tasks in the Job. */\n  readIOGiB: number;\n  /** The total amount of data in GiB written to disk by all Tasks in the Job. */\n  writeIOGiB: number;\n  /** The total number of Tasks successfully completed in the Job during the given time range. A Task completes successfully if it returns exit code 0. */\n  numSucceededTasks: number;\n  /** The total number of Tasks in the Job that failed during the given time range. A Task fails if it exhausts its maximum retry count without returning exit code 0. */\n  numFailedTasks: number;\n  /** The total number of retries on all the Tasks in the Job during the given time range. */\n  numTaskRetries: number;\n  /** The total wait time of all Tasks in the Job. The wait time for a Task is defined as the elapsed time between the creation of the Task and the start of Task execution. (If the Task is retried due to failures, the wait time is the time to the most recent Task execution.) This value is only reported in the Account lifetime statistics; it is not included in the Job statistics. */\n  waitTime: string;\n}\n\n/** Parameters for updating an Azure Batch Job. */\nexport interface BatchJobUpdateContent {\n  /** The priority of the Job. Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. If omitted, the priority of the Job is left unchanged. */\n  priority?: number;\n  /** Whether Tasks in this job can be preempted by other high priority jobs. If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. */\n  allowTaskPreemption?: boolean;\n  /** The maximum number of tasks that can be executed in parallel for the job. The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. */\n  maxParallelTasks?: number;\n  /** The execution constraints for the Job. If omitted, the existing execution constraints are left unchanged. */\n  constraints?: BatchJobConstraints;\n  /** The Pool on which the Batch service runs the Job's Tasks. You may change the Pool for a Job only when the Job is disabled. The Patch Job call will fail if you include the poolInfo element and the Job is not disabled. If you specify an autoPoolSpecification in the poolInfo, only the keepAlive property of the autoPoolSpecification can be updated, and then only if the autoPoolSpecification has a poolLifetimeOption of Job (other job properties can be updated as normal). If omitted, the Job continues to run on its current Pool. */\n  poolInfo?: BatchPoolInfo;\n  /** The action the Batch service should take when all Tasks in the Job are in the completed state. If omitted, the completion behavior is left unchanged. You may not change the value from terminatejob to noaction - that is, once you have engaged automatic Job termination, you cannot turn it off again. If you try to do this, the request fails with an 'invalid property value' error response; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  onAllTasksComplete?: OnAllBatchTasksComplete;\n  /** A list of name-value pairs associated with the Job as metadata. If omitted, the existing Job metadata is left unchanged. */\n  metadata?: Array<MetadataItem>;\n}\n\n/** Parameters for disabling an Azure Batch Job. */\nexport interface BatchJobDisableContent {\n  /** What to do with active Tasks associated with the Job. */\n  disableTasks: DisableBatchJobOption;\n}\n\n/** Parameters for terminating an Azure Batch Job. */\nexport interface BatchJobTerminateContent {\n  /** The text you want to appear as the Job's TerminationReason. The default is 'UserTerminate'. */\n  terminateReason?: string;\n}\n\n/** Parameters for creating an Azure Batch Job. */\nexport interface BatchJobCreateContent {\n  /** A string that uniquely identifies the Job within the Account. The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within an Account that differ only by case). */\n  id: string;\n  /** The display name for the Job. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** Whether Tasks in the Job can define dependencies on each other. The default is false. */\n  usesTaskDependencies?: boolean;\n  /** The priority of the Job. Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. */\n  priority?: number;\n  /** Whether Tasks in this job can be preempted by other high priority jobs. If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. */\n  allowTaskPreemption?: boolean;\n  /** The maximum number of tasks that can be executed in parallel for the job. The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. */\n  maxParallelTasks?: number;\n  /** The execution constraints for the Job. */\n  constraints?: BatchJobConstraints;\n  /** Details of a Job Manager Task to be launched when the Job is started. If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. The Job Manager Task's typical purpose is to control and/or monitor Job execution, for example by deciding what additional Tasks to run, determining when the work is complete, etc. (However, a Job Manager Task is not restricted to these activities - it is a fully-fledged Task in the system and perform whatever actions are required for the Job.) For example, a Job Manager Task might download a file specified as a parameter, analyze the contents of that file and submit additional Tasks based on those contents. */\n  jobManagerTask?: BatchJobManagerTask;\n  /** The Job Preparation Task. If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. */\n  jobPreparationTask?: BatchJobPreparationTask;\n  /** The Job Release Task. A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Nodes that have run the Job Preparation Task. The primary purpose of the Job Release Task is to undo changes to Compute Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. */\n  jobReleaseTask?: BatchJobReleaseTask;\n  /** The list of common environment variable settings. These environment variables are set for all Tasks in the Job (including the Job Manager, Job Preparation and Job Release Tasks). Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. */\n  commonEnvironmentSettings?: Array<EnvironmentSetting>;\n  /** The Pool on which the Batch service runs the Job's Tasks. */\n  poolInfo: BatchPoolInfo;\n  /** The action the Batch service should take when all Tasks in the Job are in the completed state. Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction. */\n  onAllTasksComplete?: OnAllBatchTasksComplete;\n  /** The action the Batch service should take when any Task in the Job fails. A Task is considered to have failed if has a failureInfo. A failureInfo is set if the Task completes with a non-zero exit code after exhausting its retry count, or if there was an error starting the Task, for example due to a resource file download error. The default is noaction. */\n  onTaskFailure?: OnBatchTaskFailure;\n  /** The network configuration for the Job. */\n  networkConfiguration?: BatchJobNetworkConfiguration;\n  /** A list of name-value pairs associated with the Job as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/** Contains information about the container which a Task is executing. */\nexport interface BatchTaskContainerExecutionInfo {\n  /** The ID of the container. */\n  containerId?: string;\n  /** The state of the container. This is the state of the container according to the Docker service. It is equivalent to the status field returned by \"docker inspect\". */\n  state?: string;\n  /** Detailed error information about the container. This is the detailed error string from the Docker service, if available. It is equivalent to the error field returned by \"docker inspect\". */\n  error?: string;\n}\n\n/** Information about a Task failure. */\nexport interface BatchTaskFailureInfo {\n  /** The category of the Task error. */\n  category: ErrorCategory;\n  /** An identifier for the Task error. Codes are invariant and are intended to be consumed programmatically. */\n  code?: string;\n  /** A message describing the Task error, intended to be suitable for display in a user interface. */\n  message?: string;\n  /** A list of additional details related to the error. */\n  details?: Array<NameValuePair>;\n}\n\n/**\n * A Job Schedule that allows recurring Jobs by specifying when to run Jobs and a\n * specification used to create each Job.\n */\nexport interface BatchJobSchedule {\n  /** The schedule according to which Jobs will be created. All times are fixed respective to UTC and are not impacted by daylight saving time. */\n  schedule?: BatchJobScheduleConfiguration;\n  /** The details of the Jobs to be created on this schedule. */\n  jobSpecification: BatchJobSpecification;\n  /** A list of name-value pairs associated with the schedule as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/**\n * The schedule according to which Jobs will be created. All times are fixed\n * respective to UTC and are not impacted by daylight saving time.\n */\nexport interface BatchJobScheduleConfiguration {\n  /** The earliest time at which any Job may be created under this Job Schedule. If you do not specify a doNotRunUntil time, the schedule becomes ready to create Jobs immediately. */\n  doNotRunUntil?: Date | string;\n  /** A time after which no Job will be created under this Job Schedule. The schedule will move to the completed state as soon as this deadline is past and there is no active Job under this Job Schedule. If you do not specify a doNotRunAfter time, and you are creating a recurring Job Schedule, the Job Schedule will remain active until you explicitly terminate it. */\n  doNotRunAfter?: Date | string;\n  /** The time interval, starting from the time at which the schedule indicates a Job should be created, within which a Job must be created. If a Job is not created within the startWindow interval, then the 'opportunity' is lost; no Job will be created until the next recurrence of the schedule. If the schedule is recurring, and the startWindow is longer than the recurrence interval, then this is equivalent to an infinite startWindow, because the Job that is 'due' in one recurrenceInterval is not carried forward into the next recurrence interval. The default is infinite. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  startWindow?: string;\n  /** The time interval between the start times of two successive Jobs under the Job Schedule. A Job Schedule can have at most one active Job under it at any given time. Because a Job Schedule can have at most one active Job under it at any given time, if it is time to create a new Job under a Job Schedule, but the previous Job is still running, the Batch service will not create the new Job until the previous Job finishes. If the previous Job does not finish within the startWindow period of the new recurrenceInterval, then no new Job will be scheduled for that interval. For recurring Jobs, you should normally specify a jobManagerTask in the jobSpecification. If you do not use jobManagerTask, you will need an external process to monitor when Jobs are created, add Tasks to the Jobs and terminate the Jobs ready for the next recurrence. The default is that the schedule does not recur: one Job is created, within the startWindow after the doNotRunUntil time, and the schedule is complete as soon as that Job finishes. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  recurrenceInterval?: string;\n}\n\n/** Specifies details of the Jobs to be created on a schedule. */\nexport interface BatchJobSpecification {\n  /** The priority of Jobs created under this schedule. Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. This priority is used as the default for all Jobs under the Job Schedule. You can update a Job's priority after it has been created using by using the update Job API. */\n  priority?: number;\n  /** Whether Tasks in this job can be preempted by other high priority jobs. If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. */\n  allowTaskPreemption?: boolean;\n  /** The maximum number of tasks that can be executed in parallel for the job. The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. */\n  maxParallelTasks?: number;\n  /** The display name for Jobs created under this schedule. The name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** Whether Tasks in the Job can define dependencies on each other. The default is false. */\n  usesTaskDependencies?: boolean;\n  /** The action the Batch service should take when all Tasks in a Job created under this schedule are in the completed state. Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction. */\n  onAllTasksComplete?: OnAllBatchTasksComplete;\n  /** The action the Batch service should take when any Task fails in a Job created under this schedule. A Task is considered to have failed if it have failed if has a failureInfo. A failureInfo is set if the Task completes with a non-zero exit code after exhausting its retry count, or if there was an error starting the Task, for example due to a resource file download error. The default is noaction. */\n  onTaskFailure?: OnBatchTaskFailure;\n  /** The network configuration for the Job. */\n  networkConfiguration?: BatchJobNetworkConfiguration;\n  /** The execution constraints for Jobs created under this schedule. */\n  constraints?: BatchJobConstraints;\n  /** The details of a Job Manager Task to be launched when a Job is started under this schedule. If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job using the Task API. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. */\n  jobManagerTask?: BatchJobManagerTask;\n  /** The Job Preparation Task for Jobs created under this schedule. If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. */\n  jobPreparationTask?: BatchJobPreparationTask;\n  /** The Job Release Task for Jobs created under this schedule. The primary purpose of the Job Release Task is to undo changes to Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Compute Nodes that have run the Job Preparation Task. */\n  jobReleaseTask?: BatchJobReleaseTask;\n  /** A list of common environment variable settings. These environment variables are set for all Tasks in Jobs created under this schedule (including the Job Manager, Job Preparation and Job Release Tasks). Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. */\n  commonEnvironmentSettings?: Array<EnvironmentSetting>;\n  /** The Pool on which the Batch service runs the Tasks of Jobs created under this schedule. */\n  poolInfo: BatchPoolInfo;\n  /** A list of name-value pairs associated with each Job created under this schedule as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/**\n * Contains information about Jobs that have been and will be run under a Job\n * Schedule.\n */\nexport interface BatchJobScheduleExecutionInfo {\n  /** The next time at which a Job will be created under this schedule. This property is meaningful only if the schedule is in the active state when the time comes around. For example, if the schedule is disabled, no Job will be created at nextRunTime unless the Job is enabled before then. */\n  nextRunTime?: Date | string;\n  /** Information about the most recent Job under the Job Schedule. This property is present only if the at least one Job has run under the schedule. */\n  recentJob?: RecentBatchJob;\n  /** The time at which the schedule ended. This property is set only if the Job Schedule is in the completed state. */\n  endTime?: Date | string;\n}\n\n/** Information about the most recent Job to run under the Job Schedule. */\nexport interface RecentBatchJob {\n  /** The ID of the Job. */\n  id?: string;\n  /** The URL of the Job. */\n  url?: string;\n}\n\n/** Resource usage statistics for a Job Schedule. */\nexport interface BatchJobScheduleStatistics {\n  /** The URL of the statistics. */\n  url: string;\n  /** The start time of the time range covered by the statistics. */\n  startTime: Date | string;\n  /** The time at which the statistics were last updated. All statistics are limited to the range between startTime and lastUpdateTime. */\n  lastUpdateTime: Date | string;\n  /** The total user mode CPU time (summed across all cores and all Compute Nodes) consumed by all Tasks in all Jobs created under the schedule. */\n  userCPUTime: string;\n  /** The total kernel mode CPU time (summed across all cores and all Compute Nodes) consumed by all Tasks in all Jobs created under the schedule. */\n  kernelCPUTime: string;\n  /** The total wall clock time of all the Tasks in all the Jobs created under the schedule. The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If a Task was retried, this includes the wall clock time of all the Task retries. */\n  wallClockTime: string;\n  /** The total number of disk read operations made by all Tasks in all Jobs created under the schedule. */\n  readIOps: number;\n  /** The total number of disk write operations made by all Tasks in all Jobs created under the schedule. */\n  writeIOps: number;\n  /** The total gibibytes read from disk by all Tasks in all Jobs created under the schedule. */\n  readIOGiB: number;\n  /** The total gibibytes written to disk by all Tasks in all Jobs created under the schedule. */\n  writeIOGiB: number;\n  /** The total number of Tasks successfully completed during the given time range in Jobs created under the schedule. A Task completes successfully if it returns exit code 0. */\n  numSucceededTasks: number;\n  /** The total number of Tasks that failed during the given time range in Jobs created under the schedule. A Task fails if it exhausts its maximum retry count without returning exit code 0. */\n  numFailedTasks: number;\n  /** The total number of retries during the given time range on all Tasks in all Jobs created under the schedule. */\n  numTaskRetries: number;\n  /** The total wait time of all Tasks in all Jobs created under the schedule. The wait time for a Task is defined as the elapsed time between the creation of the Task and the start of Task execution. (If the Task is retried due to failures, the wait time is the time to the most recent Task execution.). This value is only reported in the Account lifetime statistics; it is not included in the Job statistics. */\n  waitTime: string;\n}\n\n/** Parameters for updating an Azure Batch Job Schedule. */\nexport interface BatchJobScheduleUpdateContent {\n  /** The schedule according to which Jobs will be created. All times are fixed respective to UTC and are not impacted by daylight saving time. If you do not specify this element, the existing schedule is left unchanged. */\n  schedule?: BatchJobScheduleConfiguration;\n  /** The details of the Jobs to be created on this schedule. Updates affect only Jobs that are started after the update has taken place. Any currently active Job continues with the older specification. */\n  jobSpecification?: BatchJobSpecification;\n  /** A list of name-value pairs associated with the Job Schedule as metadata. If you do not specify this element, existing metadata is left unchanged. */\n  metadata?: Array<MetadataItem>;\n}\n\n/** Parameters for creating an Azure Batch Job Schedule */\nexport interface BatchJobScheduleCreateContent {\n  /** A string that uniquely identifies the schedule within the Account. The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within an Account that differ only by case). */\n  id: string;\n  /** The display name for the schedule. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** The schedule according to which Jobs will be created. All times are fixed respective to UTC and are not impacted by daylight saving time. */\n  schedule: BatchJobScheduleConfiguration;\n  /** The details of the Jobs to be created on this schedule. */\n  jobSpecification: BatchJobSpecification;\n  /** A list of name-value pairs associated with the schedule as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/** Parameters for creating an Azure Batch Task. */\nexport interface BatchTaskCreateContent {\n  /** A string that uniquely identifies the Task within the Job. The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within a Job that differ only by case). */\n  id: string;\n  /** A display name for the Task. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** How the Batch service should respond when the Task completes. */\n  exitConditions?: ExitConditions;\n  /** The command line of the Task. For multi-instance Tasks, the command line is executed as the primary Task, after the primary Task and all subtasks have finished executing the coordination command line. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the Task runs. If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line. For multi-instance Tasks, the resource files will only be downloaded to the Compute Node on which the primary Task is executed. There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of files that the Batch service will upload from the Compute Node after running the command line. For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. */\n  outputFiles?: Array<OutputFile>;\n  /** A list of environment variable settings for the Task. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** A locality hint that can be used by the Batch service to select a Compute Node on which to start the new Task. */\n  affinityInfo?: AffinityInfo;\n  /** The execution constraints that apply to this Task. If you do not specify constraints, the maxTaskRetryCount is the maxTaskRetryCount specified for the Job, the maxWallClockTime is infinite, and the retentionTime is 7 days. */\n  constraints?: BatchTaskConstraints;\n  /** The number of scheduling slots that the Task required to run. The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this must be 1. */\n  requiredSlots?: number;\n  /** The user identity under which the Task runs. If omitted, the Task runs as a non-administrative user unique to the Task. */\n  userIdentity?: UserIdentity;\n  /** An object that indicates that the Task is a multi-instance Task, and contains information about how to run the multi-instance Task. */\n  multiInstanceSettings?: MultiInstanceSettings;\n  /** The Tasks that this Task depends on. This Task will not be scheduled until all Tasks that it depends on have completed successfully. If any of those Tasks fail and exhaust their retry counts, this Task will never be scheduled. If the Job does not have usesTaskDependencies set to true, and this element is present, the request fails with error code TaskDependenciesNotSpecifiedOnJob. */\n  dependsOn?: BatchTaskDependencies;\n  /** A list of Packages that the Batch service will deploy to the Compute Node before running the command line. Application packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced package is already on the Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** The settings for an authentication token that the Task can use to perform Batch service operations. If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job. */\n  authenticationTokenSettings?: AuthenticationTokenSettings;\n}\n\n/** Specifies how the Batch service should respond when the Task completes. */\nexport interface ExitConditions {\n  /** A list of individual Task exit codes and how the Batch service should respond to them. */\n  exitCodes?: Array<ExitCodeMapping>;\n  /** A list of Task exit code ranges and how the Batch service should respond to them. */\n  exitCodeRanges?: Array<ExitCodeRangeMapping>;\n  /** How the Batch service should respond if the Task fails to start due to an error. */\n  preProcessingError?: ExitOptions;\n  /** How the Batch service should respond if a file upload error occurs. If the Task exited with an exit code that was specified via exitCodes or exitCodeRanges, and then encountered a file upload error, then the action specified by the exit code takes precedence. */\n  fileUploadError?: ExitOptions;\n  /** How the Batch service should respond if the Task fails with an exit condition not covered by any of the other properties. This value is used if the Task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection. */\n  default?: ExitOptions;\n}\n\n/**\n * How the Batch service should respond if a Task exits with a particular exit\n * code.\n */\nexport interface ExitCodeMapping {\n  /** A process exit code. */\n  code: number;\n  /** How the Batch service should respond if the Task exits with this exit code. */\n  exitOptions: ExitOptions;\n}\n\n/** Specifies how the Batch service responds to a particular exit condition. */\nexport interface ExitOptions {\n  /** An action to take on the Job containing the Task, if the Task completes with the given exit condition and the Job's onTaskFailed property is 'performExitOptionsJobAction'. The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  jobAction?: BatchJobAction;\n  /** An action that the Batch service performs on Tasks that depend on this Task. Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. */\n  dependencyAction?: DependencyAction;\n}\n\n/**\n * A range of exit codes and how the Batch service should respond to exit codes\n * within that range.\n */\nexport interface ExitCodeRangeMapping {\n  /** The first exit code in the range. */\n  start: number;\n  /** The last exit code in the range. */\n  end: number;\n  /** How the Batch service should respond if the Task exits with an exit code in the range start to end (inclusive). */\n  exitOptions: ExitOptions;\n}\n\n/**\n * A locality hint that can be used by the Batch service to select a Compute Node\n * on which to start a Task.\n */\nexport interface AffinityInfo {\n  /** An opaque string representing the location of a Compute Node or a Task that has run previously. You can pass the affinityId of a Node to indicate that this Task needs to run on that Compute Node. Note that this is just a soft affinity. If the target Compute Node is busy or unavailable at the time the Task is scheduled, then the Task will be scheduled elsewhere. */\n  affinityId: string;\n}\n\n/**\n * Multi-instance Tasks are commonly used to support MPI Tasks. In the MPI case,\n * if any of the subtasks fail (for example due to exiting with a non-zero exit\n * code) the entire multi-instance Task fails. The multi-instance Task is then\n * terminated and retried, up to its retry limit.\n */\nexport interface MultiInstanceSettings {\n  /** The number of Compute Nodes required by the Task. If omitted, the default is 1. */\n  numberOfInstances?: number;\n  /** The command line to run on all the Compute Nodes to enable them to coordinate when the primary runs the main Task command. A typical coordination command line launches a background service and verifies that the service is ready to process inter-node messages. */\n  coordinationCommandLine: string;\n  /** A list of files that the Batch service will download before running the coordination command line. The difference between common resource files and Task resource files is that common resource files are downloaded for all subtasks including the primary, whereas Task resource files are downloaded only for the primary. Also note that these resource files are not downloaded to the Task working directory, but instead are downloaded to the Task root directory (one directory above the working directory).  There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. */\n  commonResourceFiles?: Array<ResourceFile>;\n}\n\n/**\n * Specifies any dependencies of a Task. Any Task that is explicitly specified or\n * within a dependency range must complete before the dependant Task will be\n * scheduled.\n */\nexport interface BatchTaskDependencies {\n  /** The list of Task IDs that this Task depends on. All Tasks in this list must complete successfully before the dependent Task can be scheduled. The taskIds collection is limited to 64000 characters total (i.e. the combined length of all Task IDs). If the taskIds collection exceeds the maximum length, the Add Task request fails with error code TaskDependencyListTooLong. In this case consider using Task ID ranges instead. */\n  taskIds?: string[];\n  /** The list of Task ID ranges that this Task depends on. All Tasks in all ranges must complete successfully before the dependent Task can be scheduled. */\n  taskIdRanges?: Array<BatchTaskIdRange>;\n}\n\n/**\n * The start and end of the range are inclusive. For example, if a range has start\n * 9 and end 12, then it represents Tasks '9', '10', '11' and '12'.\n */\nexport interface BatchTaskIdRange {\n  /** The first Task ID in the range. */\n  start: number;\n  /** The last Task ID in the range. */\n  end: number;\n}\n\n/**\n * Batch will retry Tasks when a recovery operation is triggered on a Node.\n * Examples of recovery operations include (but are not limited to) when an\n * unhealthy Node is rebooted or a Compute Node disappeared due to host failure.\n * Retries due to recovery operations are independent of and are not counted\n * against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal\n * retry due to a recovery operation may occur. Because of this, all Tasks should\n * be idempotent. This means Tasks need to tolerate being interrupted and\n * restarted without causing any corruption or duplicate data. The best practice\n * for long running Tasks is to use some form of checkpointing.\n */\nexport interface BatchTask {\n  /** The execution constraints that apply to this Task. */\n  constraints?: BatchTaskConstraints;\n}\n\n/** Information about the execution of a Task. */\nexport interface BatchTaskExecutionInfo {\n  /** The time at which the Task started running. 'Running' corresponds to the running state, so if the Task specifies resource files or Packages, then the start time reflects the time at which the Task started downloading or deploying these. If the Task has been restarted or retried, this is the most recent time at which the Task started running. This property is present only for Tasks that are in the running or completed state. */\n  startTime?: Date | string;\n  /** The time at which the Task completed. This property is set only if the Task is in the Completed state. */\n  endTime?: Date | string;\n  /** The exit code of the program specified on the Task command line. This property is set only if the Task is in the completed state. In general, the exit code for a process reflects the specific convention implemented by the application developer for that process. If you use the exit code value to make decisions in your code, be sure that you know the exit code convention used by the application process. However, if the Batch service terminates the Task (due to timeout, or user termination via the API) you may see an operating system-defined exit code. */\n  exitCode?: number;\n  /** Information about the container under which the Task is executing. This property is set only if the Task runs in a container context. */\n  containerInfo?: BatchTaskContainerExecutionInfo;\n  /** Information describing the Task failure, if any. This property is set only if the Task is in the completed state and encountered a failure. */\n  failureInfo?: BatchTaskFailureInfo;\n  /** The number of times the Task has been retried by the Batch service. Task application failures (non-zero exit code) are retried, pre-processing errors (the Task could not be run) and file upload errors are not retried. The Batch service will retry the Task up to the limit specified by the constraints. */\n  retryCount: number;\n  /** The most recent time at which a retry of the Task started running. This element is present only if the Task was retried (i.e. retryCount is nonzero). If present, this is typically the same as startTime, but may be different if the Task has been restarted for reasons other than retry; for example, if the Compute Node was rebooted during a retry, then the startTime is updated but the lastRetryTime is not. */\n  lastRetryTime?: Date | string;\n  /** The number of times the Task has been requeued by the Batch service as the result of a user request. When the user removes Compute Nodes from a Pool (by resizing/shrinking the pool) or when the Job is being disabled, the user can specify that running Tasks on the Compute Nodes be requeued for execution. This count tracks how many times the Task has been requeued for these reasons. */\n  requeueCount: number;\n  /** The most recent time at which the Task has been requeued by the Batch service as the result of a user request. This property is set only if the requeueCount is nonzero. */\n  lastRequeueTime?: Date | string;\n  /** The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property. */\n  result?: BatchTaskExecutionResult;\n}\n\n/** Information about the Compute Node on which a Task ran. */\nexport interface BatchNodeInfo {\n  /** An identifier for the Node on which the Task ran, which can be passed when adding a Task to request that the Task be scheduled on this Compute Node. */\n  affinityId?: string;\n  /** The URL of the Compute Node on which the Task ran. */\n  nodeUrl?: string;\n  /** The ID of the Pool on which the Task ran. */\n  poolId?: string;\n  /** The ID of the Compute Node on which the Task ran. */\n  nodeId?: string;\n  /** The root directory of the Task on the Compute Node. */\n  taskRootDirectory?: string;\n  /** The URL to the root directory of the Task on the Compute Node. */\n  taskRootDirectoryUrl?: string;\n}\n\n/** Resource usage statistics for a Task. */\nexport interface BatchTaskStatistics {\n  /** The URL of the statistics. */\n  url: string;\n  /** The start time of the time range covered by the statistics. */\n  startTime: Date | string;\n  /** The time at which the statistics were last updated. All statistics are limited to the range between startTime and lastUpdateTime. */\n  lastUpdateTime: Date | string;\n  /** The total user mode CPU time (summed across all cores and all Compute Nodes) consumed by the Task. */\n  userCPUTime: string;\n  /** The total kernel mode CPU time (summed across all cores and all Compute Nodes) consumed by the Task. */\n  kernelCPUTime: string;\n  /** The total wall clock time of the Task. The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If the Task was retried, this includes the wall clock time of all the Task retries. */\n  wallClockTime: string;\n  /** The total number of disk read operations made by the Task. */\n  readIOps: number;\n  /** The total number of disk write operations made by the Task. */\n  writeIOps: number;\n  /** The total gibibytes read from disk by the Task. */\n  readIOGiB: number;\n  /** The total gibibytes written to disk by the Task. */\n  writeIOGiB: number;\n  /** The total wait time of the Task. The wait time for a Task is defined as the elapsed time between the creation of the Task and the start of Task execution. (If the Task is retried due to failures, the wait time is the time to the most recent Task execution.). */\n  waitTime: string;\n}\n\n/** A collection of Azure Batch Tasks to add. */\nexport interface BatchTaskGroup {\n  /** The collection of Tasks to add. The maximum count of Tasks is 100. The total serialized size of this collection must be less than 1MB. If it is greater than 1MB (for example if each Task has 100's of resource files or environment variables), the request will fail with code 'RequestBodyTooLarge' and should be retried again with fewer Tasks. */\n  value: Array<BatchTaskCreateContent>;\n}\n\n/** Parameters for creating a user account for RDP or SSH access on an Azure Batch Compute Node. */\nexport interface BatchNodeUserCreateContent {\n  /** The user name of the Account. */\n  name: string;\n  /** Whether the Account should be an administrator on the Compute Node. The default value is false. */\n  isAdmin?: boolean;\n  /** The time at which the Account should expire. If omitted, the default is 1 day from the current time. For Linux Compute Nodes, the expiryTime has a precision up to a day. */\n  expiryTime?: Date | string;\n  /** The password of the Account. The password is required for Windows Compute Nodes (those created with 'virtualMachineConfiguration' using a Windows Image reference). For Linux Compute Nodes, the password can optionally be specified along with the sshPublicKey property. */\n  password?: string;\n  /** The SSH public key that can be used for remote login to the Compute Node. The public key should be compatible with OpenSSH encoding and should be base 64 encoded. This property can be specified only for Linux Compute Nodes. If this is specified for a Windows Compute Node, then the Batch service rejects the request; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  sshPublicKey?: string;\n}\n\n/** Parameters for updating a user account for RDP or SSH access on an Azure Batch Compute Node. */\nexport interface BatchNodeUserUpdateContent {\n  /** The password of the Account. The password is required for Windows Compute Nodes (those created with 'virtualMachineConfiguration' using a Windows Image reference). For Linux Compute Nodes, the password can optionally be specified along with the sshPublicKey property. If omitted, any existing password is removed. */\n  password?: string;\n  /** The time at which the Account should expire. If omitted, the default is 1 day from the current time. For Linux Compute Nodes, the expiryTime has a precision up to a day. */\n  expiryTime?: Date | string;\n  /** The SSH public key that can be used for remote login to the Compute Node. The public key should be compatible with OpenSSH encoding and should be base 64 encoded. This property can be specified only for Linux Compute Nodes. If this is specified for a Windows Compute Node, then the Batch service rejects the request; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). If omitted, any existing SSH public key is removed. */\n  sshPublicKey?: string;\n}\n\n/** Parameters for rebooting an Azure Batch Compute Node. */\nexport interface BatchNodeRebootContent {\n  /** When to reboot the Compute Node and what to do with currently running Tasks. The default value is requeue. */\n  nodeRebootOption?: BatchNodeRebootOption;\n}\n\n/** Parameters for disabling scheduling on an Azure Batch Compute Node. */\nexport interface BatchNodeDisableSchedulingContent {\n  /** What to do with currently running Tasks when disabling Task scheduling on the Compute Node. The default value is requeue. */\n  nodeDisableSchedulingOption?: BatchNodeDisableSchedulingOption;\n}\n\n/** The Azure Batch service log files upload parameters for a Compute Node. */\nexport interface UploadBatchServiceLogsContent {\n  /** The URL of the container within Azure Blob Storage to which to upload the Batch Service log file(s). If a user assigned managed identity is not being used, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. The SAS duration must allow enough time for the upload to finish. The start time for SAS is optional and recommended to not be specified. */\n  containerUrl: string;\n  /** The start of the time range from which to upload Batch Service log file(s). Any log file containing a log message in the time range will be uploaded. This means that the operation might retrieve more logs than have been requested since the entire log file is always uploaded, but the operation should not retrieve fewer logs than have been requested. */\n  startTime: Date | string;\n  /** The end of the time range from which to upload Batch Service log file(s). Any log file containing a log message in the time range will be uploaded. This means that the operation might retrieve more logs than have been requested since the entire log file is always uploaded, but the operation should not retrieve fewer logs than have been requested. If omitted, the default is to upload all logs available after the startTime. */\n  endTime?: Date | string;\n  /** The reference to the user assigned identity to use to access Azure Blob Storage specified by containerUrl. The identity must have write access to the Azure Blob Storage container. */\n  identityReference?: BatchNodeIdentityReference;\n}\n\n/** Alias for CachingType */\nexport type CachingType = string;\n/** Alias for StorageAccountType */\nexport type StorageAccountType = string;\n/** Alias for ContainerType */\nexport type ContainerType = string;\n/** Alias for DiskEncryptionTarget */\nexport type DiskEncryptionTarget = string;\n/** Alias for BatchNodePlacementPolicyType */\nexport type BatchNodePlacementPolicyType = string;\n/** Alias for DiffDiskPlacement */\nexport type DiffDiskPlacement = string;\n/** Alias for SecurityTypes */\nexport type SecurityTypes = string;\n/** Alias for DynamicVNetAssignmentScope */\nexport type DynamicVNetAssignmentScope = string;\n/** Alias for InboundEndpointProtocol */\nexport type InboundEndpointProtocol = string;\n/** Alias for NetworkSecurityGroupRuleAccess */\nexport type NetworkSecurityGroupRuleAccess = string;\n/** Alias for IpAddressProvisioningType */\nexport type IpAddressProvisioningType = string;\n/** Alias for ContainerWorkingDirectory */\nexport type ContainerWorkingDirectory = string;\n/** Alias for AutoUserScope */\nexport type AutoUserScope = string;\n/** Alias for ElevationLevel */\nexport type ElevationLevel = string;\n/** Alias for BatchNodeFillType */\nexport type BatchNodeFillType = string;\n/** Alias for LoginMode */\nexport type LoginMode = string;\n/** Alias for BatchNodeCommunicationMode */\nexport type BatchNodeCommunicationMode = string;\n/** Alias for UpgradeMode */\nexport type UpgradeMode = string;\n/** Alias for BatchNodeDeallocationOption */\nexport type BatchNodeDeallocationOption = string;\n/** Alias for BatchJobState */\nexport type BatchJobState = string;\n/** Alias for OutputFileUploadCondition */\nexport type OutputFileUploadCondition = string;\n/** Alias for AccessScope */\nexport type AccessScope = string;\n/** Alias for BatchPoolLifetimeOption */\nexport type BatchPoolLifetimeOption = string;\n/** Alias for OnAllBatchTasksComplete */\nexport type OnAllBatchTasksComplete = string;\n/** Alias for OnBatchTaskFailure */\nexport type OnBatchTaskFailure = string;\n/** Alias for ErrorCategory */\nexport type ErrorCategory = string;\n/** Alias for DisableBatchJobOption */\nexport type DisableBatchJobOption = string;\n/** Alias for BatchTaskExecutionResult */\nexport type BatchTaskExecutionResult = string;\n/** Alias for BatchJobScheduleState */\nexport type BatchJobScheduleState = string;\n/** Alias for BatchJobAction */\nexport type BatchJobAction = string;\n/** Alias for DependencyAction */\nexport type DependencyAction = string;\n/** Alias for BatchTaskState */\nexport type BatchTaskState = string;\n/** Alias for BatchNodeRebootOption */\nexport type BatchNodeRebootOption = string;\n/** Alias for BatchNodeDisableSchedulingOption */\nexport type BatchNodeDisableSchedulingOption = string;\n"]}
+{"version":3,"file":"models.js","sourceRoot":"","sources":["../../src/models.ts"],"names":[],"mappings":"AAAA,uCAAuC;AACvC,kCAAkC","sourcesContent":["// Copyright (c) Microsoft Corporation.\n// Licensed under the MIT License.\n\n/** Parameters for creating an Azure Batch Pool. */\nexport interface BatchPoolCreateContent {\n  /** A string that uniquely identifies the Pool within the Account. The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two Pool IDs within an Account that differ only by case). */\n  id: string;\n  /** The display name for the Pool. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** The size of virtual machines in the Pool. All virtual machines in a Pool are the same size. For information about available VM sizes for Pools using Images from the Virtual Machines Marketplace (pools created with virtualMachineConfiguration), see Sizes for Virtual Machines (Linux) (https://azure.microsoft.com/documentation/articles/virtual-machines-linux-sizes/) or Sizes for Virtual Machines (Windows) (https://azure.microsoft.com/documentation/articles/virtual-machines-windows-sizes/). Batch supports all Azure VM sizes except STANDARD_A0 and those with premium storage (STANDARD_GS, STANDARD_DS, and STANDARD_DSV2 series). */\n  vmSize: string;\n  /** The virtual machine configuration for the Pool. This property must be specified. */\n  virtualMachineConfiguration?: VirtualMachineConfiguration;\n  /** The timeout for allocation of Compute Nodes to the Pool. This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  resizeTimeout?: string;\n  /** The user-specified tags associated with the pool. The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. */\n  resourceTags?: Record<string, string>;\n  /** The desired number of dedicated Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. */\n  targetDedicatedNodes?: number;\n  /** The desired number of Spot/Low-priority Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. */\n  targetLowPriorityNodes?: number;\n  /** Whether the Pool size should automatically adjust over time. If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula property is required and the Pool automatically resizes according to the formula. The default value is false. */\n  enableAutoScale?: boolean;\n  /** A formula for the desired number of Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. For more information about specifying this formula, see 'Automatically scale Compute Nodes in an Azure Batch Pool' (https://azure.microsoft.com/documentation/articles/batch-automatic-scaling/). */\n  autoScaleFormula?: string;\n  /** The time interval at which to automatically adjust the Pool size according to the autoscale formula. The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  autoScaleEvaluationInterval?: string;\n  /** Whether the Pool permits direct communication between Compute Nodes. Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. */\n  enableInterNodeCommunication?: boolean;\n  /** The network configuration for the Pool. */\n  networkConfiguration?: NetworkConfiguration;\n  /** A Task specified to run on each Compute Node as it joins the Pool. The Task runs when the Compute Node is added to the Pool or when the Compute Node is restarted. */\n  startTask?: BatchStartTask;\n  /** The list of Packages to be installed on each Compute Node in the Pool. When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** The number of task slots that can be used to run concurrent tasks on a single compute node in the pool. The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. */\n  taskSlotsPerNode?: number;\n  /** How Tasks are distributed across Compute Nodes in a Pool. If not specified, the default is spread. */\n  taskSchedulingPolicy?: BatchTaskSchedulingPolicy;\n  /** The list of user Accounts to be created on each Compute Node in the Pool. */\n  userAccounts?: Array<UserAccount>;\n  /** A list of name-value pairs associated with the Pool as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n  /** Mount storage using specified file system for the entire lifetime of the pool. Mount the storage using Azure fileshare, NFS, CIFS or Blobfuse based file system. */\n  mountConfiguration?: Array<MountConfiguration>;\n  /**\n   * The desired node communication mode for the pool. If omitted, the default value is Default.\n   *\n   * Possible values: \"default\", \"classic\", \"simplified\"\n   */\n  targetNodeCommunicationMode?: BatchNodeCommunicationMode;\n  /** The upgrade policy for the Pool. Describes an upgrade policy - automatic, manual, or rolling. */\n  upgradePolicy?: UpgradePolicy;\n}\n\n/**\n * The configuration for Compute Nodes in a Pool based on the Azure Virtual\n * Machines infrastructure.\n */\nexport interface VirtualMachineConfiguration {\n  /** A reference to the Azure Virtual Machines Marketplace Image or the custom Virtual Machine Image to use. */\n  imageReference: ImageReference;\n  /** The SKU of the Batch Compute Node agent to be provisioned on Compute Nodes in the Pool. The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. */\n  nodeAgentSKUId: string;\n  /** Windows operating system settings on the virtual machine. This property must not be specified if the imageReference property specifies a Linux OS Image. */\n  windowsConfiguration?: WindowsConfiguration;\n  /** The configuration for data disks attached to the Compute Nodes in the Pool. This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://docs.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://docs.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. */\n  dataDisks?: Array<DataDisk>;\n  /**\n   * This only applies to Images that contain the Windows operating system, and\n   * should only be used when you hold valid on-premises licenses for the Compute\n   * Nodes which will be deployed. If omitted, no on-premises licensing discount is\n   * applied. Values are:\n   *\n   *  Windows_Server - The on-premises license is for Windows\n   * Server.\n   *  Windows_Client - The on-premises license is for Windows Client.\n   *\n   */\n  licenseType?: string;\n  /** The container configuration for the Pool. If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. */\n  containerConfiguration?: ContainerConfiguration;\n  /** The disk encryption configuration for the pool. If specified, encryption is performed on each node in the pool during node provisioning. */\n  diskEncryptionConfiguration?: DiskEncryptionConfiguration;\n  /** The node placement configuration for the pool. This configuration will specify rules on how nodes in the pool will be physically allocated. */\n  nodePlacementConfiguration?: BatchNodePlacementConfiguration;\n  /** The virtual machine extension for the pool. If specified, the extensions mentioned in this configuration will be installed on each node. */\n  extensions?: Array<VMExtension>;\n  /** Settings for the operating system disk of the Virtual Machine. */\n  osDisk?: OSDisk;\n  /** Specifies the security profile settings for the virtual machine or virtual machine scale set. */\n  securityProfile?: SecurityProfile;\n  /** Specifies the service artifact reference id used to set same image version for all virtual machines in the scale set when using 'latest' image version. The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} */\n  serviceArtifactReference?: ServiceArtifactReference;\n}\n\n/**\n * A reference to an Azure Virtual Machines Marketplace Image or a Azure Compute Gallery Image.\n * To get the list of all Azure Marketplace Image references verified by Azure Batch, see the\n * ' List Supported Images ' operation.\n */\nexport interface ImageReference {\n  /** The publisher of the Azure Virtual Machines Marketplace Image. For example, Canonical or MicrosoftWindowsServer. */\n  publisher?: string;\n  /** The offer type of the Azure Virtual Machines Marketplace Image. For example, UbuntuServer or WindowsServer. */\n  offer?: string;\n  /** The SKU of the Azure Virtual Machines Marketplace Image. For example, 18.04-LTS or 2019-Datacenter. */\n  sku?: string;\n  /** The version of the Azure Virtual Machines Marketplace Image. A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. */\n  version?: string;\n  /** The ARM resource identifier of the Azure Compute Gallery Image. Compute Nodes in the Pool will be created using this Image Id. This is of the form /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/images/{imageDefinitionName}/versions/{VersionId} or /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/images/{imageDefinitionName} for always defaulting to the latest image version. This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */\n  virtualMachineImageId?: string;\n  /** The shared gallery image unique identifier. This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. */\n  sharedGalleryImageId?: string;\n  /** The community gallery image unique identifier. This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. */\n  communityGalleryImageId?: string;\n}\n\n/** Windows operating system settings to apply to the virtual machine. */\nexport interface WindowsConfiguration {\n  /** Whether automatic updates are enabled on the virtual machine. If omitted, the default value is true. */\n  enableAutomaticUpdates?: boolean;\n}\n\n/**\n * Settings which will be used by the data disks associated to Compute Nodes in\n * the Pool. When using attached data disks, you need to mount and format the\n * disks from within a VM to use them.\n */\nexport interface DataDisk {\n  /** The logical unit number. The logicalUnitNumber is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct logicalUnitNumber. The value must be between 0 and 63, inclusive. */\n  lun: number;\n  /**\n   * The type of caching to be enabled for the data disks. The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/.\n   *\n   * Possible values: \"none\", \"readonly\", \"readwrite\"\n   */\n  caching?: CachingType;\n  /** The initial disk size in gigabytes. */\n  diskSizeGB: number;\n  /**\n   * The storage Account type to be used for the data disk. If omitted, the default is \"standard_lrs\".\n   *\n   * Possible values: \"standard_lrs\", \"premium_lrs\", \"standardssd_lrs\"\n   */\n  storageAccountType?: StorageAccountType;\n}\n\n/** The configuration for container-enabled Pools. */\nexport interface ContainerConfiguration {\n  /**\n   * The container technology to be used.\n   *\n   * Possible values: \"dockerCompatible\", \"criCompatible\"\n   */\n  type: ContainerType;\n  /** The collection of container Image names. This is the full Image reference, as would be specified to \"docker pull\". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. */\n  containerImageNames?: string[];\n  /** Additional private registries from which containers can be pulled. If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. */\n  containerRegistries?: Array<ContainerRegistryReference>;\n}\n\n/** A private container registry. */\nexport interface ContainerRegistryReference {\n  /** The user name to log into the registry server. */\n  username?: string;\n  /** The password to log into the registry server. */\n  password?: string;\n  /** The registry URL. If omitted, the default is \"docker.io\". */\n  registryServer?: string;\n  /** The reference to the user assigned identity to use to access an Azure Container Registry instead of username and password. */\n  identityReference?: BatchNodeIdentityReference;\n}\n\n/**\n * The reference to a user assigned identity associated with the Batch pool which\n * a compute node will use.\n */\nexport interface BatchNodeIdentityReference {\n  /** The ARM resource id of the user assigned identity. */\n  resourceId?: string;\n}\n\n/**\n * The disk encryption configuration applied on compute nodes in the pool.\n * Disk encryption configuration is not supported on Linux pool created with\n * Azure Compute Gallery Image.\n */\nexport interface DiskEncryptionConfiguration {\n  /** The list of disk targets Batch Service will encrypt on the compute node. The list of disk targets Batch Service will encrypt on the compute node. */\n  targets?: DiskEncryptionTarget[];\n}\n\n/**\n * For regional placement, nodes in the pool will be allocated in the same region.\n * For zonal placement, nodes in the pool will be spread across different zones\n * with best effort balancing.\n */\nexport interface BatchNodePlacementConfiguration {\n  /**\n   * Node placement Policy type on Batch Pools. Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy.\n   *\n   * Possible values: \"Shared\", \"Startup\", \"VfsMounts\", \"Task\", \"JobPrep\", \"Applications\"\n   */\n  policy?: BatchNodePlacementPolicyType;\n}\n\n/** The configuration for virtual machine extensions. */\nexport interface VMExtension {\n  /** The name of the virtual machine extension. */\n  name: string;\n  /** The name of the extension handler publisher. */\n  publisher: string;\n  /** The type of the extension. */\n  type: string;\n  /** The version of script handler. */\n  typeHandlerVersion?: string;\n  /** Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. */\n  autoUpgradeMinorVersion?: boolean;\n  /** Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. */\n  enableAutomaticUpgrade?: boolean;\n  /** JSON formatted public settings for the extension. */\n  settings?: Record<string, string>;\n  /** The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. */\n  protectedSettings?: Record<string, string>;\n  /** The collection of extension names. Collection of extension names after which this extension needs to be provisioned. */\n  provisionAfterExtensions?: string[];\n}\n\n/** Settings for the operating system disk of the compute node (VM). */\nexport interface OSDisk {\n  /** Specifies the ephemeral Disk Settings for the operating system disk used by the compute node (VM). */\n  ephemeralOSDiskSettings?: DiffDiskSettings;\n  /**\n   * Specifies the caching requirements. Possible values are: None, ReadOnly, ReadWrite. The default values are: None for Standard storage. ReadOnly for Premium storage.\n   *\n   * Possible values: \"none\", \"readonly\", \"readwrite\"\n   */\n  caching?: CachingType;\n  /** The initial disk size in GB when creating new OS disk. */\n  diskSizeGB?: number;\n  /** The managed disk parameters. */\n  managedDisk?: ManagedDisk;\n  /** Specifies whether writeAccelerator should be enabled or disabled on the disk. */\n  writeAcceleratorEnabled?: boolean;\n}\n\n/**\n * Specifies the ephemeral Disk Settings for the operating system disk used by the\n * compute node (VM).\n */\nexport interface DiffDiskSettings {\n  /**\n   * Specifies the ephemeral disk placement for operating system disk for all VMs in the pool. This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://docs.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://docs.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements.\n   *\n   * Possible values: \"cachedisk\"\n   */\n  placement?: DiffDiskPlacement;\n}\n\n/** The managed disk parameters. */\nexport interface ManagedDisk {\n  /**\n   * The storage account type for managed disk.\n   *\n   * Possible values: \"standard_lrs\", \"premium_lrs\", \"standardssd_lrs\"\n   */\n  storageAccountType?: StorageAccountType;\n  /** Specifies the security profile settings for the managed disk. */\n  securityProfile?: VMDiskSecurityProfile;\n}\n\n/** Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. */\nexport interface VMDiskSecurityProfile {\n  /**\n   * Specifies the EncryptionType of the managed disk. It is set to VMGuestStateOnly for encryption of just the VMGuestState blob, and NonPersistedTPM for not persisting firmware state in the VMGuestState blob. **Note**: It can be set for only Confidential VMs and is required when using Confidential VMs.\n   *\n   * Possible values: \"NonPersistedTPM\", \"VMGuestStateOnly\"\n   */\n  securityEncryptionType?: SecurityEncryptionTypes;\n}\n\n/** Specifies the security profile settings for the virtual machine or virtual machine scale set. */\nexport interface SecurityProfile {\n  /** This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. */\n  encryptionAtHost: boolean;\n  /**\n   * Specifies the SecurityType of the virtual machine. It has to be set to any specified value to enable UefiSettings.\n   *\n   * Possible values: \"trustedLaunch\", \"confidentialVM\"\n   */\n  securityType: SecurityTypes;\n  /** Specifies the security settings like secure boot and vTPM used while creating the virtual machine. Specifies the security settings like secure boot and vTPM used while creating the virtual machine. */\n  uefiSettings: UefiSettings;\n}\n\n/** Specifies the security settings like secure boot and vTPM used while creating the virtual machine. */\nexport interface UefiSettings {\n  /** Specifies whether secure boot should be enabled on the virtual machine. */\n  secureBootEnabled?: boolean;\n  /** Specifies whether vTPM should be enabled on the virtual machine. */\n  vTpmEnabled?: boolean;\n}\n\n/**\n * Specifies the service artifact reference id used to set same image version\n * for all virtual machines in the scale set when using 'latest' image version.\n */\nexport interface ServiceArtifactReference {\n  /** The service artifact reference id of ServiceArtifactReference. The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} */\n  id: string;\n}\n\n/** The network configuration for a Pool. */\nexport interface NetworkConfiguration {\n  /** The ARM resource identifier of the virtual network subnet which the Compute Nodes of the Pool will join. The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication. Enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Also enable outbound connections to Azure Storage on port 443. For more details see: https://docs.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */\n  subnetId?: string;\n  /**\n   * The scope of dynamic vnet assignment.\n   *\n   * Possible values: \"none\", \"job\"\n   */\n  dynamicVNetAssignmentScope?: DynamicVNetAssignmentScope;\n  /** The configuration for endpoints on Compute Nodes in the Batch Pool. */\n  endpointConfiguration?: BatchPoolEndpointConfiguration;\n  /** The Public IPAddress configuration for Compute Nodes in the Batch Pool. */\n  publicIPAddressConfiguration?: PublicIpAddressConfiguration;\n  /** Whether this pool should enable accelerated networking. Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. */\n  enableAcceleratedNetworking?: boolean;\n}\n\n/** The endpoint configuration for a Pool. */\nexport interface BatchPoolEndpointConfiguration {\n  /** A list of inbound NAT Pools that can be used to address specific ports on an individual Compute Node externally. The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. */\n  inboundNATPools: Array<InboundNatPool>;\n}\n\n/**\n * A inbound NAT Pool that can be used to address specific ports on Compute Nodes\n * in a Batch Pool externally.\n */\nexport interface InboundNatPool {\n  /** The name of the endpoint. The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters.  If any invalid values are provided the request fails with HTTP status code 400. */\n  name: string;\n  /**\n   * The protocol of the endpoint.\n   *\n   * Possible values: \"tcp\", \"udp\"\n   */\n  protocol: InboundEndpointProtocol;\n  /** The port number on the Compute Node. This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 22, 3389, 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. */\n  backendPort: number;\n  /** The first port number in the range of external ports that will be used to provide inbound access to the backendPort on individual Compute Nodes. Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. */\n  frontendPortRangeStart: number;\n  /** The last port number in the range of external ports that will be used to provide inbound access to the backendPort on individual Compute Nodes. Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. */\n  frontendPortRangeEnd: number;\n  /** A list of network security group rules that will be applied to the endpoint. The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. */\n  networkSecurityGroupRules?: Array<NetworkSecurityGroupRule>;\n}\n\n/** A network security group rule to apply to an inbound endpoint. */\nexport interface NetworkSecurityGroupRule {\n  /** The priority for this rule. Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. */\n  priority: number;\n  /**\n   * The action that should be taken for a specified IP address, subnet range or tag.\n   *\n   * Possible values: \"allow\", \"deny\"\n   */\n  access: NetworkSecurityGroupRuleAccess;\n  /** The source address prefix or tag to match for the rule. Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses).  If any other values are provided the request fails with HTTP status code 400. */\n  sourceAddressPrefix: string;\n  /** The source port ranges to match for the rule. Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. */\n  sourcePortRanges?: string[];\n}\n\n/** The public IP Address configuration of the networking configuration of a Pool. */\nexport interface PublicIpAddressConfiguration {\n  /**\n   * The provisioning type for Public IP Addresses for the Pool. The default value is BatchManaged.\n   *\n   * Possible values: \"batchmanaged\", \"usermanaged\", \"nopublicipaddresses\"\n   */\n  provision?: IpAddressProvisioningType;\n  /** The list of public IPs which the Batch service will use when provisioning Compute Nodes. The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. */\n  ipAddressIds?: string[];\n}\n\n/**\n * Batch will retry Tasks when a recovery operation is triggered on a Node.\n * Examples of recovery operations include (but are not limited to) when an\n * unhealthy Node is rebooted or a Compute Node disappeared due to host failure.\n * Retries due to recovery operations are independent of and are not counted\n * against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal\n * retry due to a recovery operation may occur. Because of this, all Tasks should\n * be idempotent. This means Tasks need to tolerate being interrupted and\n * restarted without causing any corruption or duplicate data. The best practice\n * for long running Tasks is to use some form of checkpointing. In some cases the\n * StartTask may be re-run even though the Compute Node was not rebooted. Special\n * care should be taken to avoid StartTasks which create breakaway process or\n * install/launch services from the StartTask working directory, as this will\n * block Batch from being able to re-run the StartTask.\n */\nexport interface BatchStartTask {\n  /** The command line of the StartTask. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the StartTask runs. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line.  There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. Files listed under this element are located in the Task's working directory. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of environment variable settings for the StartTask. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** The user identity under which the StartTask runs. If omitted, the Task runs as a non-administrative user unique to the Task. */\n  userIdentity?: UserIdentity;\n  /** The maximum number of times the Task may be retried. The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). */\n  maxTaskRetryCount?: number;\n  /** Whether the Batch service should wait for the StartTask to complete successfully (that is, to exit with exit code 0) before scheduling any Tasks on the Compute Node. If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. */\n  waitForSuccess?: boolean;\n}\n\n/** The container settings for a Task. */\nexport interface BatchTaskContainerSettings {\n  /** Additional options to the container create command. These additional options are supplied as arguments to the \"docker create\" command, in addition to those controlled by the Batch Service. */\n  containerRunOptions?: string;\n  /** The Image to use to create the container in which the Task will run. This is the full Image reference, as would be specified to \"docker pull\". If no tag is provided as part of the Image name, the tag \":latest\" is used as a default. */\n  imageName: string;\n  /** The private registry which contains the container Image. This setting can be omitted if was already provided at Pool creation. */\n  registry?: ContainerRegistryReference;\n  /**\n   * The location of the container Task working directory. The default is 'taskWorkingDirectory'.\n   *\n   * Possible values: \"taskWorkingDirectory\", \"containerImageDefault\"\n   */\n  workingDirectory?: ContainerWorkingDirectory;\n  /** The paths you want to mounted to container task. If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. */\n  containerHostBatchBindMounts?: Array<ContainerHostBatchBindMountEntry>;\n}\n\n/** The entry of path and mount mode you want to mount into task container. */\nexport interface ContainerHostBatchBindMountEntry {\n  /**\n   * The path which be mounted to container customer can select.\n   *\n   * Possible values: \"regional\", \"zonal\"\n   */\n  source?: ContainerHostDataPath;\n  /** Mount this source path as read-only mode or not. Default value is false (read/write mode). For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. */\n  isReadOnly?: boolean;\n}\n\n/** A single file or multiple files to be downloaded to a Compute Node. */\nexport interface ResourceFile {\n  /** The storage container name in the auto storage Account. The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. */\n  autoStorageContainerName?: string;\n  /** The URL of the blob container within Azure Blob Storage. The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. */\n  storageContainerUrl?: string;\n  /** The URL of the file to download. The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. */\n  httpUrl?: string;\n  /** The blob prefix to use when downloading blobs from an Azure Storage container. Only the blobs whose names begin with the specified prefix will be downloaded. The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. */\n  blobPrefix?: string;\n  /** The location on the Compute Node to which to download the file(s), relative to the Task's working directory. If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). */\n  filePath?: string;\n  /** The file permission mode attribute in octal format. This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. */\n  fileMode?: string;\n  /** The reference to the user assigned identity to use to access Azure Blob Storage specified by storageContainerUrl or httpUrl. */\n  identityReference?: BatchNodeIdentityReference;\n}\n\n/** An environment variable to be set on a Task process. */\nexport interface EnvironmentSetting {\n  /** The name of the environment variable. */\n  name: string;\n  /** The value of the environment variable. */\n  value?: string;\n}\n\n/** The definition of the user identity under which the Task is run. Specify either the userName or autoUser property, but not both. */\nexport interface UserIdentity {\n  /** The name of the user identity under which the Task is run. The userName and autoUser properties are mutually exclusive; you must specify one but not both. */\n  username?: string;\n  /** The auto user under which the Task is run. The userName and autoUser properties are mutually exclusive; you must specify one but not both. */\n  autoUser?: AutoUserSpecification;\n}\n\n/** Specifies the options for the auto user that runs an Azure Batch Task. */\nexport interface AutoUserSpecification {\n  /**\n   * The scope for the auto user. The default value is pool. If the pool is running Windows, a value of Task should be specified if stricter isolation between tasks is required, such as if the task mutates the registry in a way which could impact other tasks.\n   *\n   * Possible values: \"task\", \"pool\"\n   */\n  scope?: AutoUserScope;\n  /**\n   * The elevation level of the auto user. The default value is nonAdmin.\n   *\n   * Possible values: \"nonadmin\", \"admin\"\n   */\n  elevationLevel?: ElevationLevel;\n}\n\n/** A reference to an Package to be deployed to Compute Nodes. */\nexport interface BatchApplicationPackageReference {\n  /** The ID of the application to deploy. When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). */\n  applicationId: string;\n  /** The version of the application to deploy. If omitted, the default version is deployed. If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. */\n  version?: string;\n}\n\n/** Specifies how Tasks should be distributed across Compute Nodes. */\nexport interface BatchTaskSchedulingPolicy {\n  /**\n   * How Tasks are distributed across Compute Nodes in a Pool. If not specified, the default is spread.\n   *\n   * Possible values: \"spread\", \"pack\"\n   */\n  nodeFillType: BatchNodeFillType;\n}\n\n/**\n * Properties used to create a user used to execute Tasks on an Azure Batch\n * Compute Node.\n */\nexport interface UserAccount {\n  /** The name of the user Account. Names can contain any Unicode characters up to a maximum length of 20. */\n  name: string;\n  /** The password for the user Account. */\n  password: string;\n  /**\n   * The elevation level of the user Account. The default value is nonAdmin.\n   *\n   * Possible values: \"nonadmin\", \"admin\"\n   */\n  elevationLevel?: ElevationLevel;\n  /** The Linux-specific user configuration for the user Account. This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. */\n  linuxUserConfiguration?: LinuxUserConfiguration;\n  /** The Windows-specific user configuration for the user Account. This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. */\n  windowsUserConfiguration?: WindowsUserConfiguration;\n}\n\n/** Properties used to create a user Account on a Linux Compute Node. */\nexport interface LinuxUserConfiguration {\n  /** The user ID of the user Account. The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. */\n  uid?: number;\n  /** The group ID for the user Account. The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. */\n  gid?: number;\n  /** The SSH private key for the user Account. The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). */\n  sshPrivateKey?: string;\n}\n\n/** Properties used to create a user Account on a Windows Compute Node. */\nexport interface WindowsUserConfiguration {\n  /**\n   * The login mode for the user. The default is 'batch'.\n   *\n   * Possible values: \"batch\", \"interactive\"\n   */\n  loginMode?: LoginMode;\n}\n\n/**\n * The Batch service does not assign any meaning to this metadata; it is solely\n * for the use of user code.\n */\nexport interface MetadataItem {\n  /** The name of the metadata item. */\n  name: string;\n  /** The value of the metadata item. */\n  value: string;\n}\n\n/** The file system to mount on each node. */\nexport interface MountConfiguration {\n  /** The Azure Storage Container to mount using blob FUSE on each node. This property is mutually exclusive with all other properties. */\n  azureBlobFileSystemConfiguration?: AzureBlobFileSystemConfiguration;\n  /** The NFS file system to mount on each node. This property is mutually exclusive with all other properties. */\n  nfsMountConfiguration?: NfsMountConfiguration;\n  /** The CIFS/SMB file system to mount on each node. This property is mutually exclusive with all other properties. */\n  cifsMountConfiguration?: CifsMountConfiguration;\n  /** The Azure File Share to mount on each node. This property is mutually exclusive with all other properties. */\n  azureFileShareConfiguration?: AzureFileShareConfiguration;\n}\n\n/** Information used to connect to an Azure Storage Container using Blobfuse. */\nexport interface AzureBlobFileSystemConfiguration {\n  /** The Azure Storage Account name. */\n  accountName: string;\n  /** The Azure Blob Storage Container name. */\n  containerName: string;\n  /** The Azure Storage Account key. This property is mutually exclusive with both sasKey and identity; exactly one must be specified. */\n  accountKey?: string;\n  /** The Azure Storage SAS token. This property is mutually exclusive with both accountKey and identity; exactly one must be specified. */\n  sasKey?: string;\n  /** Additional command line options to pass to the mount command. These are 'net use' options in Windows and 'mount' options in Linux. */\n  blobfuseOptions?: string;\n  /** The relative path on the compute node where the file system will be mounted. All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. */\n  relativeMountPath: string;\n  /** The reference to the user assigned identity to use to access containerName. This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. */\n  identityReference?: BatchNodeIdentityReference;\n}\n\n/** Information used to connect to an NFS file system. */\nexport interface NfsMountConfiguration {\n  /** The URI of the file system to mount. */\n  source: string;\n  /** The relative path on the compute node where the file system will be mounted. All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. */\n  relativeMountPath: string;\n  /** Additional command line options to pass to the mount command. These are 'net use' options in Windows and 'mount' options in Linux. */\n  mountOptions?: string;\n}\n\n/** Information used to connect to a CIFS file system. */\nexport interface CifsMountConfiguration {\n  /** The user to use for authentication against the CIFS file system. */\n  username: string;\n  /** The URI of the file system to mount. */\n  source: string;\n  /** The relative path on the compute node where the file system will be mounted. All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. */\n  relativeMountPath: string;\n  /** Additional command line options to pass to the mount command. These are 'net use' options in Windows and 'mount' options in Linux. */\n  mountOptions?: string;\n  /** The password to use for authentication against the CIFS file system. */\n  password: string;\n}\n\n/** Information used to connect to an Azure Fileshare. */\nexport interface AzureFileShareConfiguration {\n  /** The Azure Storage account name. */\n  accountName: string;\n  /** The Azure Files URL. This is of the form 'https://{account}.file.core.windows.net/'. */\n  azureFileUrl: string;\n  /** The Azure Storage account key. */\n  accountKey: string;\n  /** The relative path on the compute node where the file system will be mounted. All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. */\n  relativeMountPath: string;\n  /** Additional command line options to pass to the mount command. These are 'net use' options in Windows and 'mount' options in Linux. */\n  mountOptions?: string;\n}\n\n/** Describes an upgrade policy - automatic, manual, or rolling. */\nexport interface UpgradePolicy {\n  /**\n   * Specifies the mode of an upgrade to virtual machines in the scale set.<br /><br /> Possible values are:<br /><br /> **Manual** - You  control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action.<br /><br /> **Automatic** - All virtual machines in the scale set are automatically updated at the same time.<br /><br /> **Rolling** - Scale set performs updates in batches with an optional pause time in between.\n   *\n   * Possible values: \"automatic\", \"manual\", \"rolling\"\n   */\n  mode: UpgradeMode;\n  /** Configuration parameters used for performing automatic OS Upgrade. The configuration parameters used for performing automatic OS upgrade. */\n  automaticOSUpgradePolicy?: AutomaticOsUpgradePolicy;\n  /** The configuration parameters used while performing a rolling upgrade. */\n  rollingUpgradePolicy?: RollingUpgradePolicy;\n}\n\n/** The configuration parameters used for performing automatic OS upgrade. */\nexport interface AutomaticOsUpgradePolicy {\n  /** Whether OS image rollback feature should be disabled. */\n  disableAutomaticRollback?: boolean;\n  /** Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available. <br /><br /> If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. */\n  enableAutomaticOSUpgrade?: boolean;\n  /** Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. */\n  useRollingUpgradePolicy?: boolean;\n  /** Defer OS upgrades on the TVMs if they are running tasks. */\n  osRollingUpgradeDeferral?: boolean;\n}\n\n/** The configuration parameters used while performing a rolling upgrade. */\nexport interface RollingUpgradePolicy {\n  /** Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. */\n  enableCrossZoneUpgrade?: boolean;\n  /** The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. */\n  maxBatchInstancePercent?: number;\n  /** The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. */\n  maxUnhealthyInstancePercent?: number;\n  /** The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. */\n  maxUnhealthyUpgradedInstancePercent?: number;\n  /** The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format.. */\n  pauseTimeBetweenBatches?: string;\n  /** Upgrade all unhealthy instances in a scale set before any healthy instances. */\n  prioritizeUnhealthyInstances?: boolean;\n  /** Rollback failed instances to previous model if the Rolling Upgrade policy is violated. */\n  rollbackFailedInstancesOnPolicyBreach?: boolean;\n}\n\n/** Represents a name-value pair. */\nexport interface NameValuePair {\n  /** The name in the name-value pair. */\n  name?: string;\n  /** The value in the name-value pair. */\n  value?: string;\n}\n\n/** Parameters for updating an Azure Batch Pool. */\nexport interface BatchPoolUpdateContent {\n  /** The display name for the Pool. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. This field can be updated only when the pool is empty. */\n  displayName?: string;\n  /** The size of virtual machines in the Pool. For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://docs.microsoft.com/azure/batch/batch-pool-vm-sizes).<br /><br />This field can be updated only when the pool is empty. */\n  vmSize?: string;\n  /** Whether the Pool permits direct communication between Compute Nodes. Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false.<br /><br />This field can be updated only when the pool is empty. */\n  enableInterNodeCommunication?: boolean;\n  /** A Task to run on each Compute Node as it joins the Pool. The Task runs when the Compute Node is added to the Pool or when the Compute Node is restarted. If this element is present, it overwrites any existing StartTask. If omitted, any existing StartTask is left unchanged. */\n  startTask?: BatchStartTask;\n  /** A list of Packages to be installed on each Compute Node in the Pool. Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. If this element is present, it replaces any existing Package references. If you specify an empty collection, then all Package references are removed from the Pool. If omitted, any existing Package references are left unchanged. */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** A list of name-value pairs associated with the Pool as metadata. If this element is present, it replaces any existing metadata configured on the Pool. If you specify an empty collection, any metadata is removed from the Pool. If omitted, any existing metadata is left unchanged. */\n  metadata?: Array<MetadataItem>;\n  /** The virtual machine configuration for the Pool. This property must be specified.<br /><br />This field can be updated only when the pool is empty. */\n  virtualMachineConfiguration?: VirtualMachineConfiguration;\n  /**\n   * The desired node communication mode for the pool. If this element is present, it replaces the existing targetNodeCommunicationMode configured on the Pool. If omitted, any existing metadata is left unchanged.\n   *\n   * Possible values: \"default\", \"classic\", \"simplified\"\n   */\n  targetNodeCommunicationMode?: BatchNodeCommunicationMode;\n  /** The number of task slots that can be used to run concurrent tasks on a single compute node in the pool. The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256.<br /><br />This field can be updated only when the pool is empty. */\n  taskSlotsPerNode?: number;\n  /** How Tasks are distributed across Compute Nodes in a Pool. If not specified, the default is spread.<br /><br />This field can be updated only when the pool is empty. */\n  taskSchedulingPolicy?: BatchTaskSchedulingPolicy;\n  /** The network configuration for the Pool. This field can be updated only when the pool is empty. */\n  networkConfiguration?: NetworkConfiguration;\n  /** The user-specified tags associated with the pool. The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'.<br /><br />This field can be updated only when the pool is empty. */\n  resourceTags?: Record<string, string>;\n  /** The list of user Accounts to be created on each Compute Node in the Pool. This field can be updated only when the pool is empty. */\n  userAccounts?: Array<UserAccount>;\n  /** Mount storage using specified file system for the entire lifetime of the pool. Mount the storage using Azure fileshare, NFS, CIFS or Blobfuse based file system.<br /><br />This field can be updated only when the pool is empty. */\n  mountConfiguration?: Array<MountConfiguration>;\n  /** The upgrade policy for the Pool. Describes an upgrade policy - automatic, manual, or rolling.<br /><br />This field can be updated only when the pool is empty. */\n  upgradePolicy?: UpgradePolicy;\n}\n\n/** Parameters for enabling automatic scaling on an Azure Batch Pool. */\nexport interface BatchPoolEnableAutoScaleContent {\n  /** The formula for the desired number of Compute Nodes in the Pool. The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). If you specify a new interval, then the existing autoscale evaluation schedule will be stopped and a new autoscale evaluation schedule will be started, with its starting time being the time when this request was issued. */\n  autoScaleFormula?: string;\n  /** The time interval at which to automatically adjust the Pool size according to the autoscale formula. The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). If you specify a new interval, then the existing autoscale evaluation schedule will be stopped and a new autoscale evaluation schedule will be started, with its starting time being the time when this request was issued. */\n  autoScaleEvaluationInterval?: string;\n}\n\n/** Parameters for evaluating an automatic scaling formula on an Azure Batch Pool. */\nexport interface BatchPoolEvaluateAutoScaleContent {\n  /** The formula for the desired number of Compute Nodes in the Pool. The formula is validated and its results calculated, but it is not applied to the Pool. To apply the formula to the Pool, 'Enable automatic scaling on a Pool'. For more information about specifying this formula, see Automatically scale Compute Nodes in an Azure Batch Pool (https://azure.microsoft.com/documentation/articles/batch-automatic-scaling). */\n  autoScaleFormula: string;\n}\n\n/** Parameters for changing the size of an Azure Batch Pool. */\nexport interface BatchPoolResizeContent {\n  /** The desired number of dedicated Compute Nodes in the Pool. */\n  targetDedicatedNodes?: number;\n  /** The desired number of Spot/Low-priority Compute Nodes in the Pool. */\n  targetLowPriorityNodes?: number;\n  /** The timeout for allocation of Nodes to the Pool or removal of Compute Nodes from the Pool. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  resizeTimeout?: string;\n  /**\n   * Determines what to do with a Compute Node and its running task(s) if the Pool size is decreasing. The default value is requeue.\n   *\n   * Possible values: \"requeue\", \"terminate\", \"taskcompletion\", \"retaineddata\"\n   */\n  nodeDeallocationOption?: BatchNodeDeallocationOption;\n}\n\n/** Parameters for replacing properties on an Azure Batch Pool. */\nexport interface BatchPoolReplaceContent {\n  /** A Task to run on each Compute Node as it joins the Pool. The Task runs when the Compute Node is added to the Pool or when the Compute Node is restarted. If this element is present, it overwrites any existing StartTask. If omitted, any existing StartTask is removed from the Pool. */\n  startTask?: BatchStartTask;\n  /** The list of Application Packages to be installed on each Compute Node in the Pool. The list replaces any existing Application Package references on the Pool. Changes to Application Package references affect all new Compute Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Application Package references on any given Pool. If omitted, or if you specify an empty collection, any existing Application Packages references are removed from the Pool. A maximum of 10 references may be specified on a given Pool. */\n  applicationPackageReferences: Array<BatchApplicationPackageReference>;\n  /** A list of name-value pairs associated with the Pool as metadata. This list replaces any existing metadata configured on the Pool. If omitted, or if you specify an empty collection, any existing metadata is removed from the Pool. */\n  metadata: Array<MetadataItem>;\n  /**\n   * The desired node communication mode for the pool. This setting replaces any existing targetNodeCommunication setting on the Pool. If omitted, the existing setting is default.\n   *\n   * Possible values: \"default\", \"classic\", \"simplified\"\n   */\n  targetNodeCommunicationMode?: BatchNodeCommunicationMode;\n}\n\n/** Parameters for removing nodes from an Azure Batch Pool. */\nexport interface BatchNodeRemoveContent {\n  /** A list containing the IDs of the Compute Nodes to be removed from the specified Pool. A maximum of 100 nodes may be removed per request. */\n  nodeList: string[];\n  /** The timeout for removal of Compute Nodes to the Pool. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  resizeTimeout?: string;\n  /**\n   * Determines what to do with a Compute Node and its running task(s) after it has been selected for deallocation. The default value is requeue.\n   *\n   * Possible values: \"requeue\", \"terminate\", \"taskcompletion\", \"retaineddata\"\n   */\n  nodeDeallocationOption?: BatchNodeDeallocationOption;\n}\n\n/** An Azure Batch Job. */\nexport interface BatchJob {\n  /** The priority of the Job. Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. */\n  priority?: number;\n  /** Whether Tasks in this job can be preempted by other high priority jobs. If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. */\n  allowTaskPreemption?: boolean;\n  /** The maximum number of tasks that can be executed in parallel for the job. The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. */\n  maxParallelTasks?: number;\n  /** The execution constraints for the Job. */\n  constraints?: BatchJobConstraints;\n  /** The Pool settings associated with the Job. */\n  poolInfo: BatchPoolInfo;\n  /**\n   * The action the Batch service should take when all Tasks in the Job are in the completed state. The default is noaction.\n   *\n   * Possible values: \"noaction\", \"terminatejob\"\n   */\n  onAllTasksComplete?: OnAllBatchTasksComplete;\n  /** A list of name-value pairs associated with the Job as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/** The execution constraints for a Job. */\nexport interface BatchJobConstraints {\n  /** The maximum elapsed time that the Job may run, measured from the time the Job is created. If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. */\n  maxWallClockTime?: string;\n  /** The maximum number of times each Task may be retried. The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). */\n  maxTaskRetryCount?: number;\n}\n\n/**\n * Specifies details of a Job Manager Task.\n * The Job Manager Task is automatically started when the Job is created. The\n * Batch service tries to schedule the Job Manager Task before any other Tasks in\n * the Job. When shrinking a Pool, the Batch service tries to preserve Nodes where\n * Job Manager Tasks are running for as long as possible (that is, Compute Nodes\n * running 'normal' Tasks are removed before Compute Nodes running Job Manager\n * Tasks). When a Job Manager Task fails and needs to be restarted, the system\n * tries to schedule it at the highest priority. If there are no idle Compute\n * Nodes available, the system may terminate one of the running Tasks in the Pool\n * and return it to the queue in order to make room for the Job Manager Task to\n * restart. Note that a Job Manager Task in one Job does not have priority over\n * Tasks in other Jobs. Across Jobs, only Job level priorities are observed. For\n * example, if a Job Manager in a priority 0 Job needs to be restarted, it will\n * not displace Tasks of a priority 1 Job. Batch will retry Tasks when a recovery\n * operation is triggered on a Node. Examples of recovery operations include (but\n * are not limited to) when an unhealthy Node is rebooted or a Compute Node\n * disappeared due to host failure. Retries due to recovery operations are\n * independent of and are not counted against the maxTaskRetryCount. Even if the\n * maxTaskRetryCount is 0, an internal retry due to a recovery operation may\n * occur. Because of this, all Tasks should be idempotent. This means Tasks need\n * to tolerate being interrupted and restarted without causing any corruption or\n * duplicate data. The best practice for long running Tasks is to use some form of\n * checkpointing.\n */\nexport interface BatchJobManagerTask {\n  /** A string that uniquely identifies the Job Manager Task within the Job. The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. */\n  id: string;\n  /** The display name of the Job Manager Task. It need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** The command line of the Job Manager Task. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the Job Manager Task runs. If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line. Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of files that the Batch service will upload from the Compute Node after running the command line. For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. */\n  outputFiles?: Array<OutputFile>;\n  /** A list of environment variable settings for the Job Manager Task. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** Constraints that apply to the Job Manager Task. */\n  constraints?: BatchTaskConstraints;\n  /** The number of scheduling slots that the Task requires to run. The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. */\n  requiredSlots?: number;\n  /** Whether completion of the Job Manager Task signifies completion of the entire Job. If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. */\n  killJobOnCompletion?: boolean;\n  /** The user identity under which the Job Manager Task runs. If omitted, the Task runs as a non-administrative user unique to the Task. */\n  userIdentity?: UserIdentity;\n  /** Whether the Job Manager Task requires exclusive use of the Compute Node where it runs. If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. */\n  runExclusive?: boolean;\n  /**\n   * A list of Application Packages that the Batch service will deploy to the\n   * Compute Node before running the command line.Application Packages are\n   * downloaded and deployed to a shared directory, not the Task working\n   * directory. Therefore, if a referenced Application Package is already\n   * on the Compute Node, and is up to date, then it is not re-downloaded;\n   * the existing copy on the Compute Node is used. If a referenced Application\n   * Package cannot be installed, for example because the package has been deleted\n   * or because download failed, the Task fails.\n   */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** The settings for an authentication token that the Task can use to perform Batch service operations. If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job. */\n  authenticationTokenSettings?: AuthenticationTokenSettings;\n  /** Whether the Job Manager Task may run on a Spot/Low-priority Compute Node. The default value is true. */\n  allowLowPriorityNode?: boolean;\n}\n\n/** On every file uploads, Batch service writes two log files to the compute node, 'fileuploadout.txt' and 'fileuploaderr.txt'. These log files are used to learn more about a specific failure. */\nexport interface OutputFile {\n  /** A pattern indicating which file(s) to upload. Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with \".\" it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \\ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. */\n  filePattern: string;\n  /** The destination for the output file(s). */\n  destination: OutputFileDestination;\n  /** Additional options for the upload operation, including under what conditions to perform the upload. */\n  uploadOptions: OutputFileUploadConfig;\n}\n\n/** The destination to which a file should be uploaded. */\nexport interface OutputFileDestination {\n  /** A location in Azure blob storage to which files are uploaded. */\n  container?: OutputFileBlobContainerDestination;\n}\n\n/** Specifies a file upload destination within an Azure blob storage container. */\nexport interface OutputFileBlobContainerDestination {\n  /** The destination blob or virtual directory within the Azure Storage container. If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. */\n  path?: string;\n  /** The URL of the container within Azure Blob Storage to which to upload the file(s). If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. */\n  containerUrl: string;\n  /** The reference to the user assigned identity to use to access Azure Blob Storage specified by containerUrl. The identity must have write access to the Azure Blob Storage container. */\n  identityReference?: BatchNodeIdentityReference;\n  /** A list of name-value pairs for headers to be used in uploading output files. These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://docs.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types. */\n  uploadHeaders?: Array<HttpHeader>;\n}\n\n/** An HTTP header name-value pair */\nexport interface HttpHeader {\n  /** The case-insensitive name of the header to be used while uploading output files. */\n  name: string;\n  /** The value of the header to be used while uploading output files. */\n  value?: string;\n}\n\n/**\n * Options for an output file upload operation, including under what conditions\n * to perform the upload.\n */\nexport interface OutputFileUploadConfig {\n  /**\n   * The conditions under which the Task output file or set of files should be uploaded. The default is taskcompletion.\n   *\n   * Possible values: \"tasksuccess\", \"taskfailure\", \"taskcompletion\"\n   */\n  uploadCondition: OutputFileUploadCondition;\n}\n\n/** Execution constraints to apply to a Task. */\nexport interface BatchTaskConstraints {\n  /** The maximum elapsed time that the Task may run, measured from the time the Task starts. If the Task does not complete within the time limit, the Batch service terminates it. If this is not specified, there is no time limit on how long the Task may run. */\n  maxWallClockTime?: string;\n  /** The minimum time to retain the Task directory on the Compute Node where it ran, from the time it completes execution. After this time, the Batch service may delete the Task directory and all its contents. The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. */\n  retentionTime?: string;\n  /** The maximum number of times the Task may be retried. The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). */\n  maxTaskRetryCount?: number;\n}\n\n/**\n * The settings for an authentication token that the Task can use to perform Batch\n * service operations.\n */\nexport interface AuthenticationTokenSettings {\n  /** The Batch resources to which the token grants access. The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. */\n  access?: AccessScope[];\n}\n\n/**\n * A Job Preparation Task to run before any Tasks of the Job on any given Compute Node.\n * You can use Job Preparation to prepare a Node to run Tasks for the Job.\n * Activities commonly performed in Job Preparation include: Downloading common\n * resource files used by all the Tasks in the Job. The Job Preparation Task can\n * download these common resource files to the shared location on the Node.\n * (AZ_BATCH_NODE_ROOT_DIR\\shared), or starting a local service on the Node so\n * that all Tasks of that Job can communicate with it. If the Job Preparation Task\n * fails (that is, exhausts its retry count before exiting with exit code 0),\n * Batch will not run Tasks of this Job on the Node. The Compute Node remains\n * ineligible to run Tasks of this Job until it is reimaged. The Compute Node\n * remains active and can be used for other Jobs. The Job Preparation Task can run\n * multiple times on the same Node. Therefore, you should write the Job\n * Preparation Task to handle re-execution. If the Node is rebooted, the Job\n * Preparation Task is run again on the Compute Node before scheduling any other\n * Task of the Job, if rerunOnNodeRebootAfterSuccess is true or if the Job\n * Preparation Task did not previously complete. If the Node is reimaged, the Job\n * Preparation Task is run again before scheduling any Task of the Job. Batch will\n * retry Tasks when a recovery operation is triggered on a Node. Examples of\n * recovery operations include (but are not limited to) when an unhealthy Node is\n * rebooted or a Compute Node disappeared due to host failure. Retries due to\n * recovery operations are independent of and are not counted against the\n * maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to\n * a recovery operation may occur. Because of this, all Tasks should be\n * idempotent. This means Tasks need to tolerate being interrupted and restarted\n * without causing any corruption or duplicate data. The best practice for long\n * running Tasks is to use some form of checkpointing.\n */\nexport interface BatchJobPreparationTask {\n  /** A string that uniquely identifies the Job Preparation Task within the Job. The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). */\n  id?: string;\n  /** The command line of the Job Preparation Task. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the Job Preparation Task runs. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line. Files listed under this element are located in the Task's working directory.  There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of environment variable settings for the Job Preparation Task. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** Constraints that apply to the Job Preparation Task. */\n  constraints?: BatchTaskConstraints;\n  /** Whether the Batch service should wait for the Job Preparation Task to complete successfully before scheduling any other Tasks of the Job on the Compute Node. A Job Preparation Task has completed successfully if it exits with exit code 0. If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. */\n  waitForSuccess?: boolean;\n  /** The user identity under which the Job Preparation Task runs. If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. */\n  userIdentity?: UserIdentity;\n  /** Whether the Batch service should rerun the Job Preparation Task after a Compute Node reboots. The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. */\n  rerunOnNodeRebootAfterSuccess?: boolean;\n}\n\n/**\n * A Job Release Task to run on Job completion on any Compute Node where the Job has run.\n * The Job Release Task runs when the Job ends, because of one of the following:\n * The user calls the Terminate Job API, or the Delete Job API while the Job is\n * still active, the Job's maximum wall clock time constraint is reached, and the\n * Job is still active, or the Job's Job Manager Task completed, and the Job is\n * configured to terminate when the Job Manager completes. The Job Release Task\n * runs on each Node where Tasks of the Job have run and the Job Preparation Task\n * ran and completed. If you reimage a Node after it has run the Job Preparation\n * Task, and the Job ends without any further Tasks of the Job running on that\n * Node (and hence the Job Preparation Task does not re-run), then the Job Release\n * Task does not run on that Compute Node. If a Node reboots while the Job Release\n * Task is still running, the Job Release Task runs again when the Compute Node\n * starts up. The Job is not marked as complete until all Job Release Tasks have\n * completed. The Job Release Task runs in the background. It does not occupy a\n * scheduling slot; that is, it does not count towards the taskSlotsPerNode limit\n * specified on the Pool.\n */\nexport interface BatchJobReleaseTask {\n  /** A string that uniquely identifies the Job Release Task within the Job. The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). */\n  id?: string;\n  /** The command line of the Job Release Task. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the Job Release Task runs. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line.  There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. Files listed under this element are located in the Task's working directory. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of environment variable settings for the Job Release Task. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** The maximum elapsed time that the Job Release Task may run on a given Compute Node, measured from the time the Task starts. If the Task does not complete within the time limit, the Batch service terminates it. The default value is 15 minutes. You may not specify a timeout longer than 15 minutes. If you do, the Batch service rejects it with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  maxWallClockTime?: string;\n  /** The minimum time to retain the Task directory for the Job Release Task on the Compute Node. After this time, the Batch service may delete the Task directory and all its contents. The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. */\n  retentionTime?: string;\n  /** The user identity under which the Job Release Task runs. If omitted, the Task runs as a non-administrative user unique to the Task. */\n  userIdentity?: UserIdentity;\n}\n\n/** Specifies how a Job should be assigned to a Pool. */\nexport interface BatchPoolInfo {\n  /** The ID of an existing Pool. All the Tasks of the Job will run on the specified Pool. You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. */\n  poolId?: string;\n  /** Characteristics for a temporary 'auto pool'. The Batch service will create this auto Pool when the Job is submitted. If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. */\n  autoPoolSpecification?: BatchAutoPoolSpecification;\n}\n\n/**\n * Specifies characteristics for a temporary 'auto pool'. The Batch service will\n * create this auto Pool when the Job is submitted.\n */\nexport interface BatchAutoPoolSpecification {\n  /** A prefix to be added to the unique identifier when a Pool is automatically created. The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. */\n  autoPoolIdPrefix?: string;\n  /**\n   * The minimum lifetime of created auto Pools, and how multiple Jobs on a schedule are assigned to Pools.\n   *\n   * Possible values: \"jobschedule\", \"job\"\n   */\n  poolLifetimeOption: BatchPoolLifetimeOption;\n  /** Whether to keep an auto Pool alive after its lifetime expires. If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. */\n  keepAlive?: boolean;\n  /** The Pool specification for the auto Pool. */\n  pool?: BatchPoolSpecification;\n}\n\n/** Specification for creating a new Pool. */\nexport interface BatchPoolSpecification {\n  /** The display name for the Pool. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** The size of the virtual machines in the Pool. All virtual machines in a Pool are the same size. For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://docs.microsoft.com/azure/batch/batch-pool-vm-sizes). */\n  vmSize: string;\n  /** The virtual machine configuration for the Pool. This property must be specified. */\n  virtualMachineConfiguration?: VirtualMachineConfiguration;\n  /** The number of task slots that can be used to run concurrent tasks on a single compute node in the pool. The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. */\n  taskSlotsPerNode?: number;\n  /** How Tasks are distributed across Compute Nodes in a Pool. If not specified, the default is spread. */\n  taskSchedulingPolicy?: BatchTaskSchedulingPolicy;\n  /** The timeout for allocation of Compute Nodes to the Pool. This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  resizeTimeout?: string;\n  /** The user-specified tags associated with the pool.The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. */\n  resourceTags?: string;\n  /** The desired number of dedicated Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. */\n  targetDedicatedNodes?: number;\n  /** The desired number of Spot/Low-priority Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. */\n  targetLowPriorityNodes?: number;\n  /** Whether the Pool size should automatically adjust over time. If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. */\n  enableAutoScale?: boolean;\n  /** The formula for the desired number of Compute Nodes in the Pool. This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. */\n  autoScaleFormula?: string;\n  /** The time interval at which to automatically adjust the Pool size according to the autoscale formula. The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  autoScaleEvaluationInterval?: string;\n  /** Whether the Pool permits direct communication between Compute Nodes. Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. */\n  enableInterNodeCommunication?: boolean;\n  /** The network configuration for the Pool. */\n  networkConfiguration?: NetworkConfiguration;\n  /** A Task to run on each Compute Node as it joins the Pool. The Task runs when the Compute Node is added to the Pool or when the Compute Node is restarted. */\n  startTask?: BatchStartTask;\n  /** The list of Packages to be installed on each Compute Node in the Pool. When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** The list of user Accounts to be created on each Compute Node in the Pool. */\n  userAccounts?: Array<UserAccount>;\n  /** A list of name-value pairs associated with the Pool as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n  /** A list of file systems to mount on each node in the pool. This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. */\n  mountConfiguration?: Array<MountConfiguration>;\n  /**\n   * The desired node communication mode for the pool. If omitted, the default value is Default.\n   *\n   * Possible values: \"default\", \"classic\", \"simplified\"\n   */\n  targetNodeCommunicationMode?: BatchNodeCommunicationMode;\n  /** The upgrade policy for the Pool. Describes an upgrade policy - automatic, manual, or rolling. */\n  upgradePolicy?: UpgradePolicy;\n}\n\n/** The network configuration for the Job. */\nexport interface BatchJobNetworkConfiguration {\n  /** The ARM resource identifier of the virtual network subnet which Compute Nodes running Tasks from the Job will join for the duration of the Task. The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://docs.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */\n  subnetId: string;\n  /** Whether to withdraw Compute Nodes from the virtual network to DNC when the job is terminated or deleted.  If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. */\n  skipWithdrawFromVNet: boolean;\n}\n\n/** Contains information about the execution of a Job in the Azure Batch service. */\nexport interface BatchJobExecutionInfo {\n  /** The start time of the Job. This is the time at which the Job was created. */\n  startTime: Date | string;\n  /** The completion time of the Job. This property is set only if the Job is in the completed state. */\n  endTime?: Date | string;\n  /** The ID of the Pool to which this Job is assigned. This element contains the actual Pool where the Job is assigned. When you get Job details from the service, they also contain a poolInfo element, which contains the Pool configuration data from when the Job was added or updated. That poolInfo element may also contain a poolId element. If it does, the two IDs are the same. If it does not, it means the Job ran on an auto Pool, and this property contains the ID of that auto Pool. */\n  poolId?: string;\n  /** Details of any error encountered by the service in starting the Job. This property is not set if there was no error starting the Job. */\n  schedulingError?: BatchJobSchedulingError;\n  /** A string describing the reason the Job ended. This property is set only if the Job is in the completed state. If the Batch service terminates the Job, it sets the reason as follows: JMComplete - the Job Manager Task completed, and killJobOnCompletion was set to true. MaxWallClockTimeExpiry - the Job reached its maxWallClockTime constraint. TerminateJobSchedule - the Job ran as part of a schedule, and the schedule terminated. AllTasksComplete - the Job's onAllTasksComplete attribute is set to terminatejob, and all Tasks in the Job are complete. TaskFailed - the Job's onTaskFailure attribute is set to performExitOptionsJobAction, and a Task in the Job failed with an exit condition that specified a jobAction of terminatejob. Any other string is a user-defined reason specified in a call to the 'Terminate a Job' operation. */\n  terminateReason?: string;\n}\n\n/** An error encountered by the Batch service when scheduling a Job. */\nexport interface BatchJobSchedulingError {\n  /**\n   * The category of the Job scheduling error.\n   *\n   * Possible values: \"usererror\", \"servererror\"\n   */\n  category: ErrorCategory;\n  /** An identifier for the Job scheduling error. Codes are invariant and are intended to be consumed programmatically. */\n  code?: string;\n  /** A message describing the Job scheduling error, intended to be suitable for display in a user interface. */\n  message?: string;\n  /** A list of additional error details related to the scheduling error. */\n  details?: Array<NameValuePair>;\n}\n\n/** Resource usage statistics for a Job. */\nexport interface BatchJobStatistics {\n  /** The URL of the statistics. */\n  url: string;\n  /** The start time of the time range covered by the statistics. */\n  startTime: Date | string;\n  /** The time at which the statistics were last updated. All statistics are limited to the range between startTime and lastUpdateTime. */\n  lastUpdateTime: Date | string;\n  /** The total user mode CPU time (summed across all cores and all Compute Nodes) consumed by all Tasks in the Job. */\n  userCPUTime: string;\n  /** The total kernel mode CPU time (summed across all cores and all Compute Nodes) consumed by all Tasks in the Job. */\n  kernelCPUTime: string;\n  /** The total wall clock time of all Tasks in the Job.  The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If a Task was retried, this includes the wall clock time of all the Task retries. */\n  wallClockTime: string;\n  /** The total number of disk read operations made by all Tasks in the Job. */\n  readIOps: number;\n  /** The total number of disk write operations made by all Tasks in the Job. */\n  writeIOps: number;\n  /** The total amount of data in GiB read from disk by all Tasks in the Job. */\n  readIOGiB: number;\n  /** The total amount of data in GiB written to disk by all Tasks in the Job. */\n  writeIOGiB: number;\n  /** The total number of Tasks successfully completed in the Job during the given time range. A Task completes successfully if it returns exit code 0. */\n  numSucceededTasks: number;\n  /** The total number of Tasks in the Job that failed during the given time range. A Task fails if it exhausts its maximum retry count without returning exit code 0. */\n  numFailedTasks: number;\n  /** The total number of retries on all the Tasks in the Job during the given time range. */\n  numTaskRetries: number;\n  /** The total wait time of all Tasks in the Job. The wait time for a Task is defined as the elapsed time between the creation of the Task and the start of Task execution. (If the Task is retried due to failures, the wait time is the time to the most recent Task execution.) This value is only reported in the Account lifetime statistics; it is not included in the Job statistics. */\n  waitTime: string;\n}\n\n/** Parameters for updating an Azure Batch Job. */\nexport interface BatchJobUpdateContent {\n  /** The priority of the Job. Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. If omitted, the priority of the Job is left unchanged. */\n  priority?: number;\n  /** Whether Tasks in this job can be preempted by other high priority jobs. If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. */\n  allowTaskPreemption?: boolean;\n  /** The maximum number of tasks that can be executed in parallel for the job. The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. */\n  maxParallelTasks?: number;\n  /** The execution constraints for the Job. If omitted, the existing execution constraints are left unchanged. */\n  constraints?: BatchJobConstraints;\n  /** The Pool on which the Batch service runs the Job's Tasks. You may change the Pool for a Job only when the Job is disabled. The Patch Job call will fail if you include the poolInfo element and the Job is not disabled. If you specify an autoPoolSpecification in the poolInfo, only the keepAlive property of the autoPoolSpecification can be updated, and then only if the autoPoolSpecification has a poolLifetimeOption of Job (other job properties can be updated as normal). If omitted, the Job continues to run on its current Pool. */\n  poolInfo?: BatchPoolInfo;\n  /**\n   * The action the Batch service should take when all Tasks in the Job are in the completed state. If omitted, the completion behavior is left unchanged. You may not change the value from terminatejob to noaction - that is, once you have engaged automatic Job termination, you cannot turn it off again. If you try to do this, the request fails with an 'invalid property value' error response; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).\n   *\n   * Possible values: \"noaction\", \"terminatejob\"\n   */\n  onAllTasksComplete?: OnAllBatchTasksComplete;\n  /** A list of name-value pairs associated with the Job as metadata. If omitted, the existing Job metadata is left unchanged. */\n  metadata?: Array<MetadataItem>;\n  /** The network configuration for the Job. */\n  networkConfiguration?: BatchJobNetworkConfiguration;\n}\n\n/** Parameters for disabling an Azure Batch Job. */\nexport interface BatchJobDisableContent {\n  /**\n   * What to do with active Tasks associated with the Job.\n   *\n   * Possible values: \"requeue\", \"terminate\", \"wait\"\n   */\n  disableTasks: DisableBatchJobOption;\n}\n\n/** Parameters for terminating an Azure Batch Job. */\nexport interface BatchJobTerminateContent {\n  /** The text you want to appear as the Job's TerminationReason. The default is 'UserTerminate'. */\n  terminateReason?: string;\n}\n\n/** Parameters for creating an Azure Batch Job. */\nexport interface BatchJobCreateContent {\n  /** A string that uniquely identifies the Job within the Account. The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within an Account that differ only by case). */\n  id: string;\n  /** The display name for the Job. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** Whether Tasks in the Job can define dependencies on each other. The default is false. */\n  usesTaskDependencies?: boolean;\n  /** The priority of the Job. Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. */\n  priority?: number;\n  /** Whether Tasks in this job can be preempted by other high priority jobs. If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. */\n  allowTaskPreemption?: boolean;\n  /** The maximum number of tasks that can be executed in parallel for the job. The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. */\n  maxParallelTasks?: number;\n  /** The execution constraints for the Job. */\n  constraints?: BatchJobConstraints;\n  /** Details of a Job Manager Task to be launched when the Job is started. If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. The Job Manager Task's typical purpose is to control and/or monitor Job execution, for example by deciding what additional Tasks to run, determining when the work is complete, etc. (However, a Job Manager Task is not restricted to these activities - it is a fully-fledged Task in the system and perform whatever actions are required for the Job.) For example, a Job Manager Task might download a file specified as a parameter, analyze the contents of that file and submit additional Tasks based on those contents. */\n  jobManagerTask?: BatchJobManagerTask;\n  /** The Job Preparation Task. If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. */\n  jobPreparationTask?: BatchJobPreparationTask;\n  /** The Job Release Task. A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Nodes that have run the Job Preparation Task. The primary purpose of the Job Release Task is to undo changes to Compute Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. */\n  jobReleaseTask?: BatchJobReleaseTask;\n  /** The list of common environment variable settings. These environment variables are set for all Tasks in the Job (including the Job Manager, Job Preparation and Job Release Tasks). Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. */\n  commonEnvironmentSettings?: Array<EnvironmentSetting>;\n  /** The Pool on which the Batch service runs the Job's Tasks. */\n  poolInfo: BatchPoolInfo;\n  /**\n   * The action the Batch service should take when all Tasks in the Job are in the completed state. Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction.\n   *\n   * Possible values: \"noaction\", \"terminatejob\"\n   */\n  onAllTasksComplete?: OnAllBatchTasksComplete;\n  /**\n   * The action the Batch service should take when any Task in the Job fails. A Task is considered to have failed if has a failureInfo. A failureInfo is set if the Task completes with a non-zero exit code after exhausting its retry count, or if there was an error starting the Task, for example due to a resource file download error. The default is noaction.\n   *\n   * Possible values: \"noaction\", \"performexitoptionsjobaction\"\n   */\n  onTaskFailure?: OnBatchTaskFailure;\n  /** The network configuration for the Job. */\n  networkConfiguration?: BatchJobNetworkConfiguration;\n  /** A list of name-value pairs associated with the Job as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/** Contains information about the container which a Task is executing. */\nexport interface BatchTaskContainerExecutionInfo {\n  /** The ID of the container. */\n  containerId?: string;\n  /** The state of the container. This is the state of the container according to the Docker service. It is equivalent to the status field returned by \"docker inspect\". */\n  state?: string;\n  /** Detailed error information about the container. This is the detailed error string from the Docker service, if available. It is equivalent to the error field returned by \"docker inspect\". */\n  error?: string;\n}\n\n/** Information about a Task failure. */\nexport interface BatchTaskFailureInfo {\n  /**\n   * The category of the Task error.\n   *\n   * Possible values: \"usererror\", \"servererror\"\n   */\n  category: ErrorCategory;\n  /** An identifier for the Task error. Codes are invariant and are intended to be consumed programmatically. */\n  code?: string;\n  /** A message describing the Task error, intended to be suitable for display in a user interface. */\n  message?: string;\n  /** A list of additional details related to the error. */\n  details?: Array<NameValuePair>;\n}\n\n/**\n * A Job Schedule that allows recurring Jobs by specifying when to run Jobs and a\n * specification used to create each Job.\n */\nexport interface BatchJobSchedule {\n  /** The schedule according to which Jobs will be created. All times are fixed respective to UTC and are not impacted by daylight saving time. */\n  schedule?: BatchJobScheduleConfiguration;\n  /** The details of the Jobs to be created on this schedule. */\n  jobSpecification: BatchJobSpecification;\n  /** A list of name-value pairs associated with the schedule as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/**\n * The schedule according to which Jobs will be created. All times are fixed\n * respective to UTC and are not impacted by daylight saving time.\n */\nexport interface BatchJobScheduleConfiguration {\n  /** The earliest time at which any Job may be created under this Job Schedule. If you do not specify a doNotRunUntil time, the schedule becomes ready to create Jobs immediately. */\n  doNotRunUntil?: Date | string;\n  /** A time after which no Job will be created under this Job Schedule. The schedule will move to the completed state as soon as this deadline is past and there is no active Job under this Job Schedule. If you do not specify a doNotRunAfter time, and you are creating a recurring Job Schedule, the Job Schedule will remain active until you explicitly terminate it. */\n  doNotRunAfter?: Date | string;\n  /** The time interval, starting from the time at which the schedule indicates a Job should be created, within which a Job must be created. If a Job is not created within the startWindow interval, then the 'opportunity' is lost; no Job will be created until the next recurrence of the schedule. If the schedule is recurring, and the startWindow is longer than the recurrence interval, then this is equivalent to an infinite startWindow, because the Job that is 'due' in one recurrenceInterval is not carried forward into the next recurrence interval. The default is infinite. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  startWindow?: string;\n  /** The time interval between the start times of two successive Jobs under the Job Schedule. A Job Schedule can have at most one active Job under it at any given time. Because a Job Schedule can have at most one active Job under it at any given time, if it is time to create a new Job under a Job Schedule, but the previous Job is still running, the Batch service will not create the new Job until the previous Job finishes. If the previous Job does not finish within the startWindow period of the new recurrenceInterval, then no new Job will be scheduled for that interval. For recurring Jobs, you should normally specify a jobManagerTask in the jobSpecification. If you do not use jobManagerTask, you will need an external process to monitor when Jobs are created, add Tasks to the Jobs and terminate the Jobs ready for the next recurrence. The default is that the schedule does not recur: one Job is created, within the startWindow after the doNotRunUntil time, and the schedule is complete as soon as that Job finishes. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  recurrenceInterval?: string;\n}\n\n/** Specifies details of the Jobs to be created on a schedule. */\nexport interface BatchJobSpecification {\n  /** The priority of Jobs created under this schedule. Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. This priority is used as the default for all Jobs under the Job Schedule. You can update a Job's priority after it has been created using by using the update Job API. */\n  priority?: number;\n  /** Whether Tasks in this job can be preempted by other high priority jobs. If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. */\n  allowTaskPreemption?: boolean;\n  /** The maximum number of tasks that can be executed in parallel for the job. The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. */\n  maxParallelTasks?: number;\n  /** The display name for Jobs created under this schedule. The name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** Whether Tasks in the Job can define dependencies on each other. The default is false. */\n  usesTaskDependencies?: boolean;\n  /**\n   * The action the Batch service should take when all Tasks in a Job created under this schedule are in the completed state. Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction.\n   *\n   * Possible values: \"noaction\", \"terminatejob\"\n   */\n  onAllTasksComplete?: OnAllBatchTasksComplete;\n  /**\n   * The action the Batch service should take when any Task fails in a Job created under this schedule. A Task is considered to have failed if it have failed if has a failureInfo. A failureInfo is set if the Task completes with a non-zero exit code after exhausting its retry count, or if there was an error starting the Task, for example due to a resource file download error. The default is noaction.\n   *\n   * Possible values: \"noaction\", \"performexitoptionsjobaction\"\n   */\n  onTaskFailure?: OnBatchTaskFailure;\n  /** The network configuration for the Job. */\n  networkConfiguration?: BatchJobNetworkConfiguration;\n  /** The execution constraints for Jobs created under this schedule. */\n  constraints?: BatchJobConstraints;\n  /** The details of a Job Manager Task to be launched when a Job is started under this schedule. If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job using the Task API. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. */\n  jobManagerTask?: BatchJobManagerTask;\n  /** The Job Preparation Task for Jobs created under this schedule. If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. */\n  jobPreparationTask?: BatchJobPreparationTask;\n  /** The Job Release Task for Jobs created under this schedule. The primary purpose of the Job Release Task is to undo changes to Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Compute Nodes that have run the Job Preparation Task. */\n  jobReleaseTask?: BatchJobReleaseTask;\n  /** A list of common environment variable settings. These environment variables are set for all Tasks in Jobs created under this schedule (including the Job Manager, Job Preparation and Job Release Tasks). Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. */\n  commonEnvironmentSettings?: Array<EnvironmentSetting>;\n  /** The Pool on which the Batch service runs the Tasks of Jobs created under this schedule. */\n  poolInfo: BatchPoolInfo;\n  /** A list of name-value pairs associated with each Job created under this schedule as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/**\n * Contains information about Jobs that have been and will be run under a Job\n * Schedule.\n */\nexport interface BatchJobScheduleExecutionInfo {\n  /** The next time at which a Job will be created under this schedule. This property is meaningful only if the schedule is in the active state when the time comes around. For example, if the schedule is disabled, no Job will be created at nextRunTime unless the Job is enabled before then. */\n  nextRunTime?: Date | string;\n  /** Information about the most recent Job under the Job Schedule. This property is present only if the at least one Job has run under the schedule. */\n  recentJob?: RecentBatchJob;\n  /** The time at which the schedule ended. This property is set only if the Job Schedule is in the completed state. */\n  endTime?: Date | string;\n}\n\n/** Information about the most recent Job to run under the Job Schedule. */\nexport interface RecentBatchJob {\n  /** The ID of the Job. */\n  id?: string;\n  /** The URL of the Job. */\n  url?: string;\n}\n\n/** Resource usage statistics for a Job Schedule. */\nexport interface BatchJobScheduleStatistics {\n  /** The URL of the statistics. */\n  url: string;\n  /** The start time of the time range covered by the statistics. */\n  startTime: Date | string;\n  /** The time at which the statistics were last updated. All statistics are limited to the range between startTime and lastUpdateTime. */\n  lastUpdateTime: Date | string;\n  /** The total user mode CPU time (summed across all cores and all Compute Nodes) consumed by all Tasks in all Jobs created under the schedule. */\n  userCPUTime: string;\n  /** The total kernel mode CPU time (summed across all cores and all Compute Nodes) consumed by all Tasks in all Jobs created under the schedule. */\n  kernelCPUTime: string;\n  /** The total wall clock time of all the Tasks in all the Jobs created under the schedule. The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If a Task was retried, this includes the wall clock time of all the Task retries. */\n  wallClockTime: string;\n  /** The total number of disk read operations made by all Tasks in all Jobs created under the schedule. */\n  readIOps: number;\n  /** The total number of disk write operations made by all Tasks in all Jobs created under the schedule. */\n  writeIOps: number;\n  /** The total gibibytes read from disk by all Tasks in all Jobs created under the schedule. */\n  readIOGiB: number;\n  /** The total gibibytes written to disk by all Tasks in all Jobs created under the schedule. */\n  writeIOGiB: number;\n  /** The total number of Tasks successfully completed during the given time range in Jobs created under the schedule. A Task completes successfully if it returns exit code 0. */\n  numSucceededTasks: number;\n  /** The total number of Tasks that failed during the given time range in Jobs created under the schedule. A Task fails if it exhausts its maximum retry count without returning exit code 0. */\n  numFailedTasks: number;\n  /** The total number of retries during the given time range on all Tasks in all Jobs created under the schedule. */\n  numTaskRetries: number;\n  /** The total wait time of all Tasks in all Jobs created under the schedule. The wait time for a Task is defined as the elapsed time between the creation of the Task and the start of Task execution. (If the Task is retried due to failures, the wait time is the time to the most recent Task execution.). This value is only reported in the Account lifetime statistics; it is not included in the Job statistics. */\n  waitTime: string;\n}\n\n/** Parameters for updating an Azure Batch Job Schedule. */\nexport interface BatchJobScheduleUpdateContent {\n  /** The schedule according to which Jobs will be created. All times are fixed respective to UTC and are not impacted by daylight saving time. If you do not specify this element, the existing schedule is left unchanged. */\n  schedule?: BatchJobScheduleConfiguration;\n  /** The details of the Jobs to be created on this schedule. Updates affect only Jobs that are started after the update has taken place. Any currently active Job continues with the older specification. */\n  jobSpecification?: BatchJobSpecification;\n  /** A list of name-value pairs associated with the Job Schedule as metadata. If you do not specify this element, existing metadata is left unchanged. */\n  metadata?: Array<MetadataItem>;\n}\n\n/** Parameters for creating an Azure Batch Job Schedule */\nexport interface BatchJobScheduleCreateContent {\n  /** A string that uniquely identifies the schedule within the Account. The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within an Account that differ only by case). */\n  id: string;\n  /** The display name for the schedule. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** The schedule according to which Jobs will be created. All times are fixed respective to UTC and are not impacted by daylight saving time. */\n  schedule: BatchJobScheduleConfiguration;\n  /** The details of the Jobs to be created on this schedule. */\n  jobSpecification: BatchJobSpecification;\n  /** A list of name-value pairs associated with the schedule as metadata. The Batch service does not assign any meaning to metadata; it is solely for the use of user code. */\n  metadata?: Array<MetadataItem>;\n}\n\n/** Parameters for creating an Azure Batch Task. */\nexport interface BatchTaskCreateContent {\n  /** A string that uniquely identifies the Task within the Job. The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within a Job that differ only by case). */\n  id: string;\n  /** A display name for the Task. The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. */\n  displayName?: string;\n  /** How the Batch service should respond when the Task completes. */\n  exitConditions?: ExitConditions;\n  /** The command line of the Task. For multi-instance Tasks, the command line is executed as the primary Task, after the primary Task and all subtasks have finished executing the coordination command line. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using \"cmd /c MyCommand\" in Windows or \"/bin/sh -c MyCommand\" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */\n  commandLine: string;\n  /** The settings for the container under which the Task runs. If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. */\n  containerSettings?: BatchTaskContainerSettings;\n  /** A list of files that the Batch service will download to the Compute Node before running the command line. For multi-instance Tasks, the resource files will only be downloaded to the Compute Node on which the primary Task is executed. There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. */\n  resourceFiles?: Array<ResourceFile>;\n  /** A list of files that the Batch service will upload from the Compute Node after running the command line. For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. */\n  outputFiles?: Array<OutputFile>;\n  /** A list of environment variable settings for the Task. */\n  environmentSettings?: Array<EnvironmentSetting>;\n  /** A locality hint that can be used by the Batch service to select a Compute Node on which to start the new Task. */\n  affinityInfo?: AffinityInfo;\n  /** The execution constraints that apply to this Task. If you do not specify constraints, the maxTaskRetryCount is the maxTaskRetryCount specified for the Job, the maxWallClockTime is infinite, and the retentionTime is 7 days. */\n  constraints?: BatchTaskConstraints;\n  /** The number of scheduling slots that the Task required to run. The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this must be 1. */\n  requiredSlots?: number;\n  /** The user identity under which the Task runs. If omitted, the Task runs as a non-administrative user unique to the Task. */\n  userIdentity?: UserIdentity;\n  /** An object that indicates that the Task is a multi-instance Task, and contains information about how to run the multi-instance Task. */\n  multiInstanceSettings?: MultiInstanceSettings;\n  /** The Tasks that this Task depends on. This Task will not be scheduled until all Tasks that it depends on have completed successfully. If any of those Tasks fail and exhaust their retry counts, this Task will never be scheduled. If the Job does not have usesTaskDependencies set to true, and this element is present, the request fails with error code TaskDependenciesNotSpecifiedOnJob. */\n  dependsOn?: BatchTaskDependencies;\n  /** A list of Packages that the Batch service will deploy to the Compute Node before running the command line. Application packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced package is already on the Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. */\n  applicationPackageReferences?: Array<BatchApplicationPackageReference>;\n  /** The settings for an authentication token that the Task can use to perform Batch service operations. If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job. */\n  authenticationTokenSettings?: AuthenticationTokenSettings;\n}\n\n/** Specifies how the Batch service should respond when the Task completes. */\nexport interface ExitConditions {\n  /** A list of individual Task exit codes and how the Batch service should respond to them. */\n  exitCodes?: Array<ExitCodeMapping>;\n  /** A list of Task exit code ranges and how the Batch service should respond to them. */\n  exitCodeRanges?: Array<ExitCodeRangeMapping>;\n  /** How the Batch service should respond if the Task fails to start due to an error. */\n  preProcessingError?: ExitOptions;\n  /** How the Batch service should respond if a file upload error occurs. If the Task exited with an exit code that was specified via exitCodes or exitCodeRanges, and then encountered a file upload error, then the action specified by the exit code takes precedence. */\n  fileUploadError?: ExitOptions;\n  /** How the Batch service should respond if the Task fails with an exit condition not covered by any of the other properties. This value is used if the Task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection. */\n  default?: ExitOptions;\n}\n\n/**\n * How the Batch service should respond if a Task exits with a particular exit\n * code.\n */\nexport interface ExitCodeMapping {\n  /** A process exit code. */\n  code: number;\n  /** How the Batch service should respond if the Task exits with this exit code. */\n  exitOptions: ExitOptions;\n}\n\n/** Specifies how the Batch service responds to a particular exit condition. */\nexport interface ExitOptions {\n  /**\n   * An action to take on the Job containing the Task, if the Task completes with the given exit condition and the Job's onTaskFailed property is 'performExitOptionsJobAction'. The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request).\n   *\n   * Possible values: \"none\", \"disable\", \"terminate\"\n   */\n  jobAction?: BatchJobAction;\n  /**\n   * An action that the Batch service performs on Tasks that depend on this Task. Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks.\n   *\n   * Possible values: \"satisfy\", \"block\"\n   */\n  dependencyAction?: DependencyAction;\n}\n\n/**\n * A range of exit codes and how the Batch service should respond to exit codes\n * within that range.\n */\nexport interface ExitCodeRangeMapping {\n  /** The first exit code in the range. */\n  start: number;\n  /** The last exit code in the range. */\n  end: number;\n  /** How the Batch service should respond if the Task exits with an exit code in the range start to end (inclusive). */\n  exitOptions: ExitOptions;\n}\n\n/**\n * A locality hint that can be used by the Batch service to select a Compute Node\n * on which to start a Task.\n */\nexport interface AffinityInfo {\n  /** An opaque string representing the location of a Compute Node or a Task that has run previously. You can pass the affinityId of a Node to indicate that this Task needs to run on that Compute Node. Note that this is just a soft affinity. If the target Compute Node is busy or unavailable at the time the Task is scheduled, then the Task will be scheduled elsewhere. */\n  affinityId: string;\n}\n\n/**\n * Multi-instance Tasks are commonly used to support MPI Tasks. In the MPI case,\n * if any of the subtasks fail (for example due to exiting with a non-zero exit\n * code) the entire multi-instance Task fails. The multi-instance Task is then\n * terminated and retried, up to its retry limit.\n */\nexport interface MultiInstanceSettings {\n  /** The number of Compute Nodes required by the Task. If omitted, the default is 1. */\n  numberOfInstances?: number;\n  /** The command line to run on all the Compute Nodes to enable them to coordinate when the primary runs the main Task command. A typical coordination command line launches a background service and verifies that the service is ready to process inter-node messages. */\n  coordinationCommandLine: string;\n  /** A list of files that the Batch service will download before running the coordination command line. The difference between common resource files and Task resource files is that common resource files are downloaded for all subtasks including the primary, whereas Task resource files are downloaded only for the primary. Also note that these resource files are not downloaded to the Task working directory, but instead are downloaded to the Task root directory (one directory above the working directory).  There is a maximum size for the list of resource files.  When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. */\n  commonResourceFiles?: Array<ResourceFile>;\n}\n\n/**\n * Specifies any dependencies of a Task. Any Task that is explicitly specified or\n * within a dependency range must complete before the dependant Task will be\n * scheduled.\n */\nexport interface BatchTaskDependencies {\n  /** The list of Task IDs that this Task depends on. All Tasks in this list must complete successfully before the dependent Task can be scheduled. The taskIds collection is limited to 64000 characters total (i.e. the combined length of all Task IDs). If the taskIds collection exceeds the maximum length, the Add Task request fails with error code TaskDependencyListTooLong. In this case consider using Task ID ranges instead. */\n  taskIds?: string[];\n  /** The list of Task ID ranges that this Task depends on. All Tasks in all ranges must complete successfully before the dependent Task can be scheduled. */\n  taskIdRanges?: Array<BatchTaskIdRange>;\n}\n\n/**\n * The start and end of the range are inclusive. For example, if a range has start\n * 9 and end 12, then it represents Tasks '9', '10', '11' and '12'.\n */\nexport interface BatchTaskIdRange {\n  /** The first Task ID in the range. */\n  start: number;\n  /** The last Task ID in the range. */\n  end: number;\n}\n\n/**\n * Batch will retry Tasks when a recovery operation is triggered on a Node.\n * Examples of recovery operations include (but are not limited to) when an\n * unhealthy Node is rebooted or a Compute Node disappeared due to host failure.\n * Retries due to recovery operations are independent of and are not counted\n * against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal\n * retry due to a recovery operation may occur. Because of this, all Tasks should\n * be idempotent. This means Tasks need to tolerate being interrupted and\n * restarted without causing any corruption or duplicate data. The best practice\n * for long running Tasks is to use some form of checkpointing.\n */\nexport interface BatchTask {\n  /** The execution constraints that apply to this Task. */\n  constraints?: BatchTaskConstraints;\n}\n\n/** Information about the execution of a Task. */\nexport interface BatchTaskExecutionInfo {\n  /** The time at which the Task started running. 'Running' corresponds to the running state, so if the Task specifies resource files or Packages, then the start time reflects the time at which the Task started downloading or deploying these. If the Task has been restarted or retried, this is the most recent time at which the Task started running. This property is present only for Tasks that are in the running or completed state. */\n  startTime?: Date | string;\n  /** The time at which the Task completed. This property is set only if the Task is in the Completed state. */\n  endTime?: Date | string;\n  /** The exit code of the program specified on the Task command line. This property is set only if the Task is in the completed state. In general, the exit code for a process reflects the specific convention implemented by the application developer for that process. If you use the exit code value to make decisions in your code, be sure that you know the exit code convention used by the application process. However, if the Batch service terminates the Task (due to timeout, or user termination via the API) you may see an operating system-defined exit code. */\n  exitCode?: number;\n  /** Information about the container under which the Task is executing. This property is set only if the Task runs in a container context. */\n  containerInfo?: BatchTaskContainerExecutionInfo;\n  /** Information describing the Task failure, if any. This property is set only if the Task is in the completed state and encountered a failure. */\n  failureInfo?: BatchTaskFailureInfo;\n  /** The number of times the Task has been retried by the Batch service. Task application failures (non-zero exit code) are retried, pre-processing errors (the Task could not be run) and file upload errors are not retried. The Batch service will retry the Task up to the limit specified by the constraints. */\n  retryCount: number;\n  /** The most recent time at which a retry of the Task started running. This element is present only if the Task was retried (i.e. retryCount is nonzero). If present, this is typically the same as startTime, but may be different if the Task has been restarted for reasons other than retry; for example, if the Compute Node was rebooted during a retry, then the startTime is updated but the lastRetryTime is not. */\n  lastRetryTime?: Date | string;\n  /** The number of times the Task has been requeued by the Batch service as the result of a user request. When the user removes Compute Nodes from a Pool (by resizing/shrinking the pool) or when the Job is being disabled, the user can specify that running Tasks on the Compute Nodes be requeued for execution. This count tracks how many times the Task has been requeued for these reasons. */\n  requeueCount: number;\n  /** The most recent time at which the Task has been requeued by the Batch service as the result of a user request. This property is set only if the requeueCount is nonzero. */\n  lastRequeueTime?: Date | string;\n  /**\n   * The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property.\n   *\n   * Possible values: \"success\", \"failure\"\n   */\n  result?: BatchTaskExecutionResult;\n}\n\n/** Information about the Compute Node on which a Task ran. */\nexport interface BatchNodeInfo {\n  /** An identifier for the Node on which the Task ran, which can be passed when adding a Task to request that the Task be scheduled on this Compute Node. */\n  affinityId?: string;\n  /** The URL of the Compute Node on which the Task ran. */\n  nodeUrl?: string;\n  /** The ID of the Pool on which the Task ran. */\n  poolId?: string;\n  /** The ID of the Compute Node on which the Task ran. */\n  nodeId?: string;\n  /** The root directory of the Task on the Compute Node. */\n  taskRootDirectory?: string;\n  /** The URL to the root directory of the Task on the Compute Node. */\n  taskRootDirectoryUrl?: string;\n}\n\n/** Resource usage statistics for a Task. */\nexport interface BatchTaskStatistics {\n  /** The URL of the statistics. */\n  url: string;\n  /** The start time of the time range covered by the statistics. */\n  startTime: Date | string;\n  /** The time at which the statistics were last updated. All statistics are limited to the range between startTime and lastUpdateTime. */\n  lastUpdateTime: Date | string;\n  /** The total user mode CPU time (summed across all cores and all Compute Nodes) consumed by the Task. */\n  userCPUTime: string;\n  /** The total kernel mode CPU time (summed across all cores and all Compute Nodes) consumed by the Task. */\n  kernelCPUTime: string;\n  /** The total wall clock time of the Task. The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If the Task was retried, this includes the wall clock time of all the Task retries. */\n  wallClockTime: string;\n  /** The total number of disk read operations made by the Task. */\n  readIOps: number;\n  /** The total number of disk write operations made by the Task. */\n  writeIOps: number;\n  /** The total gibibytes read from disk by the Task. */\n  readIOGiB: number;\n  /** The total gibibytes written to disk by the Task. */\n  writeIOGiB: number;\n  /** The total wait time of the Task. The wait time for a Task is defined as the elapsed time between the creation of the Task and the start of Task execution. (If the Task is retried due to failures, the wait time is the time to the most recent Task execution.). */\n  waitTime: string;\n}\n\n/** A collection of Azure Batch Tasks to add. */\nexport interface BatchTaskGroup {\n  /** The collection of Tasks to add. The maximum count of Tasks is 100. The total serialized size of this collection must be less than 1MB. If it is greater than 1MB (for example if each Task has 100's of resource files or environment variables), the request will fail with code 'RequestBodyTooLarge' and should be retried again with fewer Tasks. */\n  value: Array<BatchTaskCreateContent>;\n}\n\n/** Parameters for creating a user account for RDP or SSH access on an Azure Batch Compute Node. */\nexport interface BatchNodeUserCreateContent {\n  /** The user name of the Account. */\n  name: string;\n  /** Whether the Account should be an administrator on the Compute Node. The default value is false. */\n  isAdmin?: boolean;\n  /** The time at which the Account should expire. If omitted, the default is 1 day from the current time. For Linux Compute Nodes, the expiryTime has a precision up to a day. */\n  expiryTime?: Date | string;\n  /** The password of the Account. The password is required for Windows Compute Nodes. For Linux Compute Nodes, the password can optionally be specified along with the sshPublicKey property. */\n  password?: string;\n  /** The SSH public key that can be used for remote login to the Compute Node. The public key should be compatible with OpenSSH encoding and should be base 64 encoded. This property can be specified only for Linux Compute Nodes. If this is specified for a Windows Compute Node, then the Batch service rejects the request; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */\n  sshPublicKey?: string;\n}\n\n/** Parameters for updating a user account for RDP or SSH access on an Azure Batch Compute Node. */\nexport interface BatchNodeUserUpdateContent {\n  /** The password of the Account. The password is required for Windows Compute Nodes. For Linux Compute Nodes, the password can optionally be specified along with the sshPublicKey property. If omitted, any existing password is removed. */\n  password?: string;\n  /** The time at which the Account should expire. If omitted, the default is 1 day from the current time. For Linux Compute Nodes, the expiryTime has a precision up to a day. */\n  expiryTime?: Date | string;\n  /** The SSH public key that can be used for remote login to the Compute Node. The public key should be compatible with OpenSSH encoding and should be base 64 encoded. This property can be specified only for Linux Compute Nodes. If this is specified for a Windows Compute Node, then the Batch service rejects the request; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). If omitted, any existing SSH public key is removed. */\n  sshPublicKey?: string;\n}\n\n/** Parameters for rebooting an Azure Batch Compute Node. */\nexport interface BatchNodeRebootContent {\n  /**\n   * When to reboot the Compute Node and what to do with currently running Tasks. The default value is requeue.\n   *\n   * Possible values: \"requeue\", \"terminate\", \"taskcompletion\", \"retaineddata\"\n   */\n  nodeRebootOption?: BatchNodeRebootOption;\n}\n\n/** Options for deallocating a Compute Node. */\nexport interface BatchNodeDeallocateContent {\n  /**\n   * When to deallocate the Compute Node and what to do with currently running Tasks. The default value is requeue.\n   *\n   * Possible values: \"requeue\", \"terminate\", \"taskcompletion\", \"retaineddata\"\n   */\n  nodeDeallocateOption?: BatchNodeDeallocateOption;\n}\n\n/** Parameters for reimaging an Azure Batch Compute Node. */\nexport interface BatchNodeReimageContent {\n  /**\n   * When to reimage the Compute Node and what to do with currently running Tasks. The default value is requeue.\n   *\n   * Possible values: \"requeue\", \"terminate\", \"taskcompletion\", \"retaineddata\"\n   */\n  nodeReimageOption?: BatchNodeReimageOption;\n}\n\n/** Parameters for disabling scheduling on an Azure Batch Compute Node. */\nexport interface BatchNodeDisableSchedulingContent {\n  /**\n   * What to do with currently running Tasks when disabling Task scheduling on the Compute Node. The default value is requeue.\n   *\n   * Possible values: \"requeue\", \"terminate\", \"taskcompletion\"\n   */\n  nodeDisableSchedulingOption?: BatchNodeDisableSchedulingOption;\n}\n\n/** The Azure Batch service log files upload parameters for a Compute Node. */\nexport interface UploadBatchServiceLogsContent {\n  /** The URL of the container within Azure Blob Storage to which to upload the Batch Service log file(s). If a user assigned managed identity is not being used, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. The SAS duration must allow enough time for the upload to finish. The start time for SAS is optional and recommended to not be specified. */\n  containerUrl: string;\n  /** The start of the time range from which to upload Batch Service log file(s). Any log file containing a log message in the time range will be uploaded. This means that the operation might retrieve more logs than have been requested since the entire log file is always uploaded, but the operation should not retrieve fewer logs than have been requested. */\n  startTime: Date | string;\n  /** The end of the time range from which to upload Batch Service log file(s). Any log file containing a log message in the time range will be uploaded. This means that the operation might retrieve more logs than have been requested since the entire log file is always uploaded, but the operation should not retrieve fewer logs than have been requested. If omitted, the default is to upload all logs available after the startTime. */\n  endTime?: Date | string;\n  /** The reference to the user assigned identity to use to access Azure Blob Storage specified by containerUrl. The identity must have write access to the Azure Blob Storage container. */\n  identityReference?: BatchNodeIdentityReference;\n}\n\n/** Alias for CachingType */\nexport type CachingType = string;\n/** Alias for StorageAccountType */\nexport type StorageAccountType = string;\n/** Alias for ContainerType */\nexport type ContainerType = string;\n/** Alias for DiskEncryptionTarget */\nexport type DiskEncryptionTarget = string;\n/** Alias for BatchNodePlacementPolicyType */\nexport type BatchNodePlacementPolicyType = string;\n/** Alias for DiffDiskPlacement */\nexport type DiffDiskPlacement = string;\n/** Alias for SecurityEncryptionTypes */\nexport type SecurityEncryptionTypes = string;\n/** Alias for SecurityTypes */\nexport type SecurityTypes = string;\n/** Alias for DynamicVNetAssignmentScope */\nexport type DynamicVNetAssignmentScope = string;\n/** Alias for InboundEndpointProtocol */\nexport type InboundEndpointProtocol = string;\n/** Alias for NetworkSecurityGroupRuleAccess */\nexport type NetworkSecurityGroupRuleAccess = string;\n/** Alias for IpAddressProvisioningType */\nexport type IpAddressProvisioningType = string;\n/** Alias for ContainerWorkingDirectory */\nexport type ContainerWorkingDirectory = string;\n/** Alias for ContainerHostDataPath */\nexport type ContainerHostDataPath = string;\n/** Alias for AutoUserScope */\nexport type AutoUserScope = string;\n/** Alias for ElevationLevel */\nexport type ElevationLevel = string;\n/** Alias for BatchNodeFillType */\nexport type BatchNodeFillType = string;\n/** Alias for LoginMode */\nexport type LoginMode = string;\n/** Alias for BatchNodeCommunicationMode */\nexport type BatchNodeCommunicationMode = string;\n/** Alias for UpgradeMode */\nexport type UpgradeMode = string;\n/** Alias for BatchNodeDeallocationOption */\nexport type BatchNodeDeallocationOption = string;\n/** Alias for BatchJobState */\nexport type BatchJobState = string;\n/** Alias for OutputFileUploadCondition */\nexport type OutputFileUploadCondition = string;\n/** Alias for AccessScope */\nexport type AccessScope = string;\n/** Alias for BatchPoolLifetimeOption */\nexport type BatchPoolLifetimeOption = string;\n/** Alias for OnAllBatchTasksComplete */\nexport type OnAllBatchTasksComplete = string;\n/** Alias for OnBatchTaskFailure */\nexport type OnBatchTaskFailure = string;\n/** Alias for ErrorCategory */\nexport type ErrorCategory = string;\n/** Alias for DisableBatchJobOption */\nexport type DisableBatchJobOption = string;\n/** Alias for BatchTaskExecutionResult */\nexport type BatchTaskExecutionResult = string;\n/** Alias for BatchJobScheduleState */\nexport type BatchJobScheduleState = string;\n/** Alias for BatchJobAction */\nexport type BatchJobAction = string;\n/** Alias for DependencyAction */\nexport type DependencyAction = string;\n/** Alias for BatchTaskState */\nexport type BatchTaskState = string;\n/** Alias for BatchNodeRebootOption */\nexport type BatchNodeRebootOption = string;\n/** Alias for BatchNodeDeallocateOption */\nexport type BatchNodeDeallocateOption = string;\n/** Alias for BatchNodeReimageOption */\nexport type BatchNodeReimageOption = string;\n/** Alias for BatchNodeDisableSchedulingOption */\nexport type BatchNodeDisableSchedulingOption = string;\n"]}