diff --git a/services/batch/2017-05-01.5.0/batch/computenode.go b/services/batch/2017-05-01.5.0/batch/computenode.go index e4fdb08f2a63..ac9585036376 100644 --- a/services/batch/2017-05-01.5.0/batch/computenode.go +++ b/services/batch/2017-05-01.5.0/batch/computenode.go @@ -1162,7 +1162,7 @@ func (client ComputeNodeClient) ReimageResponder(resp *http.Response) (result au return } -// UpdateUser this operation replaces of all the updateable properties of the account. For example, if the expiryTime +// UpdateUser this operation replaces of all the updatable properties of the account. For example, if the expiryTime // element is not specified, the current value is replaced with the default value, not left unmodified. You can update // a user account on a node only when it is in the idle or running state. // Parameters: diff --git a/services/batch/2017-05-01.5.0/batch/job.go b/services/batch/2017-05-01.5.0/batch/job.go index 10b57e4d1d1c..ca0f8405ddfa 100644 --- a/services/batch/2017-05-01.5.0/batch/job.go +++ b/services/batch/2017-05-01.5.0/batch/job.go @@ -1565,7 +1565,7 @@ func (client JobClient) TerminateResponder(resp *http.Response) (result autorest return } -// Update this fully replaces all the updateable properties of the job. For example, if the job has constraints +// Update this fully replaces all the updatable properties of the job. For example, if the job has constraints // associated with it and if constraints is not specified with this request, then the Batch service will remove the // existing constraints. // Parameters: diff --git a/services/batch/2017-05-01.5.0/batch/jobschedule.go b/services/batch/2017-05-01.5.0/batch/jobschedule.go index 0b0de75be29e..d55ed2ba9a9d 100644 --- a/services/batch/2017-05-01.5.0/batch/jobschedule.go +++ b/services/batch/2017-05-01.5.0/batch/jobschedule.go @@ -1248,7 +1248,7 @@ func (client JobScheduleClient) TerminateResponder(resp *http.Response) (result return } -// Update this fully replaces all the updateable properties of the job schedule. For example, if the schedule property +// Update this fully replaces all the updatable properties of the job schedule. For example, if the schedule property // is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job // schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are // unaffected. diff --git a/services/batch/2017-05-01.5.0/batch/models.go b/services/batch/2017-05-01.5.0/batch/models.go index 79ebf564dc85..ca0bed91487a 100644 --- a/services/batch/2017-05-01.5.0/batch/models.go +++ b/services/batch/2017-05-01.5.0/batch/models.go @@ -2336,7 +2336,7 @@ type ExitConditions struct { PreProcessingError *ExitOptions `json:"preProcessingError,omitempty"` // FileUploadError - 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. FileUploadError *ExitOptions `json:"fileUploadError,omitempty"` - // Default - 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 behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection. + // Default - 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. Default *ExitOptions `json:"default,omitempty"` } diff --git a/services/batch/2017-05-01.5.0/batch/pool.go b/services/batch/2017-05-01.5.0/batch/pool.go index 2539880ead08..20783770ddf3 100644 --- a/services/batch/2017-05-01.5.0/batch/pool.go +++ b/services/batch/2017-05-01.5.0/batch/pool.go @@ -1862,7 +1862,7 @@ func (client PoolClient) StopResizeResponder(resp *http.Response) (result autore return } -// UpdateProperties this fully replaces all the updateable properties of the pool. For example, if the pool has a start +// UpdateProperties this fully replaces all the updatable properties of the pool. For example, if the pool has a start // task associated with it and if start task is not specified with this request, then the Batch service will remove the // existing start task. // Parameters: diff --git a/services/batch/2018-03-01.6.1/batch/computenode.go b/services/batch/2018-03-01.6.1/batch/computenode.go index 8622e8a3d7aa..a94bf942dcbe 100644 --- a/services/batch/2018-03-01.6.1/batch/computenode.go +++ b/services/batch/2018-03-01.6.1/batch/computenode.go @@ -1164,7 +1164,7 @@ func (client ComputeNodeClient) ReimageResponder(resp *http.Response) (result au return } -// UpdateUser this operation replaces of all the updateable properties of the account. For example, if the expiryTime +// UpdateUser this operation replaces of all the updatable properties of the account. For example, if the expiryTime // element is not specified, the current value is replaced with the default value, not left unmodified. You can update // a user account on a node only when it is in the idle or running state. // Parameters: diff --git a/services/batch/2018-03-01.6.1/batch/job.go b/services/batch/2018-03-01.6.1/batch/job.go index b44ca6c0f9b0..393e4088c8b2 100644 --- a/services/batch/2018-03-01.6.1/batch/job.go +++ b/services/batch/2018-03-01.6.1/batch/job.go @@ -1710,7 +1710,7 @@ func (client JobClient) TerminateResponder(resp *http.Response) (result autorest return } -// Update this fully replaces all the updateable properties of the job. For example, if the job has constraints +// Update this fully replaces all the updatable properties of the job. For example, if the job has constraints // associated with it and if constraints is not specified with this request, then the Batch service will remove the // existing constraints. // Parameters: diff --git a/services/batch/2018-03-01.6.1/batch/jobschedule.go b/services/batch/2018-03-01.6.1/batch/jobschedule.go index 1df642b61991..1540d43123d4 100644 --- a/services/batch/2018-03-01.6.1/batch/jobschedule.go +++ b/services/batch/2018-03-01.6.1/batch/jobschedule.go @@ -1280,7 +1280,7 @@ func (client JobScheduleClient) TerminateResponder(resp *http.Response) (result return } -// Update this fully replaces all the updateable properties of the job schedule. For example, if the schedule property +// Update this fully replaces all the updatable properties of the job schedule. For example, if the schedule property // is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job // schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are // unaffected. diff --git a/services/batch/2018-03-01.6.1/batch/models.go b/services/batch/2018-03-01.6.1/batch/models.go index 87138e7373ab..988c070acdad 100644 --- a/services/batch/2018-03-01.6.1/batch/models.go +++ b/services/batch/2018-03-01.6.1/batch/models.go @@ -2540,13 +2540,13 @@ type ExitConditions struct { PreProcessingError *ExitOptions `json:"preProcessingError,omitempty"` // FileUploadError - 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. FileUploadError *ExitOptions `json:"fileUploadError,omitempty"` - // Default - 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 behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection. + // Default - 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. Default *ExitOptions `json:"default,omitempty"` } // ExitOptions ... type ExitOptions struct { - // JobAction - 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). Possible values include: 'JobActionNone', 'JobActionDisable', 'JobActionTerminate' + // JobAction - 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). Possible values include: 'JobActionNone', 'JobActionDisable', 'JobActionTerminate' JobAction JobAction `json:"jobAction,omitempty"` // DependencyAction - The default is 'satisfy' for exit code 0, and 'block' for all other exit conditions. If the job's usesTaskDependencies property is set to false, then specifying the dependencyAction 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). Possible values include: 'Satisfy', 'Block' DependencyAction DependencyAction `json:"dependencyAction,omitempty"` @@ -2763,7 +2763,7 @@ type JobPreparationTask struct { Constraints *TaskConstraints `json:"constraints,omitempty"` // WaitForSuccess - If true and the Job Preparation task fails on a compute 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 compute node. The compute 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 node. The default value is true. WaitForSuccess *bool `json:"waitForSuccess,omitempty"` - // UserIdentity - If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a a non-administrative user unique to the pool on Linux nodes. + // UserIdentity - If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a non-administrative user unique to the pool on Linux nodes. UserIdentity *UserIdentity `json:"userIdentity,omitempty"` // RerunOnNodeRebootAfterSuccess - 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. RerunOnNodeRebootAfterSuccess *bool `json:"rerunOnNodeRebootAfterSuccess,omitempty"` diff --git a/services/batch/2018-03-01.6.1/batch/pool.go b/services/batch/2018-03-01.6.1/batch/pool.go index d2af417e87ac..5a6ee763d741 100644 --- a/services/batch/2018-03-01.6.1/batch/pool.go +++ b/services/batch/2018-03-01.6.1/batch/pool.go @@ -1876,7 +1876,7 @@ func (client PoolClient) StopResizeResponder(resp *http.Response) (result autore return } -// UpdateProperties this fully replaces all the updateable properties of the pool. For example, if the pool has a start +// UpdateProperties this fully replaces all the updatable properties of the pool. For example, if the pool has a start // task associated with it and if start task is not specified with this request, then the Batch service will remove the // existing start task. // Parameters: diff --git a/services/batch/2018-08-01.7.0/batch/computenode.go b/services/batch/2018-08-01.7.0/batch/computenode.go index 9456cee6ec45..fe8b02f6e0ac 100644 --- a/services/batch/2018-08-01.7.0/batch/computenode.go +++ b/services/batch/2018-08-01.7.0/batch/computenode.go @@ -1164,7 +1164,7 @@ func (client ComputeNodeClient) ReimageResponder(resp *http.Response) (result au return } -// UpdateUser this operation replaces of all the updateable properties of the account. For example, if the expiryTime +// UpdateUser this operation replaces of all the updatable properties of the account. For example, if the expiryTime // element is not specified, the current value is replaced with the default value, not left unmodified. You can update // a user account on a node only when it is in the idle or running state. // Parameters: diff --git a/services/batch/2018-08-01.7.0/batch/job.go b/services/batch/2018-08-01.7.0/batch/job.go index b9bd3e4efacb..a727d58d1a5d 100644 --- a/services/batch/2018-08-01.7.0/batch/job.go +++ b/services/batch/2018-08-01.7.0/batch/job.go @@ -1708,7 +1708,7 @@ func (client JobClient) TerminateResponder(resp *http.Response) (result autorest return } -// Update this fully replaces all the updateable properties of the job. For example, if the job has constraints +// Update this fully replaces all the updatable properties of the job. For example, if the job has constraints // associated with it and if constraints is not specified with this request, then the Batch service will remove the // existing constraints. // Parameters: diff --git a/services/batch/2018-08-01.7.0/batch/jobschedule.go b/services/batch/2018-08-01.7.0/batch/jobschedule.go index 063cab5575db..f4e35c48da78 100644 --- a/services/batch/2018-08-01.7.0/batch/jobschedule.go +++ b/services/batch/2018-08-01.7.0/batch/jobschedule.go @@ -1280,7 +1280,7 @@ func (client JobScheduleClient) TerminateResponder(resp *http.Response) (result return } -// Update this fully replaces all the updateable properties of the job schedule. For example, if the schedule property +// Update this fully replaces all the updatable properties of the job schedule. For example, if the schedule property // is not specified with this request, then the Batch service will remove the existing schedule. Changes to a job // schedule only impact jobs created by the schedule after the update has taken place; currently running jobs are // unaffected. diff --git a/services/batch/2018-08-01.7.0/batch/models.go b/services/batch/2018-08-01.7.0/batch/models.go index e2da5491e920..f0fedd5ebf1f 100644 --- a/services/batch/2018-08-01.7.0/batch/models.go +++ b/services/batch/2018-08-01.7.0/batch/models.go @@ -2527,13 +2527,13 @@ type ExitConditions struct { PreProcessingError *ExitOptions `json:"preProcessingError,omitempty"` // FileUploadError - 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. FileUploadError *ExitOptions `json:"fileUploadError,omitempty"` - // Default - 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 behaviour on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection. + // Default - 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. Default *ExitOptions `json:"default,omitempty"` } // ExitOptions ... type ExitOptions struct { - // JobAction - 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). Possible values include: 'JobActionNone', 'JobActionDisable', 'JobActionTerminate' + // JobAction - 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). Possible values include: 'JobActionNone', 'JobActionDisable', 'JobActionTerminate' JobAction JobAction `json:"jobAction,omitempty"` // DependencyAction - The default is 'satisfy' for exit code 0, and 'block' for all other exit conditions. If the job's usesTaskDependencies property is set to false, then specifying the dependencyAction 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). Possible values include: 'Satisfy', 'Block' DependencyAction DependencyAction `json:"dependencyAction,omitempty"` @@ -2750,7 +2750,7 @@ type JobPreparationTask struct { Constraints *TaskConstraints `json:"constraints,omitempty"` // WaitForSuccess - If true and the Job Preparation task fails on a compute 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 compute node. The compute 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 node. The default value is true. WaitForSuccess *bool `json:"waitForSuccess,omitempty"` - // UserIdentity - If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a a non-administrative user unique to the pool on Linux nodes. + // UserIdentity - If omitted, the task runs as a non-administrative user unique to the task on Windows nodes, or a non-administrative user unique to the pool on Linux nodes. UserIdentity *UserIdentity `json:"userIdentity,omitempty"` // RerunOnNodeRebootAfterSuccess - 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. RerunOnNodeRebootAfterSuccess *bool `json:"rerunOnNodeRebootAfterSuccess,omitempty"` diff --git a/services/batch/2018-08-01.7.0/batch/pool.go b/services/batch/2018-08-01.7.0/batch/pool.go index 3944be0426b6..15b61063a312 100644 --- a/services/batch/2018-08-01.7.0/batch/pool.go +++ b/services/batch/2018-08-01.7.0/batch/pool.go @@ -1876,7 +1876,7 @@ func (client PoolClient) StopResizeResponder(resp *http.Response) (result autore return } -// UpdateProperties this fully replaces all the updateable properties of the pool. For example, if the pool has a start +// UpdateProperties this fully replaces all the updatable properties of the pool. For example, if the pool has a start // task associated with it and if start task is not specified with this request, then the Batch service will remove the // existing start task. // Parameters: