@aws-sdk/client-batch 3.92.0 → 3.99.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,30 @@
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
|
|
5
5
|
|
|
6
|
+
# [3.99.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.98.0...v3.99.0) (2022-05-25)
|
|
7
|
+
|
|
8
|
+
**Note:** Version bump only for package @aws-sdk/client-batch
|
|
9
|
+
|
|
10
|
+
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
|
|
14
|
+
# [3.95.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.94.0...v3.95.0) (2022-05-19)
|
|
15
|
+
|
|
16
|
+
**Note:** Version bump only for package @aws-sdk/client-batch
|
|
17
|
+
|
|
18
|
+
|
|
19
|
+
|
|
20
|
+
|
|
21
|
+
|
|
22
|
+
# [3.94.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.93.0...v3.94.0) (2022-05-18)
|
|
23
|
+
|
|
24
|
+
**Note:** Version bump only for package @aws-sdk/client-batch
|
|
25
|
+
|
|
26
|
+
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
|
|
6
30
|
# [3.92.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.91.0...v3.92.0) (2022-05-16)
|
|
7
31
|
|
|
8
32
|
**Note:** Version bump only for package @aws-sdk/client-batch
|
|
@@ -17,8 +17,10 @@ const util_utf8_node_1 = require("@aws-sdk/util-utf8-node");
|
|
|
17
17
|
const runtimeConfig_shared_1 = require("./runtimeConfig.shared");
|
|
18
18
|
const smithy_client_1 = require("@aws-sdk/smithy-client");
|
|
19
19
|
const util_defaults_mode_node_1 = require("@aws-sdk/util-defaults-mode-node");
|
|
20
|
+
const smithy_client_2 = require("@aws-sdk/smithy-client");
|
|
20
21
|
const getRuntimeConfig = (config) => {
|
|
21
22
|
var _a, _b, _c, _d, _e, _f, _g, _h, _j, _k, _l, _m, _o, _p, _q;
|
|
23
|
+
(0, smithy_client_2.emitWarningIfUnsupportedVersion)(process.version);
|
|
22
24
|
const defaultsMode = (0, util_defaults_mode_node_1.resolveDefaultsModeConfig)(config);
|
|
23
25
|
const defaultConfigProvider = () => defaultsMode().then(smithy_client_1.loadConfigsForDefaultMode);
|
|
24
26
|
const clientSharedValues = (0, runtimeConfig_shared_1.getRuntimeConfig)(config);
|
package/dist-es/runtimeConfig.js
CHANGED
|
@@ -14,8 +14,10 @@ import { fromUtf8, toUtf8 } from "@aws-sdk/util-utf8-node";
|
|
|
14
14
|
import { getRuntimeConfig as getSharedRuntimeConfig } from "./runtimeConfig.shared";
|
|
15
15
|
import { loadConfigsForDefaultMode } from "@aws-sdk/smithy-client";
|
|
16
16
|
import { resolveDefaultsModeConfig } from "@aws-sdk/util-defaults-mode-node";
|
|
17
|
+
import { emitWarningIfUnsupportedVersion } from "@aws-sdk/smithy-client";
|
|
17
18
|
export var getRuntimeConfig = function (config) {
|
|
18
19
|
var _a, _b, _c, _d, _e, _f, _g, _h, _j, _k, _l, _m, _o, _p, _q;
|
|
20
|
+
emitWarningIfUnsupportedVersion(process.version);
|
|
19
21
|
var defaultsMode = resolveDefaultsModeConfig(config);
|
|
20
22
|
var defaultConfigProvider = function () { return defaultsMode().then(loadConfigsForDefaultMode); };
|
|
21
23
|
var clientSharedValues = getSharedRuntimeConfig(config);
|
package/dist-types/Batch.d.ts
CHANGED
|
@@ -67,10 +67,11 @@ export declare class Batch extends BatchClient {
|
|
|
67
67
|
* your container instances into that Amazon ECS cluster. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html">Launching an Amazon ECS container instance</a> in the
|
|
68
68
|
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
|
|
69
69
|
* <note>
|
|
70
|
-
* <p>Batch doesn't upgrade the AMIs in a compute environment after
|
|
71
|
-
* doesn't update the AMIs when a newer version of the Amazon ECS optimized AMI is
|
|
72
|
-
* for
|
|
73
|
-
*
|
|
70
|
+
* <p>Batch doesn't automatically upgrade the AMIs in a compute environment after it's created. For example, it
|
|
71
|
+
* also doesn't update the AMIs in your compute environment when a newer version of the Amazon ECS optimized AMI is
|
|
72
|
+
* available. You're responsible for the management of the guest operating system. This includes any updates and
|
|
73
|
+
* security patches. You're also responsible for any additional application software or utilities that you install on
|
|
74
|
+
* the compute resources. There are two ways to use a new AMI for your Batch jobs. The original method is to complete
|
|
74
75
|
* these steps:</p>
|
|
75
76
|
* <ol>
|
|
76
77
|
* <li>
|
|
@@ -86,6 +87,41 @@ export declare class Batch extends BatchClient {
|
|
|
86
87
|
* <p>Delete the earlier compute environment.</p>
|
|
87
88
|
* </li>
|
|
88
89
|
* </ol>
|
|
90
|
+
* <p>In April 2022, Batch added enhanced support for updating compute environments. For more information, see
|
|
91
|
+
* <a href="https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html">Updating compute
|
|
92
|
+
* environments</a>. To use the enhanced updating of compute environments to update AMIs, follow these
|
|
93
|
+
* rules:</p>
|
|
94
|
+
* <ul>
|
|
95
|
+
* <li>
|
|
96
|
+
* <p>Either do not set the service role (<code>serviceRole</code>) parameter or set it to the <b>AWSBatchServiceRole</b> service-linked role.</p>
|
|
97
|
+
* </li>
|
|
98
|
+
* <li>
|
|
99
|
+
* <p>Set the allocation strategy (<code>allocationStrategy</code>) parameter to <code>BEST_FIT_PROGRESSIVE</code>
|
|
100
|
+
* or <code>SPOT_CAPACITY_OPTIMIZED</code>.</p>
|
|
101
|
+
* </li>
|
|
102
|
+
* <li>
|
|
103
|
+
* <p>Set the update to latest image version (<code>updateToLatestImageVersion</code>) parameter to
|
|
104
|
+
* <code>true</code>.</p>
|
|
105
|
+
* </li>
|
|
106
|
+
* <li>
|
|
107
|
+
* <p>Do not specify an AMI ID in <code>imageId</code>, <code>imageIdOverride</code> (in <a href="https://docs.aws.amazon.com/batch/latest/APIReference/API_Ec2Configuration.html">
|
|
108
|
+
* <code>ec2Configuration</code>
|
|
109
|
+
* </a>), or in the launch template (<code>launchTemplate</code>). In that case
|
|
110
|
+
* Batch will select the latest Amazon ECS optimized AMI supported by Batch at the time the infrastructure update is
|
|
111
|
+
* initiated. Alternatively you can specify the AMI ID in the <code>imageId</code> or <code>imageIdOverride</code>
|
|
112
|
+
* parameters, or the launch template identified by the <code>LaunchTemplate</code> properties. Changing any of these
|
|
113
|
+
* properties will trigger an infrastructure update. If the AMI ID is specified in the launch template, it can not be
|
|
114
|
+
* replaced by specifying an AMI ID in either the <code>imageId</code> or <code>imageIdOverride</code> parameters. It
|
|
115
|
+
* can only be replaced by specifying a different launch template, or if the launch template version is set to
|
|
116
|
+
* <code>$Default</code> or <code>$Latest</code>, by setting either a new default version for the launch template
|
|
117
|
+
* (if <code>$Default</code>)or by adding a new version to the launch template (if <code>$Latest</code>).</p>
|
|
118
|
+
* </li>
|
|
119
|
+
* </ul>
|
|
120
|
+
* <p>If these rules are followed, any update that triggers an infrastructure update will cause the AMI ID to be
|
|
121
|
+
* re-selected. If the <code>version</code> setting in the launch template (<code>launchTemplate</code>) is set to
|
|
122
|
+
* <code>$Latest</code> or <code>$Default</code>, the latest or default version of the launch template will be
|
|
123
|
+
* evaluated up at the time of the infrastructure update, even if the <code>launchTemplate</code> was not
|
|
124
|
+
* updated.</p>
|
|
89
125
|
* </note>
|
|
90
126
|
*/
|
|
91
127
|
createComputeEnvironment(args: CreateComputeEnvironmentCommandInput, options?: __HttpHandlerOptions): Promise<CreateComputeEnvironmentCommandOutput>;
|
|
@@ -26,10 +26,11 @@ export interface CreateComputeEnvironmentCommandOutput extends CreateComputeEnvi
|
|
|
26
26
|
* your container instances into that Amazon ECS cluster. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html">Launching an Amazon ECS container instance</a> in the
|
|
27
27
|
* <i>Amazon Elastic Container Service Developer Guide</i>.</p>
|
|
28
28
|
* <note>
|
|
29
|
-
* <p>Batch doesn't upgrade the AMIs in a compute environment after
|
|
30
|
-
* doesn't update the AMIs when a newer version of the Amazon ECS optimized AMI is
|
|
31
|
-
* for
|
|
32
|
-
*
|
|
29
|
+
* <p>Batch doesn't automatically upgrade the AMIs in a compute environment after it's created. For example, it
|
|
30
|
+
* also doesn't update the AMIs in your compute environment when a newer version of the Amazon ECS optimized AMI is
|
|
31
|
+
* available. You're responsible for the management of the guest operating system. This includes any updates and
|
|
32
|
+
* security patches. You're also responsible for any additional application software or utilities that you install on
|
|
33
|
+
* the compute resources. There are two ways to use a new AMI for your Batch jobs. The original method is to complete
|
|
33
34
|
* these steps:</p>
|
|
34
35
|
* <ol>
|
|
35
36
|
* <li>
|
|
@@ -45,6 +46,41 @@ export interface CreateComputeEnvironmentCommandOutput extends CreateComputeEnvi
|
|
|
45
46
|
* <p>Delete the earlier compute environment.</p>
|
|
46
47
|
* </li>
|
|
47
48
|
* </ol>
|
|
49
|
+
* <p>In April 2022, Batch added enhanced support for updating compute environments. For more information, see
|
|
50
|
+
* <a href="https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html">Updating compute
|
|
51
|
+
* environments</a>. To use the enhanced updating of compute environments to update AMIs, follow these
|
|
52
|
+
* rules:</p>
|
|
53
|
+
* <ul>
|
|
54
|
+
* <li>
|
|
55
|
+
* <p>Either do not set the service role (<code>serviceRole</code>) parameter or set it to the <b>AWSBatchServiceRole</b> service-linked role.</p>
|
|
56
|
+
* </li>
|
|
57
|
+
* <li>
|
|
58
|
+
* <p>Set the allocation strategy (<code>allocationStrategy</code>) parameter to <code>BEST_FIT_PROGRESSIVE</code>
|
|
59
|
+
* or <code>SPOT_CAPACITY_OPTIMIZED</code>.</p>
|
|
60
|
+
* </li>
|
|
61
|
+
* <li>
|
|
62
|
+
* <p>Set the update to latest image version (<code>updateToLatestImageVersion</code>) parameter to
|
|
63
|
+
* <code>true</code>.</p>
|
|
64
|
+
* </li>
|
|
65
|
+
* <li>
|
|
66
|
+
* <p>Do not specify an AMI ID in <code>imageId</code>, <code>imageIdOverride</code> (in <a href="https://docs.aws.amazon.com/batch/latest/APIReference/API_Ec2Configuration.html">
|
|
67
|
+
* <code>ec2Configuration</code>
|
|
68
|
+
* </a>), or in the launch template (<code>launchTemplate</code>). In that case
|
|
69
|
+
* Batch will select the latest Amazon ECS optimized AMI supported by Batch at the time the infrastructure update is
|
|
70
|
+
* initiated. Alternatively you can specify the AMI ID in the <code>imageId</code> or <code>imageIdOverride</code>
|
|
71
|
+
* parameters, or the launch template identified by the <code>LaunchTemplate</code> properties. Changing any of these
|
|
72
|
+
* properties will trigger an infrastructure update. If the AMI ID is specified in the launch template, it can not be
|
|
73
|
+
* replaced by specifying an AMI ID in either the <code>imageId</code> or <code>imageIdOverride</code> parameters. It
|
|
74
|
+
* can only be replaced by specifying a different launch template, or if the launch template version is set to
|
|
75
|
+
* <code>$Default</code> or <code>$Latest</code>, by setting either a new default version for the launch template
|
|
76
|
+
* (if <code>$Default</code>)or by adding a new version to the launch template (if <code>$Latest</code>).</p>
|
|
77
|
+
* </li>
|
|
78
|
+
* </ul>
|
|
79
|
+
* <p>If these rules are followed, any update that triggers an infrastructure update will cause the AMI ID to be
|
|
80
|
+
* re-selected. If the <code>version</code> setting in the launch template (<code>launchTemplate</code>) is set to
|
|
81
|
+
* <code>$Latest</code> or <code>$Default</code>, the latest or default version of the launch template will be
|
|
82
|
+
* evaluated up at the time of the infrastructure update, even if the <code>launchTemplate</code> was not
|
|
83
|
+
* updated.</p>
|
|
48
84
|
* </note>
|
|
49
85
|
* @example
|
|
50
86
|
* Use a bare-bones client and the command you need to make an API call.
|
|
@@ -489,9 +489,10 @@ export interface ComputeResource {
|
|
|
489
489
|
* <p>Key-value pair tags to be applied to EC2 resources that are launched in the compute environment. For Batch,
|
|
490
490
|
* these take the form of "String1": "String2", where String1 is the tag key and String2 is the tag value−for
|
|
491
491
|
* example, <code>{ "Name": "Batch Instance - C4OnDemand" }</code>. This is helpful for recognizing your Batch
|
|
492
|
-
* instances in the Amazon EC2 console.
|
|
493
|
-
*
|
|
494
|
-
*
|
|
492
|
+
* instances in the Amazon EC2 console. Updating these tags requires an infrastructure update to the compute environment. For
|
|
493
|
+
* more information, see <a href="https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html">Updating compute
|
|
494
|
+
* environments</a> in the <i>Batch User Guide</i>. These tags aren't seen when using the Batch
|
|
495
|
+
* <code>ListTagsForResource</code> API operation.</p>
|
|
495
496
|
* <note>
|
|
496
497
|
* <p>This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be
|
|
497
498
|
* specified.</p>
|
|
@@ -3490,7 +3491,8 @@ export interface SubmitJobRequest {
|
|
|
3490
3491
|
*/
|
|
3491
3492
|
jobQueue: string | undefined;
|
|
3492
3493
|
/**
|
|
3493
|
-
* <p>The share identifier for the job
|
|
3494
|
+
* <p>The share identifier for the job. If the job queue does not have a scheduling policy, then this parameter must
|
|
3495
|
+
* not be specified. If the job queue has a scheduling policy, then this parameter must be specified.</p>
|
|
3494
3496
|
*/
|
|
3495
3497
|
shareIdentifier?: string;
|
|
3496
3498
|
/**
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@aws-sdk/client-batch",
|
|
3
3
|
"description": "AWS SDK for JavaScript Batch Client for Node.js, Browser and React Native",
|
|
4
|
-
"version": "3.
|
|
4
|
+
"version": "3.99.0",
|
|
5
5
|
"scripts": {
|
|
6
6
|
"build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
|
|
7
7
|
"build:cjs": "tsc -p tsconfig.cjs.json",
|
|
@@ -18,9 +18,9 @@
|
|
|
18
18
|
"dependencies": {
|
|
19
19
|
"@aws-crypto/sha256-browser": "2.0.0",
|
|
20
20
|
"@aws-crypto/sha256-js": "2.0.0",
|
|
21
|
-
"@aws-sdk/client-sts": "3.
|
|
21
|
+
"@aws-sdk/client-sts": "3.99.0",
|
|
22
22
|
"@aws-sdk/config-resolver": "3.80.0",
|
|
23
|
-
"@aws-sdk/credential-provider-node": "3.
|
|
23
|
+
"@aws-sdk/credential-provider-node": "3.99.0",
|
|
24
24
|
"@aws-sdk/fetch-http-handler": "3.78.0",
|
|
25
25
|
"@aws-sdk/hash-node": "3.78.0",
|
|
26
26
|
"@aws-sdk/invalid-dependency": "3.78.0",
|
|
@@ -33,17 +33,17 @@
|
|
|
33
33
|
"@aws-sdk/middleware-stack": "3.78.0",
|
|
34
34
|
"@aws-sdk/middleware-user-agent": "3.78.0",
|
|
35
35
|
"@aws-sdk/node-config-provider": "3.80.0",
|
|
36
|
-
"@aws-sdk/node-http-handler": "3.
|
|
36
|
+
"@aws-sdk/node-http-handler": "3.94.0",
|
|
37
37
|
"@aws-sdk/protocol-http": "3.78.0",
|
|
38
|
-
"@aws-sdk/smithy-client": "3.
|
|
38
|
+
"@aws-sdk/smithy-client": "3.99.0",
|
|
39
39
|
"@aws-sdk/types": "3.78.0",
|
|
40
40
|
"@aws-sdk/url-parser": "3.78.0",
|
|
41
41
|
"@aws-sdk/util-base64-browser": "3.58.0",
|
|
42
42
|
"@aws-sdk/util-base64-node": "3.55.0",
|
|
43
43
|
"@aws-sdk/util-body-length-browser": "3.55.0",
|
|
44
44
|
"@aws-sdk/util-body-length-node": "3.55.0",
|
|
45
|
-
"@aws-sdk/util-defaults-mode-browser": "3.
|
|
46
|
-
"@aws-sdk/util-defaults-mode-node": "3.
|
|
45
|
+
"@aws-sdk/util-defaults-mode-browser": "3.99.0",
|
|
46
|
+
"@aws-sdk/util-defaults-mode-node": "3.99.0",
|
|
47
47
|
"@aws-sdk/util-user-agent-browser": "3.78.0",
|
|
48
48
|
"@aws-sdk/util-user-agent-node": "3.80.0",
|
|
49
49
|
"@aws-sdk/util-utf8-browser": "3.55.0",
|