Currently there is a single Helm task. But between Helm versions 2 and 3, quite some major changes to the cli have been made.
They are described here: https://helm.sh/docs/topics/v2_v3_migration/
I already noticed there is a PR already open for a long time with a regeneration for Helm 3 (but I think that could break Helm 2): #578 and a recent pr #839 to add a single new Helm 3 parameter.
My suggestion would be to rename the current tasks to Helm 2 and add a freshly generated Helm 3. But since this would be breaking it would be best to do this on a major version bump.
Usage Example
No response
Alternative
To just add next Helm3 tasks and just make it clear in the documentation, that it's for Helm2.
Or to add new parameter and methods to the existing Helm task, but that would be hard to generate, since it would be a combination of both CLIs.
Description
Currently there is a single Helm task. But between Helm versions 2 and 3, quite some major changes to the cli have been made. They are described here: https://helm.sh/docs/topics/v2_v3_migration/
I already noticed there is a PR already open for a long time with a regeneration for Helm 3 (but I think that could break Helm 2): #578 and a recent pr #839 to add a single new Helm 3 parameter.
My suggestion would be to rename the current tasks to Helm 2 and add a freshly generated Helm 3. But since this would be breaking it would be best to do this on a major version bump.
Usage Example
No response
Alternative