Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

Deployment

import type { Deployment } from "https://aws-api.deno.dev/v0.4/services/ecs.ts?docs=full";

The details of an Amazon ECS service deployment. This is used only when a service uses the ECS deployment controller type.

interface Deployment {
capacityProviderStrategy?: CapacityProviderStrategyItem[] | null;
createdAt?: Date | number | null;
desiredCount?: number | null;
failedTasks?: number | null;
id?: string | null;
launchType?: LaunchType | null;
networkConfiguration?: NetworkConfiguration | null;
pendingCount?: number | null;
platformFamily?: string | null;
platformVersion?: string | null;
rolloutState?: DeploymentRolloutState | null;
rolloutStateReason?: string | null;
runningCount?: number | null;
serviceConnectConfiguration?: ServiceConnectConfiguration | null;
serviceConnectResources?: ServiceConnectServiceResource[] | null;
status?: string | null;
taskDefinition?: string | null;
updatedAt?: Date | number | null;
}

§Properties

§
capacityProviderStrategy?: CapacityProviderStrategyItem[] | null
[src]

The capacity provider strategy that the deployment is using.

§
createdAt?: Date | number | null
[src]

The Unix timestamp for the time when the service deployment was created.

§
desiredCount?: number | null
[src]

The most recent desired count of tasks that was specified for the service to deploy or maintain.

§
failedTasks?: number | null
[src]

The number of consecutively failed tasks in the deployment. A task is considered a failure if the service scheduler can't launch the task, the task doesn't transition to a RUNNING state, or if it fails any of its defined health checks and is stopped.

Note: Once a service deployment has one or more successfully running tasks, the failed task count resets to zero and stops being evaluated.

§
id?: string | null
[src]

The ID of the deployment.

§
launchType?: LaunchType | null
[src]

The launch type the tasks in the service are using. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide.

§
networkConfiguration?: NetworkConfiguration | null
[src]

The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.

§
pendingCount?: number | null
[src]

The number of tasks in the deployment that are in the PENDING status.

§
platformFamily?: string | null
[src]

The operating system that your tasks in the service, or tasks are running on. A platform family is specified only for tasks using the Fargate launch type.

All tasks that run as part of this service must use the same platformFamily value as the service, for example, LINUX..

§
platformVersion?: string | null
[src]

The platform version that your tasks in the service run on. A platform version is only specified for tasks using the Fargate launch type. If one isn't specified, the LATEST platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.

§
rolloutState?: DeploymentRolloutState | null
[src]

Note: The rolloutState of a service is only returned for services that use the rolling update (ECS) deployment type that aren't behind a Classic Load Balancer.

The rollout state of the deployment. When a service deployment is started, it begins in an IN_PROGRESS state. When the service reaches a steady state, the deployment transitions to a COMPLETED state. If the service fails to reach a steady state and circuit breaker is enabled, the deployment transitions to a FAILED state. A deployment in FAILED state doesn't launch any new tasks. For more information, see "DeploymentCircuitBreaker".

§
rolloutStateReason?: string | null
[src]

A description of the rollout state of a deployment.

§
runningCount?: number | null
[src]

The number of tasks in the deployment that are in the RUNNING status.

§
serviceConnectConfiguration?: ServiceConnectConfiguration | null
[src]

The details of the Service Connect configuration that's used by this deployment. Compare the configuration between multiple deployments when troubleshooting issues with new deployments.

The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace.

Tasks that run in a namespace can use short names to connect to services in the namespace. Tasks can connect to services across all of the clusters in the namespace. Tasks connect through a managed proxy container that collects logs and metrics for increased visibility. Only the tasks that Amazon ECS services create are supported with Service Connect. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.

§
serviceConnectResources?: ServiceConnectServiceResource[] | null
[src]

The list of Service Connect resources that are associated with this deployment. Each list entry maps a discovery name to a Cloud Map service name.

§
status?: string | null
[src]

The status of the deployment. The following describes each state.

PRIMARY: The most recent deployment of a service.

ACTIVE: A service deployment that still has running tasks, but are in the process of being replaced with a new PRIMARY deployment.

INACTIVE: A deployment that has been completely replaced.

§
taskDefinition?: string | null
[src]

The most recent task definition that was specified for the tasks in the service to use.

§
updatedAt?: Date | number | null
[src]

The Unix timestamp for the time when the service deployment was last updated.