Skip to content

fResult/Helm-Intellisense

This branch is up to date with tim-koehler/Helm-Intellisense:master.

Folders and files

NameName
Last commit message
Last commit date
Dec 30, 2021
May 31, 2020
May 26, 2024
Jun 20, 2021
Aug 26, 2021
May 30, 2020
Mar 19, 2021
Dec 30, 2021
May 18, 2022
Jun 1, 2020
Feb 5, 2022
May 18, 2022
Feb 5, 2022
Aug 26, 2021
May 30, 2020

Repository files navigation

Helm-Intellisense

Visual Studio Marketplace Installs Visual Studio Marketplace Rating (Stars) GitHub Repo stars GitHub issues

Extension to help writing Helm-Templates by providing intellisense

Demo Gif

Features

  • The values.yaml file of the chart will be read and evaluated automatically to provide intellisense.
  • Autocomplete will also work for all Named Templates defined in the any .tpl file.
  • Autocomplete for defined helm variables.
  • Compatible with Windows and Linux/Unix.
  • Support for custom named value files is provided (see settings section below).
  • Lint command to validate correct values templating and usage of NamedTemplates.
  • Support and autocomplete for yaml anchors and labels
  • The extension is compatible with the Kubernetes extension.
  • Working with language type yaml and helm-template.

Commands

  • Helm-Intellisense: Lint : This command parses the currently active document and validates that all paths(like .Values.foo.bar) point to valid values.
  • Helm-Intellisense: Lint Chart : Equivalent to Lint command but for all files in the chart of the file that is currently active.

Settings

Setting Description
helm-intellisense.customValueFileNames Defines list of possible files containing values
(default: values.yaml)
helm-intellisense.lintFileOnSave If set to true the Helm-Intellisense: Lint command will be executed on save (default: true)
helm-intellisense.excludeFromLinting Define a list of filenames which should be excluded from linting.
Wildcards are also possible (Example: *.gotmpl)

Multiple value files (overriding)

When mulitple value files are defined they are parsed from the bottom up:

"helm-intellisense.customValueFileNames": [
    "prod-values.yaml",
    "dev-values.yaml",
    "values.yaml"
]

In this case values will be overwritten/merged by dev and dev by prod. This also means that the linter will only throw an error if a certain key is not found in any of the specified files.

About

Extension for Visual Studio Code - Intellisense in helm-templates from the values.yaml

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 96.9%
  • Mustache 3.1%