ansible

Commit Graph

Author	SHA1	Message	Date
Sloane Hertel	c4a6bce69f	ecs_service: make assign_public_ip option a boolean (#41759 )	6 years ago
Sloane Hertel	1268ce4d4f	[ecs_service] fix assign_public_ip network configuration to module parameter rather than fixed string (#41689 ) Fix parameter name Use suboptions document suboptions Add a test to assert assign_public_ip is configurable	6 years ago
Deepakkothandan	5a72eef0a3	[ecs_service] fix assign_public ip for network configuration (#41685 ) * fix assign_public ip for ecs_service * used module.botocore_at_least instead of distutils	6 years ago
Will Thames	a60fe1946c	Remove ECS policies from AWS compute policy The compute policy was exceeding maximum size and contained policies that already exist in ecs-policy. Look up suitable AMIs rather than hardcode We don't want to maintain multiple image IDs for multiple regions so use ec2_ami_facts to set a suitable image ID Improve exception handling	6 years ago
Michael Mayer	fbcd6f8a65	Add Fargate support for ECS modules 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	6 years ago
Will Thames	12f2b9506d	[aws]Add VPC configuration to ECS modules (#34381 ) Enable awsvpc network mode for ECS services and tasks and their underlying task definitions Improve test suite to thoroughly test the changes Use runme.sh technique to run old and new versions of botocore to ensure that the modules work with older botocore and older network modes and fail gracefully if awsvpc network mode is used with older botocore	6 years ago
Matt Clay	d653d52dd8	Mark unsupported integration tests. (#38251 ) * Mark UCS integration tests as unsupported. * Mark various connection tests as unsupported. * Mark win_domain_group test as unsupported. * Mark java_cert test as unsupported. * Mark synchronize-buildah test as unsupported. * Mark various AWS tests as unsupported. * Mark azure_rm_acs test as unsupported. * Mark GCP tests as unsupported.	7 years ago
Will Thames	423b0e0f58	Improve details and events results for ecs_service_facts (#37983 ) * Use AnsibleAWSModule to simplify AWS connection * Add Exception handling, pagination, retries and backoff * Allow events to be switched off * Allow details to be obtained without having to specify services	7 years ago
Will Thames	56196e66bf	[cloud] Improve results from ecs_taskdefinition_facts (#34337 ) ecs_taskdefinition_facts should not populate ansible_facts with so much information. Better to just return the contents of the dict directly. Reduce line lengths, use AnsibleAWSModule, don't reimplement camel_dict_to_snake_dict.	7 years ago
Will Thames	ec5e509233	[cloud] Don't log AWS credentials when creating YAML anchor for ECS integration tests (#34625 ) Turn `no_log` on when setting the fact.	7 years ago
Will Thames	866d7fdce9	[cloud] Create ECS integration test suite (#33757 ) Tests for: * ecs_cluster * ecs_service * ecs_service_facts * ecs_taskdefinition * ecs_taskdefinition_facts * Add idempotency testing Test ecs_cluster, ecs_service and ecs_taskdefinition for trivial idempotency. Add FIXMEs to the tests because the latter two fail. Remove unused dependencies	7 years ago

11 Commits (5ea414422bd5571d2c779a68ae5d8f5054ed1649)