AWS elb_target_group requires vpc_id, protocol, port when state is absent about community.aws HOT 6 CLOSED

Files identified in the description:

• plugins/modules/elb_target_group.py

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

from community.aws.

cc @jillr @s-hertel @tremble @wimnat
click here for bot help

from community.aws.

Still present with Ansible 2.9.23.

    - name: Destroy target group                                                                                        
      elb_target_group:                                                                                                 
        region: "{{ aws_region }}"                                                                                      
        name: "{{ aws_target_group_name }}-{{ k8s_cluster_id }}"                                                        
        state: absent                                                                                                   
        wait: true 

TASK [Destroy target group] **************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "target_type is instance but all of the following are missing: protocol, port, vpc_id"}

from community.aws.

cc @markuman
click here for bot help

from community.aws.

The issue seems to be at

    module = AnsibleAWSModule(argument_spec=argument_spec,
                              required_if=[
                                  ['target_type', 'instance', ['protocol', 'port', 'vpc_id']],
                                  ['target_type', 'ip', ['protocol', 'port', 'vpc_id']],
                              ]
                              )

where the required_if fails to account for the fact that ['protocol', 'port', 'vpc_id'] are not really required if state=absent (all that should be required in that case is name).

It doesn't look like required_if supports that additional level of logical complexity directly.

from community.aws.

@rwky Digging into this a little more, the issue was actually fixed by ansible/ansible#65201 however it wasn't backported to Ansible 2.9.

The latest version of Ansible is 2.11, with 2.12 due in a couple of weeks. As such Ansible 2.9 is no longer accepting most patches so you'll need to explicitly use the version of this module from the collections if you want the fix. https://docs.ansible.com/ansible/latest/user_guide/collections_using.html

This may mean you'll need to set the "collections" keyword, or refer to the module as "community.aws.elb_target_group" rather than just elb_target_group".

from community.aws.