Add a JSON schema about helm-charts HOT 5 OPEN

While this is a great idea it's not a easy task to do, it would require merging in the Flux HelmRelease jsonschema into the app-template schema. Even if that was done, you would have to specify the JSONSchema different in HelmReleases vs app-template or not. I don't know if the juice is worth the squeeze here just to have our editors be happy.

from helm-charts.

funny because I just had the same idea about this, but I don't know how do u achieve that using VSCode. In neovim, I can't put the inline schema before --- because that means it's a new file. And I also tried putting the inline schema below spec.values of the HelmRelease and it didn't work too. That means I can't put 2 schemas (HR and app-template values) and expect it to work together.

from helm-charts.

While this is a great idea it's not a easy task to do, it would require merging in the Flux HelmRelease jsonschema into the app-template schema. Even if that was done, you would have to specify the JSONSchema different in HelmReleases vs app-template or not. I don't know if the juice is worth the squeeze here just to have our editors be happy.

Maybe just including the schema for the values, without megin it with the HelmRelase jsonschema, that gives the option of having the values.yaml file validated by helm and then copy-pase it to the HelmRelease or use Kustomize to create a configMap and use the valuesFrom to load it.

It's not only for the editors, but it may be included in CI, to check if the update of the chart breaks any of the implementations

from helm-charts.

funny because I just had the same idea about this, but I don't know how do u achieve that using VSCode. In neovim, I can't put the inline schema before --- because that means it's a new file. And I also tried putting the inline schema below spec.values of the HelmRelease and it didn't work too. That means I can't put 2 schemas (HR and app-template values) and expect it to work together.

I don't know about neovim but in vscode you can configure the schema globally in the yaml config using glob patterns:

yaml.schemas: {
    "https://json.schemastore.org/chart.json": "~/home-ops/charts/**/chart.yml",
    "kubernetes": "~/home-ops/cluster/**/*",
	"~/home-ops/cluster/common/app-template/values.schema.json": "~/home-ops/cluster/**/helmrelease.yaml"
}

docs: https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml#associating-schemas

from helm-charts.

I am open to doing something like this, but maybe (also) as a base to generate documentation off of, instead of the current helm-docs approach. I'll give it some more thought and see if I can work it in to an upcoming version.

from helm-charts.