@aws-sdk/client-codedeploy 3.408.0 → 3.409.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/dist-cjs/endpoint/ruleset.js +3 -3
- package/dist-es/endpoint/ruleset.js +3 -3
- package/dist-types/CodeDeploy.d.ts +25 -25
- package/dist-types/CodeDeployClient.d.ts +25 -25
- package/dist-types/commands/BatchGetDeploymentInstancesCommand.d.ts +2 -2
- package/dist-types/commands/BatchGetDeploymentTargetsCommand.d.ts +9 -9
- package/dist-types/commands/CreateDeploymentCommand.d.ts +11 -11
- package/dist-types/commands/CreateDeploymentGroupCommand.d.ts +6 -6
- package/dist-types/commands/DeleteDeploymentConfigCommand.d.ts +2 -2
- package/dist-types/commands/GetDeploymentCommand.d.ts +2 -2
- package/dist-types/commands/ListDeploymentInstancesCommand.d.ts +2 -2
- package/dist-types/commands/ListOnPremisesInstancesCommand.d.ts +1 -1
- package/dist-types/commands/RegisterOnPremisesInstanceCommand.d.ts +2 -2
- package/dist-types/commands/UpdateDeploymentGroupCommand.d.ts +6 -6
- package/dist-types/index.d.ts +25 -25
- package/dist-types/models/models_0.d.ts +210 -218
- package/package.json +3 -3
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
"use strict";
|
|
2
2
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
3
3
|
exports.ruleSet = void 0;
|
|
4
|
-
const
|
|
5
|
-
const a = "
|
|
6
|
-
const _data = { version: "1.0", parameters: { Region:
|
|
4
|
+
const q = "required", r = "fn", s = "argv", t = "ref";
|
|
5
|
+
const a = "isSet", b = "tree", c = "error", d = "endpoint", e = "PartitionResult", f = { [q]: false, "type": "String" }, g = { [q]: true, "default": false, "type": "Boolean" }, h = { [t]: "Endpoint" }, i = { [r]: "booleanEquals", [s]: [{ [t]: "UseFIPS" }, true] }, j = { [r]: "booleanEquals", [s]: [{ [t]: "UseDualStack" }, true] }, k = {}, l = { [r]: "booleanEquals", [s]: [true, { [r]: "getAttr", [s]: [{ [t]: e }, "supportsFIPS"] }] }, m = { [r]: "booleanEquals", [s]: [true, { [r]: "getAttr", [s]: [{ [t]: e }, "supportsDualStack"] }] }, n = [i], o = [j], p = [{ [t]: "Region" }];
|
|
6
|
+
const _data = { version: "1.0", parameters: { Region: f, UseDualStack: g, UseFIPS: g, Endpoint: f }, rules: [{ conditions: [{ [r]: a, [s]: [h] }], type: b, rules: [{ conditions: n, error: "Invalid Configuration: FIPS and custom endpoint are not supported", type: c }, { conditions: o, error: "Invalid Configuration: Dualstack and custom endpoint are not supported", type: c }, { endpoint: { url: h, properties: k, headers: k }, type: d }] }, { conditions: [{ [r]: a, [s]: p }], type: b, rules: [{ conditions: [{ [r]: "aws.partition", [s]: p, assign: e }], type: b, rules: [{ conditions: [i, j], type: b, rules: [{ conditions: [l, m], type: b, rules: [{ endpoint: { url: "https://codedeploy-fips.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: k, headers: k }, type: d }] }, { error: "FIPS and DualStack are enabled, but this partition does not support one or both", type: c }] }, { conditions: n, type: b, rules: [{ conditions: [l], type: b, rules: [{ endpoint: { url: "https://codedeploy-fips.{Region}.{PartitionResult#dnsSuffix}", properties: k, headers: k }, type: d }] }, { error: "FIPS is enabled but this partition does not support FIPS", type: c }] }, { conditions: o, type: b, rules: [{ conditions: [m], type: b, rules: [{ endpoint: { url: "https://codedeploy.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: k, headers: k }, type: d }] }, { error: "DualStack is enabled but this partition does not support DualStack", type: c }] }, { endpoint: { url: "https://codedeploy.{Region}.{PartitionResult#dnsSuffix}", properties: k, headers: k }, type: d }] }] }, { error: "Invalid Configuration: Missing Region", type: c }] };
|
|
7
7
|
exports.ruleSet = _data;
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
const
|
|
2
|
-
const a = "
|
|
3
|
-
const _data = { version: "1.0", parameters: { Region:
|
|
1
|
+
const q = "required", r = "fn", s = "argv", t = "ref";
|
|
2
|
+
const a = "isSet", b = "tree", c = "error", d = "endpoint", e = "PartitionResult", f = { [q]: false, "type": "String" }, g = { [q]: true, "default": false, "type": "Boolean" }, h = { [t]: "Endpoint" }, i = { [r]: "booleanEquals", [s]: [{ [t]: "UseFIPS" }, true] }, j = { [r]: "booleanEquals", [s]: [{ [t]: "UseDualStack" }, true] }, k = {}, l = { [r]: "booleanEquals", [s]: [true, { [r]: "getAttr", [s]: [{ [t]: e }, "supportsFIPS"] }] }, m = { [r]: "booleanEquals", [s]: [true, { [r]: "getAttr", [s]: [{ [t]: e }, "supportsDualStack"] }] }, n = [i], o = [j], p = [{ [t]: "Region" }];
|
|
3
|
+
const _data = { version: "1.0", parameters: { Region: f, UseDualStack: g, UseFIPS: g, Endpoint: f }, rules: [{ conditions: [{ [r]: a, [s]: [h] }], type: b, rules: [{ conditions: n, error: "Invalid Configuration: FIPS and custom endpoint are not supported", type: c }, { conditions: o, error: "Invalid Configuration: Dualstack and custom endpoint are not supported", type: c }, { endpoint: { url: h, properties: k, headers: k }, type: d }] }, { conditions: [{ [r]: a, [s]: p }], type: b, rules: [{ conditions: [{ [r]: "aws.partition", [s]: p, assign: e }], type: b, rules: [{ conditions: [i, j], type: b, rules: [{ conditions: [l, m], type: b, rules: [{ endpoint: { url: "https://codedeploy-fips.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: k, headers: k }, type: d }] }, { error: "FIPS and DualStack are enabled, but this partition does not support one or both", type: c }] }, { conditions: n, type: b, rules: [{ conditions: [l], type: b, rules: [{ endpoint: { url: "https://codedeploy-fips.{Region}.{PartitionResult#dnsSuffix}", properties: k, headers: k }, type: d }] }, { error: "FIPS is enabled but this partition does not support FIPS", type: c }] }, { conditions: o, type: b, rules: [{ conditions: [m], type: b, rules: [{ endpoint: { url: "https://codedeploy.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: k, headers: k }, type: d }] }, { error: "DualStack is enabled but this partition does not support DualStack", type: c }] }, { endpoint: { url: "https://codedeploy.{Region}.{PartitionResult#dnsSuffix}", properties: k, headers: k }, type: d }] }] }, { error: "Invalid Configuration: Missing Region", type: c }] };
|
|
4
4
|
export const ruleSet = _data;
|
|
@@ -337,32 +337,32 @@ export interface CodeDeploy {
|
|
|
337
337
|
* to Amazon EC2 instances, on-premises instances running in your own facility,
|
|
338
338
|
* serverless Lambda functions, or applications in an Amazon ECS
|
|
339
339
|
* service.</p>
|
|
340
|
-
*
|
|
340
|
+
* <p>You can deploy a nearly unlimited variety of application content, such as an updated
|
|
341
341
|
* Lambda function, updated applications in an Amazon ECS service,
|
|
342
342
|
* code, web and configuration files, executables, packages, scripts, multimedia files, and
|
|
343
343
|
* so on. CodeDeploy can deploy application content stored in Amazon S3
|
|
344
344
|
* buckets, GitHub repositories, or Bitbucket repositories. You do not need to make changes
|
|
345
345
|
* to your existing code before you can use CodeDeploy.</p>
|
|
346
|
-
*
|
|
346
|
+
* <p>CodeDeploy makes it easier for you to rapidly release new features, helps
|
|
347
347
|
* you avoid downtime during application deployment, and handles the complexity of updating
|
|
348
348
|
* your applications, without many of the risks associated with error-prone manual
|
|
349
349
|
* deployments.</p>
|
|
350
|
-
*
|
|
350
|
+
* <p>
|
|
351
351
|
* <b>CodeDeploy Components</b>
|
|
352
|
-
*
|
|
353
|
-
*
|
|
354
|
-
*
|
|
352
|
+
* </p>
|
|
353
|
+
* <p>Use the information in this guide to help you work with the following CodeDeploy components:</p>
|
|
354
|
+
* <ul>
|
|
355
355
|
* <li>
|
|
356
|
-
*
|
|
357
|
-
*
|
|
356
|
+
* <p>
|
|
357
|
+
* <b>Application</b>: A name that uniquely identifies
|
|
358
358
|
* the application you want to deploy. CodeDeploy uses this name, which
|
|
359
359
|
* functions as a container, to ensure the correct combination of revision,
|
|
360
360
|
* deployment configuration, and deployment group are referenced during a
|
|
361
361
|
* deployment.</p>
|
|
362
362
|
* </li>
|
|
363
363
|
* <li>
|
|
364
|
-
*
|
|
365
|
-
*
|
|
364
|
+
* <p>
|
|
365
|
+
* <b>Deployment group</b>: A set of individual
|
|
366
366
|
* instances, CodeDeploy
|
|
367
367
|
* Lambda deployment configuration settings, or an Amazon ECS
|
|
368
368
|
* service and network details. A Lambda deployment group specifies how
|
|
@@ -372,20 +372,20 @@ export interface CodeDeploy {
|
|
|
372
372
|
* settings.</p>
|
|
373
373
|
* </li>
|
|
374
374
|
* <li>
|
|
375
|
-
*
|
|
376
|
-
*
|
|
375
|
+
* <p>
|
|
376
|
+
* <b>Deployment configuration</b>: A set of deployment
|
|
377
377
|
* rules and deployment success and failure conditions used by CodeDeploy during a deployment.</p>
|
|
378
378
|
* </li>
|
|
379
379
|
* <li>
|
|
380
|
-
*
|
|
381
|
-
*
|
|
380
|
+
* <p>
|
|
381
|
+
* <b>Deployment</b>: The process and the components used
|
|
382
382
|
* when updating a Lambda function, a containerized application in an
|
|
383
383
|
* Amazon ECS service, or of installing content on one or more
|
|
384
384
|
* instances. </p>
|
|
385
385
|
* </li>
|
|
386
386
|
* <li>
|
|
387
|
-
*
|
|
388
|
-
*
|
|
387
|
+
* <p>
|
|
388
|
+
* <b>Application revisions</b>: For an Lambda deployment, this is an AppSpec file that specifies the
|
|
389
389
|
* Lambda function to be updated and one or more functions to
|
|
390
390
|
* validate deployment lifecycle events. For an Amazon ECS deployment, this
|
|
391
391
|
* is an AppSpec file that specifies the Amazon ECS task definition,
|
|
@@ -397,33 +397,33 @@ export interface CodeDeploy {
|
|
|
397
397
|
* identified by its commit ID.</p>
|
|
398
398
|
* </li>
|
|
399
399
|
* </ul>
|
|
400
|
-
*
|
|
400
|
+
* <p>This guide also contains information to help you get details about the instances in
|
|
401
401
|
* your deployments, to make on-premises instances available for CodeDeploy
|
|
402
402
|
* deployments, to get details about a Lambda function deployment, and to get
|
|
403
403
|
* details about Amazon ECS service deployments.</p>
|
|
404
|
-
*
|
|
404
|
+
* <p>
|
|
405
405
|
* <b>CodeDeploy Information Resources</b>
|
|
406
406
|
* </p>
|
|
407
|
-
*
|
|
407
|
+
* <ul>
|
|
408
408
|
* <li>
|
|
409
|
-
*
|
|
409
|
+
* <p>
|
|
410
410
|
* <a href="https://docs.aws.amazon.com/codedeploy/latest/userguide">CodeDeploy User Guide</a>
|
|
411
411
|
* </p>
|
|
412
412
|
* </li>
|
|
413
413
|
* <li>
|
|
414
|
-
*
|
|
414
|
+
* <p>
|
|
415
415
|
* <a href="https://docs.aws.amazon.com/codedeploy/latest/APIReference/">CodeDeploy API Reference Guide</a>
|
|
416
416
|
* </p>
|
|
417
417
|
* </li>
|
|
418
418
|
* <li>
|
|
419
|
-
*
|
|
419
|
+
* <p>
|
|
420
420
|
* <a href="https://docs.aws.amazon.com/cli/latest/reference/deploy/index.html">CLI Reference for CodeDeploy</a>
|
|
421
421
|
* </p>
|
|
422
422
|
* </li>
|
|
423
423
|
* <li>
|
|
424
|
-
*
|
|
425
|
-
*
|
|
426
|
-
*
|
|
424
|
+
* <p>
|
|
425
|
+
* <a href="https://forums.aws.amazon.com/forum.jspa?forumID=179">CodeDeploy Developer Forum</a>
|
|
426
|
+
* </p>
|
|
427
427
|
* </li>
|
|
428
428
|
* </ul>
|
|
429
429
|
*/
|
|
@@ -201,32 +201,32 @@ export interface CodeDeployClientResolvedConfig extends CodeDeployClientResolved
|
|
|
201
201
|
* to Amazon EC2 instances, on-premises instances running in your own facility,
|
|
202
202
|
* serverless Lambda functions, or applications in an Amazon ECS
|
|
203
203
|
* service.</p>
|
|
204
|
-
*
|
|
204
|
+
* <p>You can deploy a nearly unlimited variety of application content, such as an updated
|
|
205
205
|
* Lambda function, updated applications in an Amazon ECS service,
|
|
206
206
|
* code, web and configuration files, executables, packages, scripts, multimedia files, and
|
|
207
207
|
* so on. CodeDeploy can deploy application content stored in Amazon S3
|
|
208
208
|
* buckets, GitHub repositories, or Bitbucket repositories. You do not need to make changes
|
|
209
209
|
* to your existing code before you can use CodeDeploy.</p>
|
|
210
|
-
*
|
|
210
|
+
* <p>CodeDeploy makes it easier for you to rapidly release new features, helps
|
|
211
211
|
* you avoid downtime during application deployment, and handles the complexity of updating
|
|
212
212
|
* your applications, without many of the risks associated with error-prone manual
|
|
213
213
|
* deployments.</p>
|
|
214
|
-
*
|
|
214
|
+
* <p>
|
|
215
215
|
* <b>CodeDeploy Components</b>
|
|
216
|
-
*
|
|
217
|
-
*
|
|
218
|
-
*
|
|
216
|
+
* </p>
|
|
217
|
+
* <p>Use the information in this guide to help you work with the following CodeDeploy components:</p>
|
|
218
|
+
* <ul>
|
|
219
219
|
* <li>
|
|
220
|
-
*
|
|
221
|
-
*
|
|
220
|
+
* <p>
|
|
221
|
+
* <b>Application</b>: A name that uniquely identifies
|
|
222
222
|
* the application you want to deploy. CodeDeploy uses this name, which
|
|
223
223
|
* functions as a container, to ensure the correct combination of revision,
|
|
224
224
|
* deployment configuration, and deployment group are referenced during a
|
|
225
225
|
* deployment.</p>
|
|
226
226
|
* </li>
|
|
227
227
|
* <li>
|
|
228
|
-
*
|
|
229
|
-
*
|
|
228
|
+
* <p>
|
|
229
|
+
* <b>Deployment group</b>: A set of individual
|
|
230
230
|
* instances, CodeDeploy
|
|
231
231
|
* Lambda deployment configuration settings, or an Amazon ECS
|
|
232
232
|
* service and network details. A Lambda deployment group specifies how
|
|
@@ -236,20 +236,20 @@ export interface CodeDeployClientResolvedConfig extends CodeDeployClientResolved
|
|
|
236
236
|
* settings.</p>
|
|
237
237
|
* </li>
|
|
238
238
|
* <li>
|
|
239
|
-
*
|
|
240
|
-
*
|
|
239
|
+
* <p>
|
|
240
|
+
* <b>Deployment configuration</b>: A set of deployment
|
|
241
241
|
* rules and deployment success and failure conditions used by CodeDeploy during a deployment.</p>
|
|
242
242
|
* </li>
|
|
243
243
|
* <li>
|
|
244
|
-
*
|
|
245
|
-
*
|
|
244
|
+
* <p>
|
|
245
|
+
* <b>Deployment</b>: The process and the components used
|
|
246
246
|
* when updating a Lambda function, a containerized application in an
|
|
247
247
|
* Amazon ECS service, or of installing content on one or more
|
|
248
248
|
* instances. </p>
|
|
249
249
|
* </li>
|
|
250
250
|
* <li>
|
|
251
|
-
*
|
|
252
|
-
*
|
|
251
|
+
* <p>
|
|
252
|
+
* <b>Application revisions</b>: For an Lambda deployment, this is an AppSpec file that specifies the
|
|
253
253
|
* Lambda function to be updated and one or more functions to
|
|
254
254
|
* validate deployment lifecycle events. For an Amazon ECS deployment, this
|
|
255
255
|
* is an AppSpec file that specifies the Amazon ECS task definition,
|
|
@@ -261,33 +261,33 @@ export interface CodeDeployClientResolvedConfig extends CodeDeployClientResolved
|
|
|
261
261
|
* identified by its commit ID.</p>
|
|
262
262
|
* </li>
|
|
263
263
|
* </ul>
|
|
264
|
-
*
|
|
264
|
+
* <p>This guide also contains information to help you get details about the instances in
|
|
265
265
|
* your deployments, to make on-premises instances available for CodeDeploy
|
|
266
266
|
* deployments, to get details about a Lambda function deployment, and to get
|
|
267
267
|
* details about Amazon ECS service deployments.</p>
|
|
268
|
-
*
|
|
268
|
+
* <p>
|
|
269
269
|
* <b>CodeDeploy Information Resources</b>
|
|
270
270
|
* </p>
|
|
271
|
-
*
|
|
271
|
+
* <ul>
|
|
272
272
|
* <li>
|
|
273
|
-
*
|
|
273
|
+
* <p>
|
|
274
274
|
* <a href="https://docs.aws.amazon.com/codedeploy/latest/userguide">CodeDeploy User Guide</a>
|
|
275
275
|
* </p>
|
|
276
276
|
* </li>
|
|
277
277
|
* <li>
|
|
278
|
-
*
|
|
278
|
+
* <p>
|
|
279
279
|
* <a href="https://docs.aws.amazon.com/codedeploy/latest/APIReference/">CodeDeploy API Reference Guide</a>
|
|
280
280
|
* </p>
|
|
281
281
|
* </li>
|
|
282
282
|
* <li>
|
|
283
|
-
*
|
|
283
|
+
* <p>
|
|
284
284
|
* <a href="https://docs.aws.amazon.com/cli/latest/reference/deploy/index.html">CLI Reference for CodeDeploy</a>
|
|
285
285
|
* </p>
|
|
286
286
|
* </li>
|
|
287
287
|
* <li>
|
|
288
|
-
*
|
|
289
|
-
*
|
|
290
|
-
*
|
|
288
|
+
* <p>
|
|
289
|
+
* <a href="https://forums.aws.amazon.com/forum.jspa?forumID=179">CodeDeploy Developer Forum</a>
|
|
290
|
+
* </p>
|
|
291
291
|
* </li>
|
|
292
292
|
* </ul>
|
|
293
293
|
*/
|
|
@@ -28,8 +28,8 @@ export interface BatchGetDeploymentInstancesCommandOutput extends BatchGetDeploy
|
|
|
28
28
|
* <note>
|
|
29
29
|
* <p> This method works, but is deprecated. Use <code>BatchGetDeploymentTargets</code>
|
|
30
30
|
* instead. </p>
|
|
31
|
-
*
|
|
32
|
-
*
|
|
31
|
+
* </note>
|
|
32
|
+
* <p> Returns an array of one or more instances associated with a deployment. This method
|
|
33
33
|
* works with EC2/On-premises and Lambda compute platforms. The newer
|
|
34
34
|
* <code>BatchGetDeploymentTargets</code> works with all compute platforms. The maximum
|
|
35
35
|
* number of instances that can be returned is 25.</p>
|
|
@@ -27,24 +27,24 @@ export interface BatchGetDeploymentTargetsCommandOutput extends BatchGetDeployme
|
|
|
27
27
|
* works with all compute types and should be used instead of the deprecated
|
|
28
28
|
* <code>BatchGetDeploymentInstances</code>. The maximum number of targets that can be
|
|
29
29
|
* returned is 25.</p>
|
|
30
|
-
*
|
|
30
|
+
* <p> The type of targets returned depends on the deployment's compute platform or
|
|
31
31
|
* deployment method: </p>
|
|
32
|
-
*
|
|
32
|
+
* <ul>
|
|
33
33
|
* <li>
|
|
34
|
-
*
|
|
35
|
-
*
|
|
34
|
+
* <p>
|
|
35
|
+
* <b>EC2/On-premises</b>: Information about Amazon EC2 instance targets. </p>
|
|
36
36
|
* </li>
|
|
37
37
|
* <li>
|
|
38
|
-
*
|
|
39
|
-
*
|
|
38
|
+
* <p>
|
|
39
|
+
* <b>Lambda</b>: Information about
|
|
40
40
|
* Lambda functions targets. </p>
|
|
41
41
|
* </li>
|
|
42
42
|
* <li>
|
|
43
|
-
*
|
|
44
|
-
*
|
|
43
|
+
* <p>
|
|
44
|
+
* <b>Amazon ECS</b>: Information about Amazon ECS service targets. </p>
|
|
45
45
|
* </li>
|
|
46
46
|
* <li>
|
|
47
|
-
*
|
|
47
|
+
* <p>
|
|
48
48
|
* <b>CloudFormation</b>: Information about
|
|
49
49
|
* targets of blue/green deployments initiated by a CloudFormation stack
|
|
50
50
|
* update.</p>
|
|
@@ -140,21 +140,21 @@ export interface CreateDeploymentCommandOutput extends CreateDeploymentOutput, _
|
|
|
140
140
|
*
|
|
141
141
|
* @throws {@link InvalidAlarmConfigException} (client fault)
|
|
142
142
|
* <p>The format of the alarm configuration is invalid. Possible causes include:</p>
|
|
143
|
-
*
|
|
143
|
+
* <ul>
|
|
144
144
|
* <li>
|
|
145
|
-
*
|
|
145
|
+
* <p>The alarm list is null.</p>
|
|
146
146
|
* </li>
|
|
147
147
|
* <li>
|
|
148
|
-
*
|
|
148
|
+
* <p>The alarm object is null.</p>
|
|
149
149
|
* </li>
|
|
150
150
|
* <li>
|
|
151
|
-
*
|
|
151
|
+
* <p>The alarm name is empty or null or exceeds the limit of 255 characters.</p>
|
|
152
152
|
* </li>
|
|
153
153
|
* <li>
|
|
154
|
-
*
|
|
154
|
+
* <p>Two alarms with the same name have been specified.</p>
|
|
155
155
|
* </li>
|
|
156
156
|
* <li>
|
|
157
|
-
*
|
|
157
|
+
* <p>The alarm configuration is enabled, but the alarm list is empty.</p>
|
|
158
158
|
* </li>
|
|
159
159
|
* </ul>
|
|
160
160
|
*
|
|
@@ -202,19 +202,19 @@ export interface CreateDeploymentCommandOutput extends CreateDeploymentOutput, _
|
|
|
202
202
|
*
|
|
203
203
|
* @throws {@link InvalidTargetInstancesException} (client fault)
|
|
204
204
|
* <p>The target instance configuration is invalid. Possible causes include:</p>
|
|
205
|
-
*
|
|
205
|
+
* <ul>
|
|
206
206
|
* <li>
|
|
207
|
-
*
|
|
207
|
+
* <p>Configuration data for target instances was entered for an in-place
|
|
208
208
|
* deployment.</p>
|
|
209
209
|
* </li>
|
|
210
210
|
* <li>
|
|
211
|
-
*
|
|
211
|
+
* <p>The limit of 10 tags for a tag type was exceeded.</p>
|
|
212
212
|
* </li>
|
|
213
213
|
* <li>
|
|
214
|
-
*
|
|
214
|
+
* <p>The combined length of the tag names exceeded the limit. </p>
|
|
215
215
|
* </li>
|
|
216
216
|
* <li>
|
|
217
|
-
*
|
|
217
|
+
* <p>A specified tag is not currently applied to any instances.</p>
|
|
218
218
|
* </li>
|
|
219
219
|
* </ul>
|
|
220
220
|
*
|
|
@@ -202,21 +202,21 @@ export interface CreateDeploymentGroupCommandOutput extends CreateDeploymentGrou
|
|
|
202
202
|
*
|
|
203
203
|
* @throws {@link InvalidAlarmConfigException} (client fault)
|
|
204
204
|
* <p>The format of the alarm configuration is invalid. Possible causes include:</p>
|
|
205
|
-
*
|
|
205
|
+
* <ul>
|
|
206
206
|
* <li>
|
|
207
|
-
*
|
|
207
|
+
* <p>The alarm list is null.</p>
|
|
208
208
|
* </li>
|
|
209
209
|
* <li>
|
|
210
|
-
*
|
|
210
|
+
* <p>The alarm object is null.</p>
|
|
211
211
|
* </li>
|
|
212
212
|
* <li>
|
|
213
|
-
*
|
|
213
|
+
* <p>The alarm name is empty or null or exceeds the limit of 255 characters.</p>
|
|
214
214
|
* </li>
|
|
215
215
|
* <li>
|
|
216
|
-
*
|
|
216
|
+
* <p>Two alarms with the same name have been specified.</p>
|
|
217
217
|
* </li>
|
|
218
218
|
* <li>
|
|
219
|
-
*
|
|
219
|
+
* <p>The alarm configuration is enabled, but the alarm list is empty.</p>
|
|
220
220
|
* </li>
|
|
221
221
|
* </ul>
|
|
222
222
|
*
|
|
@@ -24,10 +24,10 @@ export interface DeleteDeploymentConfigCommandOutput extends __MetadataBearer {
|
|
|
24
24
|
/**
|
|
25
25
|
* @public
|
|
26
26
|
* <p>Deletes a deployment configuration.</p>
|
|
27
|
-
*
|
|
27
|
+
* <note>
|
|
28
28
|
* <p>A deployment configuration cannot be deleted if it is currently in use. Predefined
|
|
29
29
|
* configurations cannot be deleted.</p>
|
|
30
|
-
*
|
|
30
|
+
* </note>
|
|
31
31
|
* @example
|
|
32
32
|
* Use a bare-bones client and the command you need to make an API call.
|
|
33
33
|
* ```javascript
|
|
@@ -24,12 +24,12 @@ export interface GetDeploymentCommandOutput extends GetDeploymentOutput, __Metad
|
|
|
24
24
|
/**
|
|
25
25
|
* @public
|
|
26
26
|
* <p>Gets information about a deployment.</p>
|
|
27
|
-
*
|
|
27
|
+
* <note>
|
|
28
28
|
* <p> The <code>content</code> property of the <code>appSpecContent</code> object in
|
|
29
29
|
* the returned revision is always null. Use <code>GetApplicationRevision</code> and
|
|
30
30
|
* the <code>sha256</code> property of the returned <code>appSpecContent</code> object
|
|
31
31
|
* to get the content of the deployment’s AppSpec file. </p>
|
|
32
|
-
*
|
|
32
|
+
* </note>
|
|
33
33
|
* @example
|
|
34
34
|
* Use a bare-bones client and the command you need to make an API call.
|
|
35
35
|
* ```javascript
|
|
@@ -30,8 +30,8 @@ export interface ListDeploymentInstancesCommandOutput extends ListDeploymentInst
|
|
|
30
30
|
* it works with all compute types. <code>ListDeploymentInstances</code> throws an
|
|
31
31
|
* exception if it is used with a compute platform other than EC2/On-premises or
|
|
32
32
|
* Lambda. </p>
|
|
33
|
-
*
|
|
34
|
-
*
|
|
33
|
+
* </note>
|
|
34
|
+
* <p> Lists the instance for a deployment associated with the IAM user or
|
|
35
35
|
* Amazon Web Services account. </p>
|
|
36
36
|
* @example
|
|
37
37
|
* Use a bare-bones client and the command you need to make an API call.
|
|
@@ -24,7 +24,7 @@ export interface ListOnPremisesInstancesCommandOutput extends ListOnPremisesInst
|
|
|
24
24
|
/**
|
|
25
25
|
* @public
|
|
26
26
|
* <p>Gets a list of names for one or more on-premises instances.</p>
|
|
27
|
-
*
|
|
27
|
+
* <p>Unless otherwise specified, both registered and deregistered on-premises instance
|
|
28
28
|
* names are listed. To list only registered or deregistered on-premises instance names,
|
|
29
29
|
* use the registration status parameter.</p>
|
|
30
30
|
* @example
|
|
@@ -24,9 +24,9 @@ export interface RegisterOnPremisesInstanceCommandOutput extends __MetadataBeare
|
|
|
24
24
|
/**
|
|
25
25
|
* @public
|
|
26
26
|
* <p>Registers an on-premises instance.</p>
|
|
27
|
-
*
|
|
27
|
+
* <note>
|
|
28
28
|
* <p>Only one IAM ARN (an IAM session ARN or IAM user ARN) is supported in the request. You cannot use both.</p>
|
|
29
|
-
*
|
|
29
|
+
* </note>
|
|
30
30
|
* @example
|
|
31
31
|
* Use a bare-bones client and the command you need to make an API call.
|
|
32
32
|
* ```javascript
|
|
@@ -202,21 +202,21 @@ export interface UpdateDeploymentGroupCommandOutput extends UpdateDeploymentGrou
|
|
|
202
202
|
*
|
|
203
203
|
* @throws {@link InvalidAlarmConfigException} (client fault)
|
|
204
204
|
* <p>The format of the alarm configuration is invalid. Possible causes include:</p>
|
|
205
|
-
*
|
|
205
|
+
* <ul>
|
|
206
206
|
* <li>
|
|
207
|
-
*
|
|
207
|
+
* <p>The alarm list is null.</p>
|
|
208
208
|
* </li>
|
|
209
209
|
* <li>
|
|
210
|
-
*
|
|
210
|
+
* <p>The alarm object is null.</p>
|
|
211
211
|
* </li>
|
|
212
212
|
* <li>
|
|
213
|
-
*
|
|
213
|
+
* <p>The alarm name is empty or null or exceeds the limit of 255 characters.</p>
|
|
214
214
|
* </li>
|
|
215
215
|
* <li>
|
|
216
|
-
*
|
|
216
|
+
* <p>Two alarms with the same name have been specified.</p>
|
|
217
217
|
* </li>
|
|
218
218
|
* <li>
|
|
219
|
-
*
|
|
219
|
+
* <p>The alarm configuration is enabled, but the alarm list is empty.</p>
|
|
220
220
|
* </li>
|
|
221
221
|
* </ul>
|
|
222
222
|
*
|
package/dist-types/index.d.ts
CHANGED
|
@@ -3,32 +3,32 @@
|
|
|
3
3
|
* to Amazon EC2 instances, on-premises instances running in your own facility,
|
|
4
4
|
* serverless Lambda functions, or applications in an Amazon ECS
|
|
5
5
|
* service.</p>
|
|
6
|
-
*
|
|
6
|
+
* <p>You can deploy a nearly unlimited variety of application content, such as an updated
|
|
7
7
|
* Lambda function, updated applications in an Amazon ECS service,
|
|
8
8
|
* code, web and configuration files, executables, packages, scripts, multimedia files, and
|
|
9
9
|
* so on. CodeDeploy can deploy application content stored in Amazon S3
|
|
10
10
|
* buckets, GitHub repositories, or Bitbucket repositories. You do not need to make changes
|
|
11
11
|
* to your existing code before you can use CodeDeploy.</p>
|
|
12
|
-
*
|
|
12
|
+
* <p>CodeDeploy makes it easier for you to rapidly release new features, helps
|
|
13
13
|
* you avoid downtime during application deployment, and handles the complexity of updating
|
|
14
14
|
* your applications, without many of the risks associated with error-prone manual
|
|
15
15
|
* deployments.</p>
|
|
16
|
-
*
|
|
16
|
+
* <p>
|
|
17
17
|
* <b>CodeDeploy Components</b>
|
|
18
|
-
*
|
|
19
|
-
*
|
|
20
|
-
*
|
|
18
|
+
* </p>
|
|
19
|
+
* <p>Use the information in this guide to help you work with the following CodeDeploy components:</p>
|
|
20
|
+
* <ul>
|
|
21
21
|
* <li>
|
|
22
|
-
*
|
|
23
|
-
*
|
|
22
|
+
* <p>
|
|
23
|
+
* <b>Application</b>: A name that uniquely identifies
|
|
24
24
|
* the application you want to deploy. CodeDeploy uses this name, which
|
|
25
25
|
* functions as a container, to ensure the correct combination of revision,
|
|
26
26
|
* deployment configuration, and deployment group are referenced during a
|
|
27
27
|
* deployment.</p>
|
|
28
28
|
* </li>
|
|
29
29
|
* <li>
|
|
30
|
-
*
|
|
31
|
-
*
|
|
30
|
+
* <p>
|
|
31
|
+
* <b>Deployment group</b>: A set of individual
|
|
32
32
|
* instances, CodeDeploy
|
|
33
33
|
* Lambda deployment configuration settings, or an Amazon ECS
|
|
34
34
|
* service and network details. A Lambda deployment group specifies how
|
|
@@ -38,20 +38,20 @@
|
|
|
38
38
|
* settings.</p>
|
|
39
39
|
* </li>
|
|
40
40
|
* <li>
|
|
41
|
-
*
|
|
42
|
-
*
|
|
41
|
+
* <p>
|
|
42
|
+
* <b>Deployment configuration</b>: A set of deployment
|
|
43
43
|
* rules and deployment success and failure conditions used by CodeDeploy during a deployment.</p>
|
|
44
44
|
* </li>
|
|
45
45
|
* <li>
|
|
46
|
-
*
|
|
47
|
-
*
|
|
46
|
+
* <p>
|
|
47
|
+
* <b>Deployment</b>: The process and the components used
|
|
48
48
|
* when updating a Lambda function, a containerized application in an
|
|
49
49
|
* Amazon ECS service, or of installing content on one or more
|
|
50
50
|
* instances. </p>
|
|
51
51
|
* </li>
|
|
52
52
|
* <li>
|
|
53
|
-
*
|
|
54
|
-
*
|
|
53
|
+
* <p>
|
|
54
|
+
* <b>Application revisions</b>: For an Lambda deployment, this is an AppSpec file that specifies the
|
|
55
55
|
* Lambda function to be updated and one or more functions to
|
|
56
56
|
* validate deployment lifecycle events. For an Amazon ECS deployment, this
|
|
57
57
|
* is an AppSpec file that specifies the Amazon ECS task definition,
|
|
@@ -63,33 +63,33 @@
|
|
|
63
63
|
* identified by its commit ID.</p>
|
|
64
64
|
* </li>
|
|
65
65
|
* </ul>
|
|
66
|
-
*
|
|
66
|
+
* <p>This guide also contains information to help you get details about the instances in
|
|
67
67
|
* your deployments, to make on-premises instances available for CodeDeploy
|
|
68
68
|
* deployments, to get details about a Lambda function deployment, and to get
|
|
69
69
|
* details about Amazon ECS service deployments.</p>
|
|
70
|
-
*
|
|
70
|
+
* <p>
|
|
71
71
|
* <b>CodeDeploy Information Resources</b>
|
|
72
72
|
* </p>
|
|
73
|
-
*
|
|
73
|
+
* <ul>
|
|
74
74
|
* <li>
|
|
75
|
-
*
|
|
75
|
+
* <p>
|
|
76
76
|
* <a href="https://docs.aws.amazon.com/codedeploy/latest/userguide">CodeDeploy User Guide</a>
|
|
77
77
|
* </p>
|
|
78
78
|
* </li>
|
|
79
79
|
* <li>
|
|
80
|
-
*
|
|
80
|
+
* <p>
|
|
81
81
|
* <a href="https://docs.aws.amazon.com/codedeploy/latest/APIReference/">CodeDeploy API Reference Guide</a>
|
|
82
82
|
* </p>
|
|
83
83
|
* </li>
|
|
84
84
|
* <li>
|
|
85
|
-
*
|
|
85
|
+
* <p>
|
|
86
86
|
* <a href="https://docs.aws.amazon.com/cli/latest/reference/deploy/index.html">CLI Reference for CodeDeploy</a>
|
|
87
87
|
* </p>
|
|
88
88
|
* </li>
|
|
89
89
|
* <li>
|
|
90
|
-
*
|
|
91
|
-
*
|
|
92
|
-
*
|
|
90
|
+
* <p>
|
|
91
|
+
* <a href="https://forums.aws.amazon.com/forum.jspa?forumID=179">CodeDeploy Developer Forum</a>
|
|
92
|
+
* </p>
|
|
93
93
|
* </li>
|
|
94
94
|
* </ul>
|
|
95
95
|
*
|