- 18 Dec, 2013 1 commit
-
-
Using `ec2_tag` module without the state argument currently results in: ``` failed: [127.0.0.1] => {"failed": true, "parsed": false} ``` This fix makes `state=present` the default
willthames committed
-
- 17 Dec, 2013 1 commit
-
-
Moved `AWS_REGIONS` into `ec2` module Created `ec2_connect` method in `ec2` module Updated modules able to use `ec2_connect` and `AWS_REGIONS`
willthames committed
-
- 27 Nov, 2013 2 commits
-
-
Brandon Hilkert committed
-
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.
Justin Ludwig committed
-
- 01 Nov, 2013 1 commit
-
-
James Tanner committed
-
- 12 Oct, 2013 1 commit
-
-
Harrison Gu committed
-
- 13 Aug, 2013 1 commit
-
-
lwade committed
-