Nelm CLI

[ilya-lesikov]

Nelm CLI Design doc: https://docs.google.com/document/d/1zwzrEXGy6o-zqC5bOttS_nqcXB3kJqUugcMEq1S0ArE/edit?tab=t.0

rel #134

[Aleksey-Kalinin]

Please consider the following possibilities:

• set the parameters of the Nelm operation through the YAML file, and not only through the parameters and env
• using any YAML and JSON template engines (including future ones), not just Go templates

[shurup]

using any YAML and JSON template engines (including future ones), not just Go templates

This is not directly related to CLI itself, and we have a separate issue for this feature request: #54

[felipecrs]

It would be awesome if there was a drop-in helm replacement nelm binary I could use.

I would just symlink it to /usr/local/bin/helm in my pipelines and would benefit from it very little effort.

[ilya-lesikov]

@felipecrs We will have different cli layout and cli flags, some commands will return results in a different form (helm get vs nelm release get), so it won't be a drop-in replacement. But Helm charts and Helm releases are supported.

[felipecrs]

I suppose my best luck is to keep using werf helm then, right?

[ilya-lesikov]

Supporting both werf helm, nelm and werf just for Kubernetes deployments is too much for us. werf helm is going to be deprecated and removed in werf v3 or v4 in favor of standalone Nelm. And, frankly, we haven't actively developed werf helm in quite some time.

We will recommend migrating to standalone Nelm from werf helm. It shouldn't take too much work, generally you only need to change cli commands/flags in your CI, e.g. werf helm upgrade --install > nelm release install.

[felipecrs]

I see, thank you.