The workflow for the pushing to aws-fargate-service looks like this:
Get ECR Authorization (this is a token acquired through AWS APIs that gives the docker daemon access to push ECR)
Retag the image from source to the target ECR repo (this mainly changes out the registry host in the image url to an ECR host)
Push the image using the docker API client through the user's docker daemon (using the authorization from step 1)
NOTES
The push command in aws-fargate-service currently only supports pushing to an ECR image registry. We don't have custom image registries configured yet.
As a result of the outputs.Retriever in https://github.com/nullstone-io/nullstone/pull/6, this PR also refactors the existing deploy code for aws-fargate-service. The same provider is used for the push command.
This PR introduces the
nullstone pushcommand.The workflow for the pushing to aws-fargate-service looks like this:
NOTES
The push command in
aws-fargate-servicecurrently only supports pushing to an ECR image registry. We don't have custom image registries configured yet.As a result of the
outputs.Retrieverin https://github.com/nullstone-io/nullstone/pull/6, this PR also refactors the existing deploy code foraws-fargate-service. The same provider is used for the push command.