harvard-vpal / ecs-app-utils Goto Github PK

A common mistake is building a new image version and forgetting to push to ECR, then attempting to deploy - leading to either a CannotPullContainer error or no update occurring.

Add the ability to do a combined build and push action in a single CLI command, either as a new subcommand or with a named argument on existing build or push subcommands.

--no-cache option that can be passed to docker-compose build to ignore cache

Could utilize rich types to reduce number of module inputs/outputs

https://www.hashicorp.com/blog/terraform-0-12-rich-value-types

Specify docker-compose build definition file location as optional argument to build subcommand. At the moment, the default of build/docker-compose.build.yml is hard-coded.

Ability to infer AWS region setting from either AWS_REGION (not currently supported) or AWS_DEFAULT_REGION env variables

In case user attempts apply before pushing the relevant image to the repo.

Ability to run commands under a particular AWS profile, instead of assuming default profile (possibly with a --profile option for relevant commands)

If configuration is kept in a separate repo, the configuration can also be version tagged independently of the application version tag. The tag used for built images can be a combination of the two tags, e.g. {APP_TAG}-{CONFIG_TAG} or 2.1.1-10 . The ecs-utils CLI could support this with a new optional argument --config-tag.