-
Notifications
You must be signed in to change notification settings - Fork 17
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
ECS automatic deployment #37
Conversation
port being what's used with the load balancer
version it's running
@@ -9,6 +9,10 @@ before_install: | |||
- export PATH="$HOME/.meteor:$PATH" | |||
- pip install --user awscli | |||
- export PATH=$PATH:$HOME/.local/bin | |||
- curl -o $HOME/.local/bin/ecs-cli https://s3.amazonaws.com/amazon-ecs-cli/ecs-cli-linux-amd64-latest && chmod +x $HOME/.local/bin/ecs-cli | |||
- aws configure set profile.lmb-dev.aws_access_key_id $AWS_ACCESS_KEY_ID |
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.
Later, when we merge this stuff with staging, we'll need to use the conditional which prevents the script from trying to access the AWS env vars on pull request CI builds.
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.
Oh, that's a point. I guess this should all be setup in the deploy stage only.
Current deploys on any commit for testing purposes. We can limit easily to master later. Won't pass CI since it doesn't get access to AWS_SECRET_ACCESS_KEY!
Has a longer timeout: aws/amazon-ecs-cli#401 (comment)
Still unanswered questions: