Mike Arnold

I would prefer to see `solution_stack` left alone until I decide to change it.

The input [update_level](https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment#input_update_level) should not be set if `minor` or `patch` are not passed in.

Let me know when this PR will actually be reviewed and I will update it to fix any merge conflicts.

See #147 as related.

@joe-niland My naive approach would be to completely remove those two actions. I do not understand why they would be needed. Otherwise, forcing a user to specify the role to...

`ssh_source_restriction` is a variable but is not implemented in the tf code, so I imagine the security group is not being updated with a port 22/tcp rule.

@joe-niland I am curious, what does a readme rebuild have to do with adding a single Beanstalk `setting`?

@jamengual I have not. And I am not clear on why I would when I want to destroy the entire configuration, not disable it.

Uh. Another `iam:PassRole` to `*` again. See https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/issues/147 and the source [Unit 42 Cloud Threat Report: Misconfigured IAM Roles Lead to Thousands of Compromised Cloud Workloads](https://unit42.paloaltonetworks.com/iam-roles-compromised-workloads/).

Where are these parameters documented? I do not see them in /usr/share/doc/initscripts-9.03.40/sysconfig.txt .