I’ve had great success in building out my security groups with this module, until today.
The issue is that I cannot code in yaml a destination referencing a prefix-list. “pl-XXXXXX”
Is this supported? Or planned in the future?
Has anyone found a method around this?
This came up about a year ago on the ansible-devel list,
https://groups.google.com/forum/#!searchin/ansible-devel/prefix$20list|sort:relevance/ansible-devel/YjfcFY75wJk/qXoEDQbrEwAJ
is the thread: I'd asked about it, someone replied "yes but it'd be
tricky", I don't think anything's happened since then.
Our workaround is to do it by hand in the AWS console, and put a note in
our configs and docs about it. :^(
You could also probably do something clever with a 'command' module that
called the AWS CLI with appropriate arguments, but I haven't tried that.
-Josh (jbs@care.com)
(apologies for the automatic corporate disclaimer that follows)
This email is intended for the person(s) to whom it is addressed and may contain information that is PRIVILEGED or CONFIDENTIAL. Any unauthorized use, distribution, copying, or disclosure by any person other than the addressee(s) is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and delete the message and any attachments from your system.
I was thinking about possibly using vars in the yaml to deduce what the prefix list actually is.
Like, if it’s possible to do a var where pl-123456 can be deduced by describing it in AWS cli, then substituting it in. Thanks for the response, now I don’t feel like a small island 