This came up about a year ago on the ansible-devel list,
https://groups.google.com/forum/#!searchin/ansible-devel/prefix$20list%7Csort: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 (j...@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.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/22606.46223.45257.968242%40gargle.gargle.HOWL.
For more options, visit https://groups.google.com/d/optout.
