1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Commit graph

19 commits

Author SHA1 Message Date
willthames
238da3cb02 ec2_elb module: Minor improvements to documentation
ELB(s) cause a weird formatting behaviour - it appears as EL**s**
Added choices documentation to the state option
2014-01-16 13:14:44 +10:00
willthames
12005a1cd0 Move more responsibility to common EC2 module
Moved `AWS_REGIONS` into `ec2` module
Created `ec2_connect` method in `ec2` module
Updated modules able to use `ec2_connect` and `AWS_REGIONS`
2013-12-17 14:07:24 +10:00
Jim Dalton
aa329b4b48 Make sure initial_state is initialized 2013-12-12 13:09:40 -08:00
Jim Dalton
ac1e84d976 Account for instances that have not yet been registered. Fixes #5076 2013-12-09 19:38:03 -08:00
Justin Ludwig
26374d89a0 Fix AWS credential params for s3 and other modules
The `ec2_ami`, `ec2_elb`, `ec2_tag`, `ec2_vpc`, `route53`, and `s3` modules
all canonicalize the AWS access and secret key params as
`aws_access_key` and `aws_secret_key`. However, following the fixes for #4540,
those modules now use `get_ec2_creds` from `lib/ansible/module_utils/ec2.py`,
which requires access/secret key params to be canonicalized as
`ec2_access_key` and `ec2_secret_key`. As a result, AWS credentials passed
to those six modules as parameters are ignored (they instead always use
the AWS credentials specified via environment variables, or nothing).

So this change fixes those six modules to canonicalize the
AWS access and secret key params as `ec2_access_key` and `ec2_secret_key`,
allowing them to again accept AWS credentials passed via module params.
2013-11-26 19:29:06 -08:00
James Tanner
afa5988391 Fixes #4540 Use shared module snippet to evaluate ec2 credentials 2013-11-01 11:59:24 -04:00
kiri
c1c32c75ac add NoneType check. 2013-10-28 21:35:57 +09:00
Jim Dalton
3ea0b2bc05 Add enable_availability_zone parameter to ec2 module. 2013-09-23 08:58:47 -07:00
James Cammarata
d27372ff08 Modified ec2_elb doc per issue #3849 2013-09-03 16:13:25 -05:00
Bruce Pennypacker
80ddb1aee6 Added wait parameter 2013-08-23 13:56:59 -04:00
Bruce Pennypacker
0f458210bc Rebase attempt
No idea if I'm rebasing properly or not.  This is my first attempt.
2013-08-20 15:14:16 -04:00
Bruce Pennypacker
8171b7ba48 Added optional region parameter. Fail if you specify an ELB that doesn't exist.
Boto blindly assumes the us-east-1 region if you don't hardcode a
region in it's config, so you could end up attempting to modify ELB's
in one region from a totally different region.  If a region isn't
specified then default to the region that the module is being run
within rather than the default us-east-1 region since it's a pretty
safe assumption that you intend to work on the ELB's within your
current region.

Also throw an error if a specified ELB instance doesn't exist.  The old
behavior would be to silently succeed with changed=false, so if you had
so much as a typo in the name of your ELB (or were in the wrong region
like my initial testing) you wouldn't get a clear indication that a
problem had occurred.
2013-08-01 16:50:01 -04:00
Michael DeHaan
d6449711ae Revert "Added an elb_region parameter for interacting with the ec2 elastic load balancer to work with regions other than us-east-1"
This reverts commit 1264a5b47d.
2013-07-20 10:48:39 -04:00
Ian O Connell
1264a5b47d Added an elb_region parameter for interacting with the ec2 elastic load balancer to work with regions other than us-east-1 2013-07-19 18:21:51 -07:00
John Jarvis
e5d9dad205 Parameter and variable naming issues 2013-05-03 06:55:06 -04:00
John Jarvis
a45b312907 changing arg name for consistency, absent/present for registration 2013-05-02 21:29:36 -04:00
John Jarvis
e625155cd5 doc update 2013-04-30 09:03:31 -04:00
John Jarvis
70b61f13e4 marking the state changed only when there are ELBs to work on 2013-04-30 09:00:10 -04:00
John Jarvis
e9254fbc5a Adding module to de-register/register EC2 instances
This module handles AWS EC2 ELB registration.

* De-registration requires the instance id which can be looked up using
  the ec2_facts module.
* Registration requires both the instance id and the elbs that the
  instance belongs to.

De-registration will return an ec2_elb fact that can be used for
registration in post_tasks.
2013-04-29 23:40:17 -04:00