« blib/lib/Paws/ECS/DeploymentConfiguration.pm
↑ Summary
blib/lib/Paws/ECS/DeregisterContainerInstance.pm »
| 1 | # Generated by default/object.tt | ||
| 2 | package Paws::ECS::DeploymentController; | ||
| 3 | use Moose; | ||
| 4 | has Type => (is => 'ro', isa => 'Str', request_name => 'type', traits => ['NameInRequest'], required => 1); | ||
| 5 | |||
| 6 | 1; | ||
| 7 | |||
| 8 | ### main pod documentation begin ### | ||
| 9 | |||
| 10 | =head1 NAME | ||
| 11 | |||
| 12 | Paws::ECS::DeploymentController | ||
| 13 | |||
| 14 | =head1 USAGE | ||
| 15 | |||
| 16 | This class represents one of two things: | ||
| 17 | |||
| 18 | =head3 Arguments in a call to a service | ||
| 19 | |||
| 20 | Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. | ||
| 21 | Each attribute should be used as a named argument in the calls that expect this type of object. | ||
| 22 | |||
| 23 | As an example, if Att1 is expected to be a Paws::ECS::DeploymentController object: | ||
| 24 | |||
| 25 | $service_obj->Method(Att1 => { Type => $value, ..., Type => $value }); | ||
| 26 | |||
| 27 | =head3 Results returned from an API call | ||
| 28 | |||
| 29 | Use accessors for each attribute. If Att1 is expected to be an Paws::ECS::DeploymentController object: | ||
| 30 | |||
| 31 | $result = $service_obj->Method(...); | ||
| 32 | $result->Att1->Type | ||
| 33 | |||
| 34 | =head1 DESCRIPTION | ||
| 35 | |||
| 36 | The deployment controller to use for the service. For more information, | ||
| 37 | see Amazon ECS Deployment Types | ||
| 38 | (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html) | ||
| 39 | in the I<Amazon Elastic Container Service Developer Guide>. | ||
| 40 | |||
| 41 | =head1 ATTRIBUTES | ||
| 42 | |||
| 43 | |||
| 44 | =head2 B<REQUIRED> Type => Str | ||
| 45 | |||
| 46 | The deployment controller type to use. | ||
| 47 | |||
| 48 | There are three deployment controller types available: | ||
| 49 | |||
| 50 | =over | ||
| 51 | |||
| 52 | =item ECS | ||
| 53 | |||
| 54 | The rolling update (C<ECS>) deployment type involves replacing the | ||
| 55 | current running version of the container with the latest version. The | ||
| 56 | number of containers Amazon ECS adds or removes from the service during | ||
| 57 | a rolling update is controlled by adjusting the minimum and maximum | ||
| 58 | number of healthy tasks allowed during a service deployment, as | ||
| 59 | specified in the DeploymentConfiguration. | ||
| 60 | |||
| 61 | =item CODE_DEPLOY | ||
| 62 | |||
| 63 | The blue/green (C<CODE_DEPLOY>) deployment type uses the blue/green | ||
| 64 | deployment model powered by AWS CodeDeploy, which allows you to verify | ||
| 65 | a new deployment of a service before sending production traffic to it. | ||
| 66 | |||
| 67 | =item EXTERNAL | ||
| 68 | |||
| 69 | The external (C<EXTERNAL>) deployment type enables you to use any | ||
| 70 | third-party deployment controller for full control over the deployment | ||
| 71 | process for an Amazon ECS service. | ||
| 72 | |||
| 73 | =back | ||
| 74 | |||
| 75 | |||
| 76 | |||
| 77 | |||
| 78 | =head1 SEE ALSO | ||
| 79 | |||
| 80 | This class forms part of L<Paws>, describing an object used in L<Paws::ECS> | ||
| 81 | |||
| 82 | =head1 BUGS and CONTRIBUTIONS | ||
| 83 | |||
| 84 | The source code is located here: L<https://github.com/pplu/aws-sdk-perl> | ||
| 85 | |||
| 86 | Please report bugs to: L<https://github.com/pplu/aws-sdk-perl/issues> | ||
| 87 | |||
| 88 | =cut | ||
| 89 |