knife-cookbook-doc 0.6.0 → 0.7.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +8 -8
- data/CHANGELOG.md +5 -0
- data/README.md +17 -2
- data/lib/knife_cookbook_doc/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,15 +1,15 @@
|
|
1
1
|
---
|
2
2
|
!binary "U0hBMQ==":
|
3
3
|
metadata.gz: !binary |-
|
4
|
-
|
4
|
+
ZGM3MTZiNmYzYTVkOTYwMzUzYjRmMjI0OGZkMGMwMTZkMTg4ZGU4YQ==
|
5
5
|
data.tar.gz: !binary |-
|
6
|
-
|
6
|
+
MjkxZTJiOWUzMmM3ZTVmYjE5YWVlNjE5ZDA0MGM5YzhiNWIyY2Q0OQ==
|
7
7
|
!binary "U0hBNTEy":
|
8
8
|
metadata.gz: !binary |-
|
9
|
-
|
10
|
-
|
11
|
-
|
9
|
+
ZTQxZTVlNzIwMDU3Y2YyMjFlMmY2ZmQxNmJiYzhlYTExMDBiZjBlNWNhMDA3
|
10
|
+
OGY4NDI0ZjIzMGUwZDVmN2FlNTI5Y2I4YWZlOGFlM2ZlNGQ1NzFiNTk4NTRh
|
11
|
+
NTk3MDNiYTlhM2M5OThlZDFhMDRiYzdkZWU5MTFmM2NmMzI4Y2Q=
|
12
12
|
data.tar.gz: !binary |-
|
13
|
-
|
14
|
-
|
15
|
-
|
13
|
+
MGFkM2U0MzhhYzkyOTQ4OTZlNzNmODY0Njg2MDc1MzYyNTM4ZjBlMDRmZTNk
|
14
|
+
M2VjYTg3YmNiMGE3ODZiZDg5YTAxOTVjNzRlOWI3ZTRjMWMxMTAyMjkzMzZj
|
15
|
+
M2IyOWFjNGM2NzBmMzRlZTIxYzUxZWYyZjI1MTQxNzhmNjc4Y2M=
|
data/CHANGELOG.md
CHANGED
data/README.md
CHANGED
@@ -16,8 +16,10 @@ it's currency.
|
|
16
16
|
|
17
17
|
Populate the `metadata.rb` of your cookbook according to Opscode's
|
18
18
|
[documentation](http://docs.opscode.com/config_rb_metadata.html). Particular
|
19
|
-
attention should be paid to documenting the
|
20
|
-
|
19
|
+
attention should be paid to documenting the platform compatibility and
|
20
|
+
cookbook requirements (i.e. depends, recommends, suggests etc). Documentation
|
21
|
+
for attributes and recipes can either be derived from scanning the source
|
22
|
+
code or by explicit declaration in `metadata.rb`.
|
21
23
|
|
22
24
|
#### Step 2
|
23
25
|
|
@@ -29,6 +31,19 @@ At the top of each recipe, add a detailed documentation section such as;
|
|
29
31
|
#>
|
30
32
|
=end
|
31
33
|
|
34
|
+
If the user has not specified documentation for the recipe in `metadata.rb`
|
35
|
+
then the tool takes the first sentence of the detailed documentation as the
|
36
|
+
summary to use in the table of contents.
|
37
|
+
|
38
|
+
#### Step 2
|
39
|
+
|
40
|
+
If the user has not specified documentation for the attributes in `metadata.rb`
|
41
|
+
then the tool scans the attribute files and uses the documentation block
|
42
|
+
preceding the attribute.
|
43
|
+
|
44
|
+
#<> MyApp Admin Group: The group allowed to manage MyApp.
|
45
|
+
default['myapp']['group'] = 'myapp-admin'
|
46
|
+
|
32
47
|
#### Step 3
|
33
48
|
|
34
49
|
In each LWRP, add detailed documentation such as;
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: knife-cookbook-doc
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.7.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Mathias Lafeldt
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2013-10-
|
12
|
+
date: 2013-10-13 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: chef
|