Vector v0.22.0 release notes

Vector’s configuration interpolation of environment variables has been enhanced to both allow setting of default values and returning an error message if an expected environment variable is unset or empty. The syntax matches bash interpolation syntax:

• ${VARIABLE:-default} evaluates to default if VARIABLE is unset or empty in the environment.
• ${VARIABLE-default} evaluates to default only if VARIABLE is unset in the environment.
• ${VARIABLE:?err} exits with an error message containing err if VARIABLE is unset or empty in the environment.
• ${VARIABLE?err} exits with an error message containing err if VARIABLE is unset in the environment.

The parse_json function now takes an optional max_depth parameter to control how far it will recurse when deserializing the event. Once the depth limit is hit, the remainder of the fields is left as raw JSON in the deserialized event.

For example:

parse_json!("{"1": {"2": {"3": {"4": {"5": {"6": "finish"}}}}}}", max_depth: 5)

Yields:

{ "1": { "2": { "3": { "4": { "5": "{"6": "finish"}" } } } } }

The default remains no max depth limit.

VRL now includes two new functions for encrypting and decrypting field values: encrypt and decrypt. A random_bytes function was added to make it easy to generate initialization vectors for the encrypt function.

See the highlight for more details about this new functionality.

The gcp_stackdriver_metrics sink now requires configuration of labels at the top-level to match the gcp_stackdriver_logs sink. Previously these were nested under .labels.

See the upgrade guide for more details.

VRL now correctly updates the type definition of variables defined in one scope, that are mutated in another.

For example:

foo = 1
{ foo = "bar" }
upcase(foo)

Would previously fail to compile because VRL thinks foo is an integer when, in fact, it has been reassigned to a string.