Releases: netsells/cli
Releases · netsells/cli
v2.2.5
Bumps dependencies to fix an issue with aws:ecs:manage-env
diff issue
v2.2.4
- Fixed issue where ecs:connect was double sanitising menu names, causing them to be empty strings
v2.2.3
- Fixes bug where defaults were not respected if the Netsells file was empty
v2.2.2
- Fixes bug where AWS account ID and region did not fall back to the Netsells file
v2.2.1
- Fixes bug where
NETSELLS_
environment variables were not detected for some commands
v2.2.0
- Adds tag prefixing
:latest
will always be tagged- when passing
--environment ENVNAME
or env varNETSELLS_ENVIRONMENT
:ENVNAME
will be tagged- Eg
:production
- Eg
- Usual tag will be prefixed with the environment name
ENVNAME-commitsha
- Eg
production-e2b54fc07d8f20bedaa4
- Eg
- Pass
skip-additional-tags
to only push the commit sha
- Internal refactors
- The command instance is now passed around for you, no need to pass $this about
- Options/Arguments/Netsells File/Env vars are handled automatically now, no need to manage by hand
v2.1.1
- Adds compatibility for newer version of the AWS CLI (2.1.31) which broke ECS deploy-update
v2.1.0
- Makes ECS Updates smarter by using the docker-compose file. Also now accepts a list of services via
--service
for partial deployments - Fixes bug where
--tunnel
was not provided with hint to re-run command
v2.0.0
- Removes
aws:ssm:start-session
command (as this has been absorbed intoaws:ssm:connect
aws:ssm:connect
now initiates an SSH connection directly from the CLI instead of the developer having to copy and paste a generated command
v1.3.0
- Adds new
docker:aws:login
to login your local shell into the AWS ECR repo