Explicitly support or do not support the awsebcli
Relevant support conversation: 30637
CircleCI 2 provides first-class support for `awscli` through passing in environment variables. However, this is insufficient for the use of the `awsebcli`, which seems to be a wrapper around sets of commands in the `awscli`.
The difference is that `awsebcli` requires a profile/credential file, which was provided in CircleCI 1. To use a command like `eb deploy` in CircleCI 2, you either need to explicitly dump the credential variables into a profile file, or patch together the same functionality using a series of `aws` commands - an s3 upload, an elasticbeanstalk version update, and an elasticbeanstalk environment update.
[People have suggested workarounds](https://medium.com/engineering-on-the-incline/continuous-integration-with-circleci-2-0-github-and-elastic-beanstalk-cf1a0b7f05c6), and we're using the workaround where you dump the env vars into a credential file.
One of the things that CircleCI trumpets is first-class support for various deployment pipelines. The experience was better in CircleCI 1 for the `awsebcli`, and it's frustrating to find documentation for this in v1 that isn't in v2.
I'd like one of two things:
- Provide first-class support for `awsebcli` alongside `awscli`
- Provide documentation that indicates that `awsebcli` does not work out of the box, and provide workarounds in said documentation