1
1
# Deep dive to plan
2
2
3
- By default, plan is stored in ` .helmwave ` directory
3
+
4
+ ## Definitions
5
+
6
+ By default, plan is stored in ` .helmwave ` directory. This directory name is ` plandir ` .
7
+
8
+ ` Uniqname ` is the unique release name, which is used to identify the release. Uniqname is ` release-name@namespace@kube-context ` .
9
+
10
+
11
+ ## Structure
4
12
5
13
Explanation of what a plan is.
6
14
@@ -10,35 +18,62 @@ Explanation of what a plan is.
10
18
- values/
11
19
- charts/
12
20
13
- ## planfile
21
+
22
+ ```
23
+ tree .helmwave
24
+ .helmwave
25
+ |____charts/
26
+ |____manifest
27
+
28
+
29
+ |____values
30
+ | |____api@ns@context
31
+ | | |____cb18185ed7a1e8d2f06fc029708867eb.yml
32
+ | |____web@ns@context
33
+ | | |____63610d2dfb7f7427e17b6f3f58937161.yml
34
+ |____charts
35
+ | |____api@ns@context
36
+ | | |____api-1.0.0.tgz
37
+ | |____web@ns@context
38
+ | | |____web-1.0.0.tgz
39
+ |____planfile
40
+ |____graph.md
41
+ ```
42
+
43
+ ### planfile
14
44
15
45
Planfile is a main yaml document. It contains information about all your planned resources.
16
46
Planfile is a computed ` helmwave.yml ` file.
17
47
48
+ by default, planfile is stored in ` .helmwave/planfile `
18
49
19
50
20
- ## graph.md
51
+ ### graph.md
21
52
22
53
graph.md is a markdown file. It contains visualisation for graph dependencies.
23
54
24
55
You can open this file with your favorite IDE and render image with [ mermaid] ( https://github.com/mermaid-js/mermaid ) .
25
56
26
- ## manifest
57
+ ### manifest
27
58
28
- Manifest is a directory where you can find all templated kubernetes resources in next format ` <release>@<namespace>.yml `
59
+ Manifest is a directory where you can find all templated kubernetes resources.
29
60
30
- You can scan the manifests in this directory.
61
+ by default is stored in ` .helmwave/manifest/<uniqname>.yml `
31
62
32
- See the [ :material-duck: example ] ( ../ci/?h=ci#kube-linter-and-helmwave )
63
+ You can do whatever you want with the manifests in this directory.
33
64
34
- Sure! You can apply that manifests directly like that: ` kubectl apply -f .helmwave/manifest `
65
+ ** For example, **
35
66
36
- ## values
67
+ - You can apply that manifests directly like that: ` kubectl apply -f .helmwave/manifest `
68
+ - You can lint manifests [ :material-duck: example] ( ../ci/?h=ci#kube-linter-and-helmwave )
69
+
70
+ ### values
37
71
38
72
Values is a directory where you can find rendered values files of your releases.
39
- To find the values for your releases you can use next pattern : ` ./helmwave/values/<release>@<namespace>/<hash>.yml `
73
+ To find the values for your releases you can use next pattern: ` .helmwave/values/<uniqname>/<hash>.yml `
74
+
40
75
41
- ## charts
76
+ ### charts
42
77
43
78
Charts is a directory where helmwave can store downloaded charts for all your releases.
44
79
It's not required but very useful when you want to use helmwave with DMZ cases.
0 commit comments