Improve dev cycle for pushing to ECR #765
Description
Describe the feature
In the old .NET deployment experience we had the aws-ecs-tools-defaults.json created during deployment so redeployments could be a quick 2 click start and confirm process.
With our new experience because we don't include ECR repositories as part of the Existing Targets each ECR push involves going through the whole deployment experience making the dev cycle have too many clicks.
We need to look into how we can improve the dev cycle for ECR pushes after the initial push to be back to the 2 click start and confirm process.
Use Case
ECR pushes after the first push should be able to be done in a 2 click start and confirm process.
Proposed Solution
Showing all ECR repositories in the Existing Targets is probably too much because the repository could have no relationship to our tooling or this project.
Look into maybe tagging the repositories as we create/push to them so we can use that as a filter in the Existing Target. Or possibly reintroduce some version of a local config file.
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
Version used
1.12.3
Operating System and version
Any