Helm sanity check

[saksmt]

Make some sort of sanity check for helm

Use Case:

This will prevent embarassingly stupid mistakes (like writing buildInputs = pkgs.helm in nix) from failing with undecipherable error messages. Current checks seems to be limited to just verifying that binary exists, but it does not actually check whether it is kubernetes related helm and not something else entirely.

Proposed Solution:

There could be added a check for helm version output, which can be additionally used to verify minimal accepted helm version. Alternatively sample hello-world chart or something similar could be run.

Other:

Current behavior given following setup for nix project:
./default.nix

let
  pkgs = import <nixpkgs> {};
in {
  shell = pkgs.mkShell {
    buildInputs = with pkgs; [
      nodejs
      helm # <-- this is not helm you're looking for!
    ];
  };
}

leads to incomprehensible errors from typescript cdk8s package:

Synthesizing application
$PROJECT_PATH/node_modules/cdk8s/src/api-object.ts:230
  const v = apiVersion.split('/');
                       ^
TypeError: Cannot read properties of undefined (reading 'split')
    at parseApiGroup ($PROJECT_PATH/node_modules/cdk8s/src/api-object.ts:230:24)
    at new ApiObject ($PROJECT_PATH/node_modules/cdk8s/src/api-object.ts:148:21)
    at new Include ($PROJECT_PATH/node_modules/cdk8s/src/include.ts:33:7)
    at new Helm ($PROJECT_PATH/node_modules/cdk8s/src/helm.ts:131:5)
    ...

Obviously it is low-priority feature and can only be met at absurdly stupid situations (like one described above), but nevertheless it is a worthy feature at least as a "good first issue" material.

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request