petelock
|
00dc5d9116
|
fix checker error message (#1266)
Signed-off-by: petelock <pete2387@gmail.com>
|
2024-01-04 17:31:00 +08:00 |
yxxhero
|
0199b5f764
|
fix checker for empty array case (#1153)
|
2023-11-20 16:34:24 +08:00 |
|
yxxhero
|
34ccbf9056
|
fix issue 1093 (#1094)
|
2023-10-25 10:42:47 +08:00 |
|
yxxhero
|
48e48aa568
|
feat: add friendly tips for helmfile config order (#710)
* feat: add kindful tips for helmfile config order
Signed-off-by: yxxhero <aiopsclub@163.com>
|
2023-08-06 22:22:36 +08:00 |
|
yxxhero
|
c55fa0f765
|
Replace interface{} by any (#901)
Signed-off-by: yxxhero <aiopsclub@163.com>
|
2023-06-16 10:49:05 +09:00 |
Yusuke Kuoka
|
8f2d97a1b3
|
Relax the forbid-env-with-releases policy for plain helmfile.yaml on v1 (#684)
|
2023-02-09 07:02:50 +08:00 |
|
Yusuke Kuoka
|
8c130a4fa7
|
fix: Make the forbid-env-with-releases policy strict on v1 (#683)
Currently, both v0 and v1 warns any usage of environments with releases within the same helmfile part.
It should rather be an error for v1, as proposed in https://github.com/helmfile/helmfile/blob/main/docs/proposals/towards-1.0.md#forbid-the-use-of-environments-and-releases-within-a-single-helmfileyaml-part.
Follow-up for #592
Signed-off-by: Yusuke Kuoka <ykuoka@gmail.com>
|
2023-02-08 09:09:12 +08:00 |
|
yxxhero
|
d8d0bf830a
|
Add helmfile state validate policy (#592)
|
2022-12-21 10:49:31 +08:00 |