[ECS] [request]: new Action for ECS service
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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**
Adding new action when select service in cluster ECS
**Which service(s) is this request for?**
This could be Fargate, ECS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Adding an option to select the service in Fargate and execute the Force new deployment action would be of great help.
Today this action can only be performed on the console by editing the service and checking the checkbox to update the service.
**Are you currently working around this issue?**
You need to edit the service, check the action checkbox and update the service
**Attachments**

The Force new deployment action could be added here

Contributor guide
Research direction
The issue does not name repository files, tests, or entry points. Start by reviewing the ECS/Fargate service selection flow and the requested Force new deployment action; done means the action is available for a selected service as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100