Deploy release branches to staging ECS environment #4758
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,64 +1,48 @@ | ||
| #!/bin/bash | ||
|
|
||
| sudo apt-get -y install python3-pip wget | ||
| sudo pip3 install awscli | ||
|
|
||
| if [ -z "${AWS_REGION}" ]; then | ||
| AWS_REGION=us-west-2 | ||
| fi | ||
|
|
||
| ENVIRONMENT=staging | ||
| CLUSTER=core | ||
| export core_CIRCLE_SHA1=$CIRCLE_SHA1 | ||
|
|
||
| PROPEL_CONFIG_FILE="propel.yaml" | ||
| if [ ! -f ${PROPEL_CONFIG_FILE} ]; then | ||
| echo "Propel configuration file not found!" | ||
| exit 1 | ||
| fi | ||
|
|
||
| ENV_NAME_UPPERCASE=$(echo $ENVIRONMENT | awk '{print toupper($0)}') | ||
| AWS_ACCESS_KEY_ID_VAR_NAME=CLOUDFORMATION_${ENV_NAME_UPPERCASE}_AWS_ACCESS_KEY_ID | ||
| AWS_SECRET_ACCESS_KEY_VAR_NAME=CLOUDFORMATION_${ENV_NAME_UPPERCASE}_AWS_SECRET_ACCESS_KEY | ||
|
|
||
| if [ "${!AWS_ACCESS_KEY_ID_VAR_NAME}" ]; then | ||
| AWS_ACCESS_KEY_ID=${!AWS_ACCESS_KEY_ID_VAR_NAME} | ||
| fi | ||
|
|
||
| if [ "${!AWS_SECRET_ACCESS_KEY_VAR_NAME}" ]; then | ||
| AWS_SECRET_ACCESS_KEY=${!AWS_SECRET_ACCESS_KEY_VAR_NAME} | ||
| fi | ||
|
|
||
| mkdir -p ~/.aws | ||
| echo "[default]" > ~/.aws/credentials | ||
| echo "aws_access_key_id = ${AWS_ACCESS_KEY_ID}" >> ~/.aws/credentials | ||
| echo "aws_secret_access_key = ${AWS_SECRET_ACCESS_KEY}" >> ~/.aws/credentials | ||
|
|
||
| echo "[default]" > ~/.aws/config | ||
| echo "region = ${AWS_REGION}" >> ~/.aws/config | ||
|
|
||
| echo Running aws s3 cp s3://${S3_PROPEL_ARTIFACTS_BUCKET}/propel-linux-amd64 ./propel | ||
| aws s3 cp s3://${S3_PROPEL_ARTIFACTS_BUCKET}/propel-linux-amd64 ./propel | ||
|
|
||
| sudo mv propel /usr/local/bin/propel | ||
| sudo chmod +x /usr/local/bin/propel | ||
|
|
||
| RELEASE_DESCRIPTION="CircleCI build URL: ${CIRCLE_BUILD_URL}" | ||
| echo storefront_CIRCLE_SHA1=$storefront_CIRCLE_SHA1 | ||
| propel release create --deploy --descr "${RELEASE_DESCRIPTION}" -f ${PROPEL_CONFIG_FILE} --env $ENVIRONMENT --cluster $CLUSTER | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -339,9 +339,9 @@ workflows: | |
| - deploy-to-ecs: | ||
| requires: | ||
| - docker-push | ||
| filters: | ||
| branches: | ||
| only: /^release*/ | ||
|
There was a problem hiding this comment. Were we going to do cc @spencern There was a problem hiding this comment. OK I'll change it to /^release-2.*/ for now. |
||
| - deploy-docs: | ||
| requires: | ||
| - test-unit | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| services: | ||
| - name: reaction-core | ||
| certificate_arn: arn:aws:acm:us-west-2:773713188930:certificate/c2979a7a-7b84-43ed-b3a7-24b0256a1b9f | ||
| root_domain: staging.reactioncommerce.com | ||
| dns_name: reaction-core | ||
| desired_task_count: 2 | ||
| min_task_count: 0 | ||
| max_task_count: 2 | ||
| min_healthy_percent: 100 | ||
| max_percent: 200 | ||
| alb_listener_port: 80 | ||
| alb_listener_path: / | ||
| alb_health_check_path: /health | ||
| task-definition: | ||
| name: staging-core | ||
| containers: | ||
| - name: core | ||
| cpu: 500 | ||
| memory: 1800 | ||
| port_mappings: | ||
| - container_port: 3000 | ||
| host_port: 3000 | ||
| image: reactioncommerce/reaction | ||
| image_tag: release-2.0.0-rc.5 | ||
|
There was a problem hiding this comment. So this will need to be updated every time we make a new release branch? There was a problem hiding this comment. The image_tag is used only if you deploy using propel from the command line. CircleCI deployments will automatically use the SHA1 of the newly built Docker image. |
||
| env_params: | ||
| - name: REACTION_AUTH | ||
| - name: REACTION_EMAIL | ||
| - name: REACTION_USER | ||
| - name: MONGO_URL | ||
| - name: ROOT_URL | ||
| - name: HYDRA_ADMIN_URL | ||
| - name: HYDRA_OAUTH2_INTROSPECT_URL | ||
| - name: SKIP_FIXTURES | ||
|
There was a problem hiding this comment. Does this list need to change when we add env variables? Where do the values come from? Maybe we can make this more straightforward when we do #4706 There was a problem hiding this comment. Those are there for informational purposes only. I can remove them once we have the .env.example file. |
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@griggheo Just curious, why write these to a file when AWS lib typically already looks for env variables with these names? Seems more secure to avoid any credentials in files.
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.
It didn't work for me when I specified the AWS keys without actually writing them to the credentials file. I'll try again. Agreed it's better not to save them to disk.