You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 31, 2019. It is now read-only.
Boondoggle is a little tool meant to simplify deployment of cloudformation
4
-
stacks.
3
+
Boondoggle is a little tool meant to simplify deployment of Cloudformation stacks.
4
+
5
+
## Usage
6
+
7
+
Given a CloudFormation template residing on S3 that takes two parameters `HttpImage` (an AMI ID) and `DesiredHostCount` (say, the desired count for an Autoscaling Group) deploy with:
The `ensure` subcommand will create the stack if no such stack currently exists, or update it with the specified template on S3 and parameters if it already exists.
14
+
15
+
Or cancel an in-progress update to a stack:
16
+
17
+
```bash
18
+
$ boondoggle cancel-update my-stack
19
+
```
20
+
21
+
Or just look up the status of a stack:
22
+
23
+
```bash
24
+
$ boondoggle status my-stack
25
+
```
26
+
27
+
All these commands are _blocking_, so the operation will be allowed to complete before `boondoggle` exits.
28
+
29
+
30
+
```
31
+
Options:
32
+
-p --profile=<profile> Use the specified profile in your .boto
33
+
-r --region=<region> Use the specified region [default: us-east-1]
34
+
-h --help Show this screen.
35
+
-v --version Show version.
36
+
```
37
+
38
+
## Why not use the AWS CLI?
39
+
40
+
The AWS CLI provides methods to create and update Cloudformation stacks, but the CLI uses separate commands for creating and updating a stack, and the syntax for stack parameters is rather torturous.
41
+
42
+
Boondoggle also blocks until the stack update is complete, making it a better fit for CI and deployment.
0 commit comments