list_deployment_instances
async
¶
list_deployment_instances(
deployment_id: DeploymentId,
*,
config_overrides: Optional[AsyncCodeDeployClientConfig] = None,
next_token: Optional[NextToken] = None,
instance_status_filter: Optional[InstanceStatusList] = None,
instance_type_filter: Optional[InstanceTypeList] = None,
) -> ListDeploymentInstancesOutput
The newer BatchGetDeploymentTargets should be used instead because it works with all compute types. ListDeploymentInstances throws an exception if it is used with a compute platform other than EC2/On-premises or Lambda.
Lists the instance for a deployment associated with the user or Amazon Web Services account.
Parameters:
-
deployment_id(DeploymentId) –The unique ID of a deployment.
-
next_token(Optional[NextToken], default:None) –An identifier returned from the previous list deployment instances call. It can be used to return the next set of deployment instances in the list.
-
instance_status_filter(Optional[InstanceStatusList], default:None) –A subset of instances to list by status:
-
Pending: Include those instances with pending deployments. -
InProgress: Include those instances where deployments are still in progress. -
Succeeded: Include those instances with successful deployments. -
Failed: Include those instances with failed deployments. -
Skipped: Include those instances with skipped deployments. -
Unknown: Include those instances with deployments in an unknown state.
-
-
instance_type_filter(Optional[InstanceTypeList], default:None) –The set of instances in a blue/green deployment, either those in the original environment ("BLUE") or those in the replacement environment ("GREEN"), for which you want to view instance information.
Raises:
-
ApplicationDoesNotExistException–The application does not exist with the user or Amazon Web Services account.
-
DeploymentDoesNotExistException–The deployment with the user or Amazon Web Services account does not exist.
-
DeploymentGroupDoesNotExistException–The named deployment group with the user or Amazon Web Services account does not exist.
-
DeploymentIdRequiredException–At least one deployment ID must be specified.
-
DeploymentNotStartedException–The specified deployment has not started.
-
InvalidComputePlatformException–The computePlatform is invalid. The computePlatform should be
Lambda,Server, orECS. -
InvalidDeploymentIdException–At least one of the deployment IDs was specified in an invalid format.
-
InvalidDeploymentInstanceTypeException–An instance type was specified for an in-place deployment. Instance types are supported for blue/green deployments only.
-
InvalidInstanceStatusException–The specified instance status does not exist.
-
InvalidInstanceTypeException–An invalid instance type was specified for instances in a blue/green deployment. Valid values include "Blue" for an original environment and "Green" for a replacement environment.
-
InvalidNextTokenException–The next token was specified in an invalid format.
-
InvalidTargetFilterNameException–The target filter name is invalid.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_codedeploy/_services/async_code_deploy.py
2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 | |