Helmize
GitHub Toggle Dark/Light/Auto modeToggle Dark/Light/Auto modeToggle Dark/Light/Auto mode Back to homepage

Conditions

Conditions translate into paths where files are looked up based on given values which are relevant for deployment. Conditions are declared as list, based on the order the files are looked up and merged.

Configuration

Each condition can have the followin configurations.

name

Required

Type string

Used across helmize to reference to condition.

key

Optional

Type string

Path to the value in the user delivered values which is used as key to lookup.

key_types

Optional

Type slice Default [ "string", "slice" ]

Define the types the key must have. For example if you only want to allow a single value, the type should be slice. Types you can use are documented here:

required

Optional

Type boolean

The declared key must have a value. If no value is given the templating fails.

default

Optional

Type string

If the declared key does not contain a value, this default value will be used.

path

Optional

Type string

The path defines under which directory path the given values for the condition are looked up. If no path is given, the condition’s name is used as path. Note that the path is complementary to the inventory_directory

filter

Optional

Type string/slice

Filter keylist for values that are not allowed and exclude them as valid path. The filter is executed against all inputs for this condition. If a filter matches a value, the value is removed. You can use regex patterns. The allow_root is not affected by any filter and will always be added.

reverse_filter

Optional

Type boolean

Reverses the filter configuration so that only values given with the filter are accepted.

allow_root

Optional

Type boolean

In addition to checking all keys, it becomes also valid to have files directly in the root of the condition’s path.