-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No defaults for launch type on consumption of run-task
#87
Comments
I have a similar dilemma with the |
Thanks for reporting this, we'll look into revising the defaults. In the meantime, there is an example of using |
What would you like to be added
On ecs run-task, I'd like to have a launch-type configuration that has no default values.
Currently the ECS run-task CLI doesn't require this
launch-type
parameter by default. However, the orb implementation requires this, and defaults to aFargate
value - which doesn't make sense for users who useEC2
launch types.Why is this needed
For users who use launch-type of EC2, the current default value creates implementation friction - as the launch-type needs to be overridden. Default values being
Fargate
here will probably cause some errors for future users that don't want their tasks run under Fargate launch type.The text was updated successfully, but these errors were encountered: