-
Notifications
You must be signed in to change notification settings - Fork 398
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
[WIP] add algorithm_type option for elb_target_group #282
Conversation
d'oh
|
Hi @markuman, did you find any workarounds? I looked at your shippable build failed error and I noticed that it display |
@sakar97 the access_key is approximately a username, Amazon don't treat it as a secret so we don't. |
The target group itself does not know if it is attached to an ALB, ELB Classic or NLB imho. Basically it is implemented like that: https://github.com/ansible-collections/community.aws/pull/282/files#diff-2c1c6b6915c4678f611809c13fca7baf3b17b239efd502403f050f52d2f03eafR756 That means, we must do more requests to verify where the target group is attached to. |
closing for the benefit of #1016 |
* Vendor ipaddress.py module util It had been previously vendored in ansible.netcommon but dropped in 2.0 This is needed for ec2_group until we can switch to python3-only, for ipv6 support. Also drop ansible.netcommon dependency. * Copy sanity ignores from netcommon for ipaddress * We still need netcommon in tests, for ipaddr filter
SUMMARY
Add option
algorithm_type
forelb_target_group
ISSUE TYPE
COMPONENT NAME
elb_target_group