Prepare for release (#1426) (d99d3e0c) · Commits · Public Repositories / Smithy Rust

aws/sdk/aws-models/apigateway.json

+694 −600

File changed.

Preview size limit exceeded, changes collapsed.

aws/sdk/aws-models/appflow.json

+85 −57

File changed.

Preview size limit exceeded, changes collapsed.

aws/sdk/aws-models/appmesh.json

+153 −106

File changed.

Preview size limit exceeded, changes collapsed.

aws/sdk/aws-models/apprunner.json

+2 −2

Original line number	Diff line number	Diff line
		@@ -549,7 +549,7 @@
		"CodeConfiguration": {
		"target": "com.amazonaws.apprunner#CodeConfiguration",
		"traits": {
		"smithy.api#documentation": "<p>Configuration for building and running the service from a source code repository.</p>"
		"smithy.api#documentation": "<p>Configuration for building and running the service from a source code repository.</p>\n <note>\n <p>\n <code>CodeConfiguration</code> is required only for <code>CreateService</code> request.</p>\n </note>"
		}
		}
		},
		@@ -1026,7 +1026,7 @@
		"Subnets": {
		"target": "com.amazonaws.apprunner#StringList",
		"traits": {
		"smithy.api#documentation": "<p>A list of IDs of subnets that App Runner should use when it associates your service with a custom Amazon VPC. Specify IDs of subnets of a single\n Amazon VPC. App Runner determines the Amazon VPC from the subnets you specify.</p>",
		"smithy.api#documentation": "<p>A list of IDs of subnets that App Runner should use when it associates your service with a custom Amazon VPC. Specify IDs of subnets of a single\n Amazon VPC. App Runner determines the Amazon VPC from the subnets you specify.</p>\n <note>\n <p>\n App Runner currently only provides support for IPv4.\n </p>\n </note>",
		"smithy.api#required": {}
		}
		},

aws/sdk/aws-models/batch.json

+8 −3

Original line number	Diff line number	Diff line
		@@ -688,7 +688,7 @@
		"tags": {
		"target": "com.amazonaws.batch#TagsMap",
		"traits": {
		"smithy.api#documentation": "<p>Key-value pair tags to be applied to EC2 resources that are launched in the compute environment. For Batch,\n these take the form of \"String1\": \"String2\", where String1 is the tag key and String2 is the tag value−for\n example, <code>{ \"Name\": \"Batch Instance - C4OnDemand\" }</code>. This is helpful for recognizing your Batch\n instances in the Amazon EC2 console. These tags can't be updated or removed after the compute environment is created. Any\n changes to these tags require that you create a new compute environment and remove the old compute environment. These\n tags aren't seen when using the Batch <code>ListTagsForResource</code> API operation.</p>\n <note>\n <p>This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.</p>\n </note>"
		"smithy.api#documentation": "<p>Key-value pair tags to be applied to EC2 resources that are launched in the compute environment. For Batch,\n these take the form of \"String1\": \"String2\", where String1 is the tag key and String2 is the tag value−for\n example, <code>{ \"Name\": \"Batch Instance - C4OnDemand\" }</code>. This is helpful for recognizing your Batch\n instances in the Amazon EC2 console. Updating these tags requires an infrastructure update to the compute environment. For\n more information, see <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html\">Updating compute\n environments</a> in the <i>Batch User Guide</i>. These tags aren't seen when using the Batch\n <code>ListTagsForResource</code> API operation.</p>\n <note>\n <p>This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.</p>\n </note>"
		}
		},
		"placementGroup": {
		@@ -1221,7 +1221,7 @@
		}
		],
		"traits": {
		"smithy.api#documentation": "<p>Creates an Batch compute environment. You can create <code>MANAGED</code> or <code>UNMANAGED</code> compute\n environments. <code>MANAGED</code> compute environments can use Amazon EC2 or Fargate resources.\n <code>UNMANAGED</code> compute environments can only use EC2 resources.</p>\n <p>In a managed compute environment, Batch manages the capacity and instance types of the compute resources\n within the environment. This is based on the compute resource specification that you define or the <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html\">launch template</a> that you\n specify when you create the compute environment. Either, you can choose to use EC2 On-Demand Instances and EC2 Spot\n Instances. Or, you can use Fargate and Fargate Spot capacity in your managed compute environment. You can\n optionally set a maximum price so that Spot Instances only launch when the Spot Instance price is less than a\n specified percentage of the On-Demand price.</p>\n <note>\n <p>Multi-node parallel jobs aren't supported on Spot Instances.</p>\n </note>\n <p>In an unmanaged compute environment, you can manage your own EC2 compute resources and have a lot of flexibility\n with how you configure your compute resources. For example, you can use custom AMIs. However, you must verify that\n each of your AMIs meet the Amazon ECS container instance AMI specification. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_instance_AMIs.html\">container instance AMIs</a> in the\n <i>Amazon Elastic Container Service Developer Guide</i>. After you created your unmanaged compute environment, you can use the <a>DescribeComputeEnvironments</a> operation to find the Amazon ECS cluster that's associated with it. Then, launch\n 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\n <i>Amazon Elastic Container Service Developer Guide</i>.</p>\n <note>\n <p>Batch doesn't upgrade the AMIs in a compute environment after the environment is created. For example, it\n doesn't update the AMIs when a newer version of the Amazon ECS optimized AMI is available. Therefore, you're responsible\n for managing the guest operating system (including its updates and security patches) and any additional application\n software or utilities that you install on the compute resources. To use a new AMI for your Batch jobs, complete\n these steps:</p>\n <ol>\n <li>\n <p>Create a new compute environment with the new AMI.</p>\n </li>\n <li>\n <p>Add the compute environment to an existing job queue.</p>\n </li>\n <li>\n <p>Remove the earlier compute environment from your job queue.</p>\n </li>\n <li>\n <p>Delete the earlier compute environment.</p>\n </li>\n </ol>\n </note>",
		"smithy.api#documentation": "<p>Creates an Batch compute environment. You can create <code>MANAGED</code> or <code>UNMANAGED</code> compute\n environments. <code>MANAGED</code> compute environments can use Amazon EC2 or Fargate resources.\n <code>UNMANAGED</code> compute environments can only use EC2 resources.</p>\n <p>In a managed compute environment, Batch manages the capacity and instance types of the compute resources\n within the environment. This is based on the compute resource specification that you define or the <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html\">launch template</a> that you\n specify when you create the compute environment. Either, you can choose to use EC2 On-Demand Instances and EC2 Spot\n Instances. Or, you can use Fargate and Fargate Spot capacity in your managed compute environment. You can\n optionally set a maximum price so that Spot Instances only launch when the Spot Instance price is less than a\n specified percentage of the On-Demand price.</p>\n <note>\n <p>Multi-node parallel jobs aren't supported on Spot Instances.</p>\n </note>\n <p>In an unmanaged compute environment, you can manage your own EC2 compute resources and have a lot of flexibility\n with how you configure your compute resources. For example, you can use custom AMIs. However, you must verify that\n each of your AMIs meet the Amazon ECS container instance AMI specification. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_instance_AMIs.html\">container instance AMIs</a> in the\n <i>Amazon Elastic Container Service Developer Guide</i>. After you created your unmanaged compute environment, you can use the <a>DescribeComputeEnvironments</a> operation to find the Amazon ECS cluster that's associated with it. Then, launch\n 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\n <i>Amazon Elastic Container Service Developer Guide</i>.</p>\n <note>\n <p>Batch doesn't automatically upgrade the AMIs in a compute environment after it's created. For example, it\n also doesn't update the AMIs in your compute environment when a newer version of the Amazon ECS optimized AMI is\n available. You're responsible for the management of the guest operating system. This includes any updates and\n security patches. You're also responsible for any additional application software or utilities that you install on\n the compute resources. There are two ways to use a new AMI for your Batch jobs. The original method is to complete\n these steps:</p>\n <ol>\n <li>\n <p>Create a new compute environment with the new AMI.</p>\n </li>\n <li>\n <p>Add the compute environment to an existing job queue.</p>\n </li>\n <li>\n <p>Remove the earlier compute environment from your job queue.</p>\n </li>\n <li>\n <p>Delete the earlier compute environment.</p>\n </li>\n </ol>\n <p>In April 2022, Batch added enhanced support for updating compute environments. For more information, see\n <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/updating-compute-environments.html\">Updating compute\n environments</a>. To use the enhanced updating of compute environments to update AMIs, follow these\n rules:</p>\n <ul>\n <li>\n <p>Either do not set the service role (<code>serviceRole</code>) parameter or set it to the <b>AWSBatchServiceRole</b> service-linked role.</p>\n </li>\n <li>\n <p>Set the allocation strategy (<code>allocationStrategy</code>) parameter to <code>BEST_FIT_PROGRESSIVE</code>\n or <code>SPOT_CAPACITY_OPTIMIZED</code>.</p>\n </li>\n <li>\n <p>Set the update to latest image version (<code>updateToLatestImageVersion</code>) parameter to\n <code>true</code>.</p>\n </li>\n <li>\n <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\">\n <code>ec2Configuration</code>\n </a>), or in the launch template (<code>launchTemplate</code>). In that case\n Batch will select the latest Amazon ECS optimized AMI supported by Batch at the time the infrastructure update is\n initiated. Alternatively you can specify the AMI ID in the <code>imageId</code> or <code>imageIdOverride</code>\n parameters, or the launch template identified by the <code>LaunchTemplate</code> properties. Changing any of these\n properties will trigger an infrastructure update. If the AMI ID is specified in the launch template, it can not be\n replaced by specifying an AMI ID in either the <code>imageId</code> or <code>imageIdOverride</code> parameters. It\n can only be replaced by specifying a different launch template, or if the launch template version is set to\n <code>$Default</code> or <code>$Latest</code>, by setting either a new default version for the launch template\n (if <code>$Default</code>)or by adding a new version to the launch template (if <code>$Latest</code>).</p>\n </li>\n </ul>\n <p>If these rules are followed, any update that triggers an infrastructure update will cause the AMI ID to be\n re-selected. If the <code>version</code> setting in the launch template (<code>launchTemplate</code>) is set to\n <code>$Latest</code> or <code>$Default</code>, the latest or default version of the launch template will be\n evaluated up at the time of the infrastructure update, even if the <code>launchTemplate</code> was not\n updated.</p>\n </note>",
		"smithy.api#http": {
		"method": "POST",
		"uri": "/v1/createcomputeenvironment",
		@@ -1659,6 +1659,7 @@
		"smithy.api#paginated": {
		"inputToken": "nextToken",
		"outputToken": "nextToken",
		"items": "computeEnvironments",
		"pageSize": "maxResults"
		}
		}
		@@ -1732,6 +1733,7 @@
		"smithy.api#paginated": {
		"inputToken": "nextToken",
		"outputToken": "nextToken",
		"items": "jobDefinitions",
		"pageSize": "maxResults"
		}
		}
		@@ -1817,6 +1819,7 @@
		"smithy.api#paginated": {
		"inputToken": "nextToken",
		"outputToken": "nextToken",
		"items": "jobQueues",
		"pageSize": "maxResults"
		}
		}
		@@ -2977,6 +2980,7 @@
		"smithy.api#paginated": {
		"inputToken": "nextToken",
		"outputToken": "nextToken",
		"items": "jobSummaryList",
		"pageSize": "maxResults"
		}
		}
		@@ -3081,6 +3085,7 @@
		"smithy.api#paginated": {
		"inputToken": "nextToken",
		"outputToken": "nextToken",
		"items": "schedulingPolicies",
		"pageSize": "maxResults"
		}
		}
		@@ -3900,7 +3905,7 @@
		"shareIdentifier": {
		"target": "com.amazonaws.batch#String",
		"traits": {
		"smithy.api#documentation": "<p>The share identifier for the job.</p>"
		"smithy.api#documentation": "<p>The share identifier for the job. If the job queue does not have a scheduling policy, then this parameter must\n not be specified. If the job queue has a scheduling policy, then this parameter must be specified.</p>"
		}
		},
		"schedulingPriorityOverride": {