New issue
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
Circle 1->2 #42
Circle 1->2 #42
Conversation
# install dependencies for loading ecs task definitions | ||
command: | | ||
eval $(aws ecr get-login --no-include-email) | ||
sudo pip install --upgrade elcaminoreal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know I know. but I have to do one manual merge of something so I can know that the deploy flow works correctly before I can merge globality build.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I understand that it's only a auto generator for the existing circleCI config files, but it might worth to see why we're not it in this way (Postgres for instance):
https://github.com/globality-corp/globality-service-data/blob/develop/.circleci/config.yml#L57
In this way the postgres container will run as a daemon and will be accessible for other containers.
No description provided.