Important feature requests and planned changes to be discussed
This is going to be pinned to the header of our GitHub issues list so that everyone can be aware of and redirected to important planned features for discussion :)
- Allow opting in for inheriting all the values to sub-helmfile #762
- Add option for remote values files located in other repos #469
- Stop bases inheriting parents' values by default #688
- Automated rollback of failed release #256
- Atomic helmfile release #925
- Installing a helm release from single K8s manifest YAML file hosted somewhere (e.g. OperatorHub) #1720
- Remove helmfile --args #1804
- Add
--dry-run#118 - Add
{{ include }}#1345 - Let double-rendering go #932
- Stop helmfile on first error #1977
- A flag to render subchart notes #2001
- Disallow layering valuesTemplates + values #2037
- Ability to set release values via helmfile flag #2049
My only concern is losing helmfile --args specifically for performing a dry-run. I understand the reason behind deprecating the --args option, but can we find a compromise in adding a --dry-run ability? That is an incalculable tool for our purposes.
@mumoshu Howdy! Thank you for bringing this up. Since remote values will take a touch, maybe this one will be also a small but a handy addition #1817 (for values might also make sense).
@notjames Hey! Please add your comment to #118 🙏 Everyone replying here with various topics on various related issues just makes my work harder!
@dennybaa Hey! Are you talking about #469? Then, I'd appreciate it very much if you could reply there. The reason is the same as above
Well, I reread your comment and it turned about you're suggesting to add #1817 to here as it's similar to #469, right? :) Gotcha!
Please let me have some time and decide the priority myself because I believe I'm the only one trying to balance the importance of each feature request/user-support/maintenance/existence of contributors/etc here. I believe they all are essential for maintaining Helmfile.
When you want to bump up one feature request to be prioritized over another feature request, put your comment or 👍 on corresponding issues, not here!