-
Notifications
You must be signed in to change notification settings - Fork 22
Deployments
Brett Weaver edited this page Dec 14, 2012
·
4 revisions
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. Builds are expected to be uploaded via Heirloom.
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.
- Configuration scripts installed in /opt/intu/admin/bin/configure.sh
When you execute a deployment, Simple Deploy performs the following:
- Sets deployment in progress.
- Reads the chef_repo, cookbooks and app versions.
- Converts the chef_repo, cookbooks and app versions into Heirloom style deployment links.
- Updates CookbooksURL, ChefRepoURL and AppURL Cloud Formation parameters with the updated links.
- Sends notification (if set) that deployment is starting.
- Executes /opt/intu/admin/bin/configure.sh with the COOKBOOKS_URL, CHEF_REPO_URL and APP_URL set to the Heirloom links of the respective files across all instnaces within the target stack.
- Unsets deployment in progress.
- Sends notification (if set) that deployment is complete.