We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
One can't deploy git tags because of the requirement for a var ECS_CLUSTER_BRANCH_NAME
ECS_CLUSTER_BRANCH_NAME
There also isn't a way to just let one set CLUSTER because it's overriden here https://github.com/motleyagency/travis-ecs-deploy/blob/master/lib/ecs-deploy#L92 and set to false.
There should be a way for users to just pass --service-name and --cluster without the need to go through travis-ecs-deploy
The text was updated successfully, but these errors were encountered:
@urbanslug hi! Sorry for the late reply.
That sounds great! The ecs-deploy is vendored from https://github.com/silinternational/ecs-deploy/blob/develop/ecs-deploy (IIRC), so it might make sense to make the changes there first.
ecs-deploy
Sorry, something went wrong.
@petetnt Sorry for the late reply too.
Not sure if I'll have time to put into this because I am migrating services from ECS to kubernetes. Feel free to close the issue.
@urbanslug no problem! I'll keep the issue open as it definitely something that would be really nice!
No branches or pull requests
One can't deploy git tags because of the requirement for a var
ECS_CLUSTER_BRANCH_NAME
There also isn't a way to just let one set CLUSTER because it's overriden here https://github.com/motleyagency/travis-ecs-deploy/blob/master/lib/ecs-deploy#L92 and set to false.
There should be a way for users to just pass --service-name and --cluster without the need to go through travis-ecs-deploy
The text was updated successfully, but these errors were encountered: