-
Notifications
You must be signed in to change notification settings - Fork 20
Deployments
Simple Deploy supports performing deployments in an opinionated way to Instances with in a Cloud Formation stack. It supports both directed deployments to running instances, as well as converged deployments to new instances.
Simple Deploy makes the following assumptions about deployments:
- Deployments will be kicked off by a single script (currently hard set to /opt/intu/admin/bin/configure.sh).
- Deployments will be done via the above script regardless of the change size or scope (infra structure, application code, etc).
To leverage Simple Deploy for deployments, your app will require the following:
- Builds Via Heirloom.
- Instances bootstraped via Cloud Init with Metadata staged in specific locations.
- Chef installed (either on AMI or via Cloud Init)
- Configuration scripts intalled in /var/chef/scripts
Simple Deploy requires two builds to be in Heirloom for deployments.
- Chef Repo
- App
The Chef Repo will contain the chef configuration management repo. It is expected to contain the recipes required to read metadata. For more information see the Chef Section below.
Each instances is expected the have the following metadata configured by Cloud Init prior to kicking off check.
An example of a Cloud Formation template that sets the necessary metadata can be seen here.