Deployment

Elevation Service Staging Environment

The elevation service has a fargate service defined in the stage-gaia-cluster ECS cluster. If you'd like to deploy to the staging cluster, it's a manual process unfortunately, but here's how you can do that:

1. get your changes pushed to the gaiagps/elevation-service ECR repo. this will happen automatically on every commit pushed to remote, on every branch. copy the image the URI associated with your commit, i.e. 265147712162.dkr.ecr.us-east-1.amazonaws.com/gaiagps/elevation-service:e897f0adb91e37ea7855355606b47e509de1cde0
2. Update the staging-elevation-task by creating a new task definition that will reference the image you just pushed to ECR. You'll need to hit "Create new revision" and then scroll down to Container 1 (or update the json directly if you prefer) and paste the image URI from step 1 into the "image URI" text box then hit "Create". This will create a new task definition, but it will not be deployed at this time. It is safe to create as many task definitions as you need, and it's also fine to create a revision that doesn't even end up getting used.
3. Now it is time to deploy the service using the new task definition you just created. Navigate to to the stage-elevation-service page, and hit "Update Service". In the deployment configuration box at the top, hit the "revision" drop down and select the task revision number you just created in step 2. It should be the latest one. Hit "update" and that should trigger a deployment of the most recent image using the task definition you created, meaning your changes should be reflected in staging!