lono-cfn 0.0.2 → 0.0.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +4 -0
- data/Gemfile.lock +1 -1
- data/README.md +2 -2
- data/lib/lono_cfn/cli/help.rb +2 -2
- data/lib/lono_cfn/version.rb +1 -1
- data/spec/fixtures/my_project/output/params/my-stack.json +2 -4
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 2bf84b20c1282ec13d59fd62885d1fba43bdbcde
|
4
|
+
data.tar.gz: ffd102241da5df42ed250f7915f45a69868588d1
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 93e1da08ad74beac891b830aa50a4798b6c4cbbb5eb6d34c84fe62c12864467918609e283f3679c076e0403d5c935b9b202b626f4f9170f9bae64cef94f582d9
|
7
|
+
data.tar.gz: f3ac0486f5da76f20468df99b59666f5096ceb21534a6d6549cc95751dd083dbcebf9dcebbefd0ceaec42a65ff62cd6ee56480bf1ce7fff82ac13c6bee244a62
|
data/CHANGELOG.md
CHANGED
@@ -3,6 +3,10 @@
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
4
4
|
This project *tries* to adhere to [Semantic Versioning](http://semver.org/), even before v1.0.
|
5
5
|
|
6
|
+
## [0.0.3] update cli help
|
7
|
+
|
8
|
+
- Update CLI help.
|
9
|
+
|
6
10
|
## [0.0.2] lono-cfn update
|
7
11
|
|
8
12
|
- `lono-cfn update` implemented.
|
data/Gemfile.lock
CHANGED
data/README.md
CHANGED
@@ -36,11 +36,11 @@ Provided that you are in a lono project and have a `my-stack` lono template defi
|
|
36
36
|
$ lono-cfn create my-stack
|
37
37
|
```
|
38
38
|
|
39
|
-
The above command will generate and use the template in output/my-stack.json and parameters in params/my-stack.txt.
|
39
|
+
The above command will generate and use the template in output/my-stack.json and parameters in params/my-stack.txt.
|
40
40
|
|
41
41
|
### Conventions
|
42
42
|
|
43
|
-
The template by convention defaults to the name of the stack. In turn, the params by convention defaults to the name of the template
|
43
|
+
The template by convention defaults to the name of the stack. In turn, the params by convention defaults to the name of the template.
|
44
44
|
|
45
45
|
* stack - This is a required parameter and is the CLI first parameter.
|
46
46
|
* template - By convention matches the stack name but can be overriden with `--template`.
|
data/lib/lono_cfn/cli/help.rb
CHANGED
@@ -10,7 +10,7 @@ Provided that you are in a lono project and have a `my-stack` lono template defi
|
|
10
10
|
|
11
11
|
$ lono-cfn create my-stack
|
12
12
|
|
13
|
-
The above command will generate and use the template in output/my-stack.json and parameters in params/my-stack.txt. The template
|
13
|
+
The above command will generate and use the template in output/my-stack.json and parameters in params/my-stack.txt. The template by convention defaults to the name of the stack. In turn, the params by convention defaults to the name of the template.
|
14
14
|
|
15
15
|
Here are examples of overriding the template and params name conventions.
|
16
16
|
|
@@ -37,7 +37,7 @@ Provided that you are in a lono project and have a `my-stack` lono template defi
|
|
37
37
|
|
38
38
|
$ lono-cfn update my-stack
|
39
39
|
|
40
|
-
The above command will generate and use the template in output/my-stack.json and parameters in params/my-stack.txt. The template
|
40
|
+
The above command will generate and use the template in output/my-stack.json and parameters in params/my-stack.txt. The template by convention defaults to the name of the stack. In turn, the params by convention defaults to the name of the template.
|
41
41
|
|
42
42
|
Here are examples of overriding the template and params name conventions.
|
43
43
|
|
data/lib/lono_cfn/version.rb
CHANGED