Feature Description
Today, run-task and service update reuse the same wait-for-minutes parameter. I think there should be a separate parameter, run-task-wait-for-minutes parameter that overrides wait-for-minutes when set.
Problem Statement
A very common use case for run-task is to run migrations before an ECS service is updated. In my case, I want to allow a different amount of time for migrations compared to how long I wait for service stability.
Today, I only have a single lever for this.
Alternatives Considered/ Work-arounds
- Don't use
run-task and use the AWS CLI myself
Willingness to Contribute
Yes
Feature Description
Today,
run-taskand service update reuse the samewait-for-minutesparameter. I think there should be a separate parameter,run-task-wait-for-minutesparameter that overrideswait-for-minuteswhen set.Problem Statement
A very common use case for
run-taskis to run migrations before an ECS service is updated. In my case, I want to allow a different amount of time for migrations compared to how long I wait for service stability.Today, I only have a single lever for this.
Alternatives Considered/ Work-arounds
run-taskand use the AWS CLI myselfWillingness to Contribute
Yes