mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
fbcd6f8a65
Fargate instances do not require memory and cpu descriptors. EC2 instances do require descriptions. https://botocore.readthedocs.io/en/latest/reference/services/ecs.html#ECS.Client.describe_task_definition Fargate requires that cpu and memory be defined at task definition level. EC2 launch requires them to be defined at the container level. Fargate requires the use of awsvpc for the networking_mode. Also updated, the documentation regarding where and when memory/cpu needs to the assigned. The task_definition variable for the awspvc configuration colided with the ecs_service for the bridge network. This would cause the test to fail. Add testing for fargate Add examples for fargate and ec2 |
||
|---|---|---|
| .. | ||
| host_vars | ||
| targets | ||
| cloud-config-aws.yml.template | ||
| cloud-config-azure.yml.template | ||
| cloud-config-cs.ini.template | ||
| cloud-config-gcp.yml.template | ||
| cloud-config-opennebula.yml.template | ||
| cloud-config-openshift.kubeconfig.template | ||
| cloud-config-tower.cfg.template | ||
| integration.cfg | ||
| integration_config.yml | ||
| inventory | ||
| inventory.networking.template | ||
| inventory.remote.template | ||
| inventory.winrm.template | ||
| network-integration.cfg | ||
| target-prefixes.network | ||
| windows-integration.cfg | ||