The EB CLI is a command line interface for Elastic Beanstalk that provides interactive commands that simplify creating, updating and monitoring environments from a local repository.
Apache License 2.0
161
stars
77
forks
source link
Add complete support for parameter based configuration #516
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Tell us about your request
Am requesting that the eb cli support complete configuration through command line arguments.
For instance, I'd like to be able to run the eb cli command as follows:
eb deploy --application-name myapp --environment dev
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I am trying to solve two problems:
When running the eb deploy command (or other commands) in CI/CD (or on any system where we wish to run an eb command without having a .elasticbeanstalk/config.yml we need to run eb initor create a file named .elasticbeanstalk/config.yml prior to running the eb tool
Ensuring a consistent user experience across all AWS provided tooling - I believe most other AWS CLI tools support nearly complete configuration via command line arguments
Are you currently working around this issue?
Currently we either check-in or create an EB file. Example below:
If just the --application-name argument was accepted this would probably support most of the use cases where this would be desired.
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information).
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Tell us about your request
Am requesting that the
eb cli
support complete configuration through command line arguments.For instance, I'd like to be able to run the eb cli command as follows:
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I am trying to solve two problems:
When running the
eb deploy
command (or other commands) in CI/CD (or on any system where we wish to run aneb
command without having a.elasticbeanstalk/config.yml
we need to runeb init
or create a file named.elasticbeanstalk/config.yml
prior to running theeb
toolEnsuring a consistent user experience across all AWS provided tooling - I believe most other AWS CLI tools support nearly complete configuration via command line arguments
Are you currently working around this issue?
Currently we either check-in or create an EB file. Example below:
How are you currently solving this problem?
See above.
Additional context
If just the
--application-name
argument was accepted this would probably support most of the use cases where this would be desired.Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information).