Publish to AWS: Quickly re-publish container images to ECR

[LuizPonce]

From Publish to AWS, once I have published my application as a container into ECR, I would like a fast way to republish the same project to the same ECR. The re-publish should not need as many interactions/configurations as publishing to a New Target.

Original issue text is below

---

In Publish to AWS, the Existing Targets list did not show my project. I expected to see it there.

I've created a new Publish to New Target, deploy successfully many times. But never been show in "Existing Targets".
Then I tried use "administrator profile" to check if maybe the issue was permission and the same result. unsuccessfully use Existing Targets.

Do I need create manually the "settings" file ?
I'm using "Container Image to Amazon ECR"

Toolkit: 1.40.0.0
Visual Studio: 17.2.6

[awschristou]

Hi @LuizPonce , when you publish your application container into an ECR repo, this is considered a one-time deployment. ECR repo deployments do not appear under the "Existing targets" list. Publishing to the registry on its own does not create corresponding infrastructure as code (like CDK or CloudFormation for example). As an example, if you were to publish your application to Fargate, part of the publish process would push the application container to ECR, and a backing CloudFormation stack would be created, which would then appear in the "Existing Targets" list.

Since you'd have to publish to a new target each time you want to push your container to ECR, do you have suggestions that could make that process smoother?

(@ashovlin / @normj - you might be interested in feedback about this experience)

[LuizPonce]

Hi @awschristou thank you for you quickly answer.

My suggest is do like the used in previous version. There was possible use "aws-ecs-tools-defaults.json" then i only confirmed the values and publish.
Is it make sense?

thank you,

[awschristou]

Thank you for the suggestion @LuizPonce . I have updated this issue's title and text to reflect the feature request. I have talked with the team that is responsible for the .NET Deploy tool (which powers the Publish to AWS experience), and they have opened up issue aws/aws-dotnet-deploy#765 to track improvements made in ECR publishing.

We'll leave this issue open as well, and as improvements are made to the .NET Deploy tool, we will look at integrating them into the Publish to AWS experience, and update this issue.