ansible-elastic-beanstalk icon indicating copy to clipboard operation
ansible-elastic-beanstalk copied to clipboard

Ansible modules for working with Amazon Elastic Beanstalk

Results 17 ansible-elastic-beanstalk issues
Sort by recently updated
recently updated
newest added

This PR adds Python 3 support to the project, most of all changes are about syntax between python versions.

It'd be great if there was a way for it to diff new settings vs what's currently there in an environment, and not redeploy if there haven't been any changes....

``` /Users/benjamin/.ansible/tmp/ansible-tmp-1539239250.317117-87862374970487/AnsiballZ_elasticbeanstalk_version.py:17: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp Traceback (most recent call last): File "/Users/benjamin/.ansible/tmp/ansible-tmp-1539239250.317117-87862374970487/AnsiballZ_elasticbeanstalk_version.py", line 113,...

I am having an issue when trying to create an application environment that already exists. Current error logic handles checking environments existing in the given application but not environments existing...

i tried to run the scripts and an application was created in the AWS beansalk console, but was not able to create an enviornment. I'm getting the following errors `TASK...

I am creating my cloud infrastructure in AWS with **terraform** and deploying the applications with ansible. Terraform allows me to create an environment without any version associated. Consequently, the VersionLabel...

PLEASE HELP :( .. my first deployment is failing at Ensure Application Exists in Beanstalk. and if i comment out this task it fails at "name: "Create Application Version"..." TASK...

I'm unable to use this module when installed via ansible-galaxy. The error suggests that my playbook doesn't recognise `elasticbeanstalk_app` as a valid action. Max OS X 10.12.5, Python 2.7.10, Ansible...

The way the update environment call is currently setup cannot update the solution stack in use, without terminating and re-deploying the environment. Any reason we can't start checking and sending...