-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ecs_taskdefiniton port_mapping not idempotent when missing hostPort #690
Labels
Comments
Files identified in the description:
If these files are inaccurate, please update the |
I can confirm this for community.aws 1.5.0. ---
- hosts: localhost
connection: local
tasks:
- name: Register task definition
ecs_taskdefinition:
family: something
state: present
containers:
- name: something
essential: true
image: nginx
memory: 1
command:
- uptime
portMappings:
- containerPort: 3000
- name: Register task definition
ecs_taskdefinition:
family: something
state: present
containers:
- name: something
essential: true
image: nginx
memory: 1
command:
- uptime
portMappings:
- containerPort: 3000 results in
It was fixed by #574 |
alinabuzachis
pushed a commit
to alinabuzachis/community.aws
that referenced
this issue
May 25, 2022
…collections#690) ec2_vpc_route_table - support associating internet gateways Depends-On: ansible/ansible-zuul-jobs#1362 Depends-On: ansible/ansible-zuul-jobs#1364 SUMMARY Update ec2_vpc_route_table to support associating internet gateways per feature request ansible-collections#476 Add integration tests Fix idempotency issue when associating a subnet with a route table ISSUE TYPE Feature Pull Request COMPONENT NAME ec2_vpc_route_table Reviewed-by: Mandar Kulkarni <mandar242@gmail.com> Reviewed-by: Joseph Torcasso <None> Reviewed-by: Abhijeet Kasurde <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None> Reviewed-by: Mike Graves <mgraves@redhat.com> Reviewed-by: Mark Chappell <None> Reviewed-by: Mark Woolley <mw@marknet15.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Summary
ecs task definitions are not idempotent when missing the
hostPort
key value pair in theport_mappings
parameter.boto3 does not require the
hostPort
value when registering a task definition .I would suggest updating the documentation and stating
hostPort
,containerPort
are required parameters. Alternatively,hostPort
could be set to the same value ascontainerPort
. The solution will be very similar to what was done for theprotocol
parameter.Issue Type
Bug Report
Component Name
ecs_taskdefinition
Ansible Version
Collection Versions
I am not currently using collections, I am running an older version of ansible. But looking at the code for the ecs_taskdefinition.py module, it is still effected
AWS SDK versions
Configuration
DEFAULT_KEEP_REMOTE_FILES(env: ANSIBLE_KEEP_REMOTE_FILES) = True
OS / Environment
Red Hat Enterprise Linux Server release 7.9 (Maipo)
Steps to Reproduce
Expected Results
task_definitions should be idempotent.
Actual Results
The most important part here is the
portMappings
inrequested_container
vsactual_container
.Code of Conduct
The text was updated successfully, but these errors were encountered: