Patrick.Sy/spring-petclinic
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-petclinic.git synced 2025-07-22 15:55:49 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fixed indentation

Browse source
This commit is contained in:
ebracho 2017-09-23 13:16:37 -07:00
parent 1f631a317d
commit 7ff8791b8d
1 changed files with 32 additions and 30 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
blue-green/blue-green-deploy
View file

@ -1,23 +1,25 @@
#!/bin/bash -xe
# This script executes a blue/green deployment on the petclinic production infrastructure.
# This script executes a blue/green deployment on the petclinic
# production infrastructure.
#
# Production infrastructure consists of:
# - An application load balancer (prod-petclinic)
# - Two target groups (proda-petclinic, prodb-petclinic)
# - A single t2.micro ec2 instance in each target group (proda.petclinic.liatr.io, prodb.petclinic.liatr.io)
# - A single t2.micro ec2 instance in each target group
#
# One of the two target groups should be attached to the ALB at any given time via a Listener
# One of the two target groups should be attached to the ALB at any given timel
# via a Listener
#
# To perform a blue/green deployment, we:
# - Figure out which target group is detached
# - Deploy the application to each instance in the detached target group (only 1 instance in this case)
# - Deploy the application to each instance in the detached target group
# - Run smoke tests on the newly deployed applications
# - Delete the current attached listener
# - Attach a new listener that forwards to the target group we deployed to.
#
# Expected environment variables:
# - DEPLOY_KEY_PATH Private key used to shell deploy to petclinic prod instances
# - DEPLOY_KEY_PATH Private key to access prod instances
# - AWS_ACCESS_ID_ID
# - AWS_SECRET_ACCESS_KEY For modifying load balancer resources
# - IMAGE Dockerhub repo to deploy from