Currently, the "GWY/Release: AWS" images releasing to ECR follows the standard push convention:
registry/repo:tag (for example: registry-1.docker.io/library/ubuntu:24.04)
In order to follow this standard, even though it's easy to edit and explained how to in the README, GWY builds the ECR pushing URL to {ECR_registry}/{app_name}:{app_version}, using as application name the go.mod module name, and retrieving the release version from the releasing branch name (either extracts the version from the branch if it follows release branches convention or uses the entire branch name as tag).
Now.. small teams, or even lone wolves using DockerHub private accounts, might want to deploy all their applications to a same repo and differentiate between them with a tag stating both the app name and version.
The scope of this Ticket is to enable in the releasing workflow an option to state what convention the client wants to use, if either the single app repos convention or multi-app repos one.
Currently, the "GWY/Release: AWS" images releasing to ECR follows the standard push convention:
registry/repo:tag(for example:registry-1.docker.io/library/ubuntu:24.04)In order to follow this standard, even though it's easy to edit and explained how to in the README, GWY builds the ECR pushing URL to
{ECR_registry}/{app_name}:{app_version}, using as application name thego.modmodule name, and retrieving the release version from the releasing branch name (either extracts the version from the branch if it follows release branches convention or uses the entire branch name as tag).Now.. small teams, or even lone wolves using DockerHub private accounts, might want to deploy all their applications to a same repo and differentiate between them with a tag stating both the app name and version.
The scope of this Ticket is to enable in the releasing workflow an option to state what convention the client wants to use, if either the single app repos convention or multi-app repos one.