Skip to content

Commit

Permalink
Update to latest models
Browse files Browse the repository at this point in the history
  • Loading branch information
aws-sdk-python-automation committed Feb 4, 2019
1 parent 1ae092e commit ab3f900
Show file tree
Hide file tree
Showing 8 changed files with 159 additions and 51 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"category": "``application-autoscaling``",
"type": "api-change",
"description": "Update application-autoscaling client to latest version"
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-codecommit-90523.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"category": "``codecommit``",
"type": "api-change",
"description": "Update codecommit client to latest version"
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-ecs-62440.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"category": "``ecs``",
"type": "api-change",
"description": "Update ecs client to latest version"
}
5 changes: 5 additions & 0 deletions .changes/next-release/api-change-workspaces-62169.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"category": "``workspaces``",
"type": "api-change",
"description": "Update workspaces client to latest version"
}
96 changes: 48 additions & 48 deletions botocore/data/application-autoscaling/2016-02-06/service-2.json

Large diffs are not rendered by default.

1 change: 1 addition & 0 deletions botocore/data/codecommit/2015-04-13/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -619,6 +619,7 @@
{"shape":"TipOfSourceReferenceIsDifferentException"},
{"shape":"ReferenceDoesNotExistException"},
{"shape":"InvalidCommitIdException"},
{"shape":"RepositoryNotAssociatedWithPullRequestException"},
{"shape":"RepositoryNameRequiredException"},
{"shape":"InvalidRepositoryNameException"},
{"shape":"RepositoryDoesNotExistException"},
Expand Down
88 changes: 86 additions & 2 deletions botocore/data/ecs/2014-11-13/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -907,6 +907,22 @@
"healthStatus":{
"shape":"HealthStatus",
"documentation":"<p>The health status of the container. If health checks are not configured for this container in its task definition, then it reports the health status as <code>UNKNOWN</code>.</p>"
},
"cpu":{
"shape":"String",
"documentation":"<p>The number of CPU units set for the container. The value will be <code>0</code> if no value was specified in the container definition when the task definition was registered.</p>"
},
"memory":{
"shape":"String",
"documentation":"<p>The hard limit (in MiB) of memory set for the container.</p>"
},
"memoryReservation":{
"shape":"String",
"documentation":"<p>The soft limit (in MiB) of memory set for the container.</p>"
},
"gpuIds":{
"shape":"GpuIds",
"documentation":"<p>The IDs of each GPU assigned to the container.</p>"
}
},
"documentation":"<p>A Docker container that is part of a task.</p>"
Expand Down Expand Up @@ -1045,6 +1061,10 @@
"systemControls":{
"shape":"SystemControls",
"documentation":"<p>A list of namespaced kernel parameters to set in the container. This parameter maps to <code>Sysctls</code> in the <a href=\"https://docs.docker.com/engine/api/v1.35/#operation/ContainerCreate\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.35/\">Docker Remote API</a> and the <code>--sysctl</code> option to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>.</p> <note> <p>It is not recommended that you specify network-related <code>systemControls</code> parameters for multiple containers in a single task that also uses either the <code>awsvpc</code> or <code>host</code> network modes. For tasks that use the <code>awsvpc</code> network mode, the container that is started last determines which <code>systemControls</code> parameters take effect. For tasks that use the <code>host</code> network mode, it changes the container instance's namespaced kernel parameters as well as the containers.</p> </note>"
},
"resourceRequirements":{
"shape":"ResourceRequirements",
"documentation":"<p>The type and amount of a resource to assign to a container. The only supported resource is a GPU.</p>"
}
},
"documentation":"<p>Container definitions are used in task definitions to describe the different containers that are launched as part of a task.</p>"
Expand Down Expand Up @@ -1164,6 +1184,10 @@
"memoryReservation":{
"shape":"BoxedInteger",
"documentation":"<p>The soft limit (in MiB) of memory to reserve for the container, instead of the default value from the task definition. You must also specify a container name.</p>"
},
"resourceRequirements":{
"shape":"ResourceRequirements",
"documentation":"<p>The type and amount of a resource to assign to a container, instead of the default value from the task definition. The only supported resource is a GPU.</p>"
}
},
"documentation":"<p>The overrides that should be sent to a container.</p>"
Expand Down Expand Up @@ -1313,7 +1337,7 @@
},
"propagateTags":{
"shape":"PropagateTags",
"documentation":"<p>Specifies whether to propagate the tags from the task definition or the service to the tasks. If no value is specified, the tags are not propagated. Tags can only be propagated to the tasks within the service during service creation. To add tags to a task after service creation, use the <a>TagResource</a> API action.</p>"
"documentation":"<p>Specifies whether to propagate the tags from the task definition or the service to the tasks in the service. If no value is specified, the tags are not propagated. Tags can only be propagated to the tasks within the service during service creation. To add tags to a task after service creation, use the <a>TagResource</a> API action.</p>"
}
}
},
Expand Down Expand Up @@ -1819,6 +1843,10 @@
"type":"list",
"member":{"shape":"Failure"}
},
"GpuIds":{
"type":"list",
"member":{"shape":"String"}
},
"HealthCheck":{
"type":"structure",
"required":["command"],
Expand Down Expand Up @@ -2515,6 +2543,32 @@
"binpack"
]
},
"PlatformDevice":{
"type":"structure",
"required":[
"id",
"type"
],
"members":{
"id":{
"shape":"String",
"documentation":"<p>The ID for the GPU(s) on the container instance. The available GPU IDs can also be obtained on the container instance in the <code>/var/lib/ecs/gpu/nvidia_gpu_info.json</code> file.</p>"
},
"type":{
"shape":"PlatformDeviceType",
"documentation":"<p>The type of device that is available on the container instance. The only supported value is <code>GPU</code>.</p>"
}
},
"documentation":"<p>The devices that are available on the container instance. The only supported device type is a GPU.</p>"
},
"PlatformDeviceType":{
"type":"string",
"enum":["GPU"]
},
"PlatformDevices":{
"type":"list",
"member":{"shape":"PlatformDevice"}
},
"PlatformTaskDefinitionIncompatibilityException":{
"type":"structure",
"members":{
Expand Down Expand Up @@ -2642,6 +2696,10 @@
"shape":"Attributes",
"documentation":"<p>The container instance attributes that this container instance supports.</p>"
},
"platformDevices":{
"shape":"PlatformDevices",
"documentation":"<p>The devices that are available on the container instance. The only supported device type is a GPU.</p>"
},
"tags":{
"shape":"Tags",
"documentation":"<p>The metadata that you apply to the container instance to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. Tag keys can have a maximum character length of 128 characters, and tag values can have a maximum length of 256 characters.</p>"
Expand Down Expand Up @@ -2783,6 +2841,32 @@
"documentation":"<p>The specified resource could not be found.</p>",
"exception":true
},
"ResourceRequirement":{
"type":"structure",
"required":[
"value",
"type"
],
"members":{
"value":{
"shape":"String",
"documentation":"<p>The number of GPUs to assign to a container.</p>"
},
"type":{
"shape":"ResourceType",
"documentation":"<p>The type of resource a container desires. The only supported value is <code>GPU</code>.</p>"
}
},
"documentation":"<p>The type and amount of a resource to assign to a container. The only supported resource is a GPU.</p>"
},
"ResourceRequirements":{
"type":"list",
"member":{"shape":"ResourceRequirement"}
},
"ResourceType":{
"type":"string",
"enum":["GPU"]
},
"Resources":{
"type":"list",
"member":{"shape":"Resource"}
Expand Down Expand Up @@ -2845,7 +2929,7 @@
},
"propagateTags":{
"shape":"PropagateTags",
"documentation":"<p>Specifies whether to propagate the tags from the task definition or the service to the task. If no value is specified, the tags are not propagated.</p>"
"documentation":"<p>Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags are not propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the <a>TagResource</a> API action.</p> <note> <p>An error will be received if you specify the <code>SERVICE</code> option when running a task.</p> </note>"
}
}
},
Expand Down
5 changes: 4 additions & 1 deletion botocore/data/workspaces/2015-04-08/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -1372,7 +1372,10 @@
},
"ModifyClientPropertiesRequest":{
"type":"structure",
"required":["ResourceId"],
"required":[
"ResourceId",
"ClientProperties"
],
"members":{
"ResourceId":{
"shape":"NonEmptyString",
Expand Down

0 comments on commit ab3f900

Please sign in to comment.