-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
elb_application_lb #33021
Comments
Files identified in the description: If these files are inaccurate, please update the |
Will fix in upcoming PR with rewrite for NLB support |
@wimnat is there an existing issue tracking the rewrite? I can't find it within the tracker |
@bobobox this seems resolved now with latest version of the module. Can you confirm? |
Now the SslPolicy parameter is required, but the docs doesn't say that it is required. |
Ok, now tested and it works (with required SslPolicy), reports as unchanged. |
My vote would be that it matches AWS' requirement. Thanks! |
Thank you very much for your interest in Ansible. Ansible has migrated much of the content into separate repositories to allow for more rapid, independent development. We are closing this issue/PR because this content has been moved to one or more collection repositories.
For further information, please see: |
ISSUE TYPE
COMPONENT NAME
elb_application_lb
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
If an Application Load Balancer is created/maintained via Ansible, and the 'SslPolicy' on a listener is not specified (documentation says 'The default is the current predefined security policy.', indicating it can be omitted to use the default), the listener is created successfully along with the ALB, but on subsequent runs the task fails with a KeyError.
STEPS TO REPRODUCE
Create ALB using a play like the one shown below, then re-run the same play.
Example play:
EXPECTED RESULTS
Play succeeds on first as well as subsequent runs.
ACTUAL RESULTS
Play fails after first run, due to KeyError when comparing SslPolicy.
The text was updated successfully, but these errors were encountered: