ebitool-fe
repo (e.g bug fixing, new feature, etc).
master|test-build|release/v[0-9]+\\.[0-9]+\\.x(\\-[\\w]+)?
will trigger codebuild
codebuild
will run after commit named ebi-ebitool-fe-build
ebi-ebitool-fe-build
success, then will trigger ebitool-fe-ami-baking
codepipeline
and also trigger ebitool-fe-bake-ami
codebuild
ebitool-fe-bake-ami
codebuild
build logs, and that AMI-ID will use to update ebitool-fe
EC2 instance.
NOTE : staging and production use same build process and same artifact file.
ebi-ansible-playbook
repo, on this path /playbooks/ebitool-fe/staging.yml
ansible-galaxy install -r requirements.yml
tvlk-dev
AWS account as ProductDomainDeployer_ebi **
ansible-playbook staging.yml -e ami_id=<baked-ami-id> -e asg_min_size=1 -e asg_max_size=1 -asg_desired_capacity=1
ebi-ansible-playbook
repo, on this path /playbooks/ebitool-fe/production.yml
ansible-galaxy install -r requirements.yml
tvlk-prod
AWS account as ProductDomainDeployer_ebi **
ansible-playbook production.yml -e ami_id=<baked-ami-id> -e asg_min_size=1 -e asg_max_size=1 -asg_desired_capacity=1
Should you have questions or concerns regarding this, feel free to ask me, thanks