hull-demo-1.31.3

Changelog

---

[1.31.3]

CHANGES:

• added Gateway API objects in version 1.2.0-experimental as main object types to HULL: backendlbpolicy, backendtlspolicy, gatewayclass, gateway, grpcroute, httproute, referencegrant, tcproute, tlsroute and udproute. This should make it more comfortable to use them opposed to specifying them using the generic customresource object type. Thanks to suggestion from ievgenii-shepeliuk made here
• introducing sources feature for pods (pod level in the workload specifications) and containers (initContainers and containers levels in the workload specifications). Using souces enables global defaulting of pod and container properties and flexible sharing plus stacking of sets of properties for both pods and containers. Potential usages range from globally enforcing workload security settings, specifying shared minimum or special resource requirements or harmonization of all pods and containers in a chart. See the chart design guide for details. This also closes issues Add sharedContainers feature and Default security settings.
• added configurable multi-pass rendering of HULL transformations. This enables forward referencing of values in the YAML tree which was previously not possible. For example, using only a single HULL transformation rendering pass, a field .Values.hull.config.specific.field_a: _HT*hull.config.specific.field_b, where _HT*hull.config.specific.field_b: _HT*hull.config.specific.field_c, will resolve field_a to literal string _HT*hull.config.specific.field_c. This is the case because at the time when field_a is resolved the value of field_b is not yet resolved due to the alphanumeric order of HULL transformation processing. With the new multi-pass default of hull.config.general.render: 3, the field_a: _HT*hull.config.specific.field_c value is fully resolved to the referenced value of _HT*hull.config.specific.field_c in the second pass.

hull-demo-1.30.8

Changelog

---

[1.30.8]

CHANGES:

• added Gateway API objects in version 1.2.0-experimental as main object types to HULL: backendlbpolicy, backendtlspolicy, gatewayclass, gateway, grpcroute, httproute, referencegrant, tcproute, tlsroute and udproute. This should make it more comfortable to use them opposed to specifying them using the generic customresource object type. Thanks to suggestion from ievgenii-shepeliuk made here
• introducing sources feature for pods (pod level in the workload specifications) and containers (initContainers and containers levels in the workload specifications). Using souces enables global defaulting of pod and container properties and flexible sharing plus stacking of sets of properties for both pods and containers. Potential usages range from globally enforcing workload security settings, specifying shared minimum or special resource requirements or harmonization of all pods and containers in a chart. See the chart design guide for details. This also closes issues Add sharedContainers feature and Default security settings.
• added configurable multi-pass rendering of HULL transformations. This enables forward referencing of values in the YAML tree which was previously not possible. For example, using only a single HULL transformation rendering pass, a field .Values.hull.config.specific.field_a: _HT*hull.config.specific.field_b, where _HT*hull.config.specific.field_b: _HT*hull.config.specific.field_c, will resolve field_a to literal string _HT*hull.config.specific.field_c. This is the case because at the time when field_a is resolved the value of field_b is not yet resolved due to the alphanumeric order of HULL transformation processing. With the new multi-pass default of hull.config.general.render: 3, the field_a: _HT*hull.config.specific.field_c value is fully resolved to the referenced value of _HT*hull.config.specific.field_c in the second pass.

hull-1.31.3

Changelog

---

[1.31.3]

CHANGES:

• added Gateway API objects in version 1.2.0-experimental as main object types to HULL: backendlbpolicy, backendtlspolicy, gatewayclass, gateway, grpcroute, httproute, referencegrant, tcproute, tlsroute and udproute. This should make it more comfortable to use them opposed to specifying them using the generic customresource object type. Thanks to suggestion from ievgenii-shepeliuk made here
• introducing sources feature for pods (pod level in the workload specifications) and containers (initContainers and containers levels in the workload specifications). Using souces enables global defaulting of pod and container properties and flexible sharing plus stacking of sets of properties for both pods and containers. Potential usages range from globally enforcing workload security settings, specifying shared minimum or special resource requirements or harmonization of all pods and containers in a chart. See the chart design guide for details. This also closes issues Add sharedContainers feature and Default security settings.
• added configurable multi-pass rendering of HULL transformations. This enables forward referencing of values in the YAML tree which was previously not possible. For example, using only a single HULL transformation rendering pass, a field .Values.hull.config.specific.field_a: _HT*hull.config.specific.field_b, where _HT*hull.config.specific.field_b: _HT*hull.config.specific.field_c, will resolve field_a to literal string _HT*hull.config.specific.field_c. This is the case because at the time when field_a is resolved the value of field_b is not yet resolved due to the alphanumeric order of HULL transformation processing. With the new multi-pass default of hull.config.general.render: 3, the field_a: _HT*hull.config.specific.field_c value is fully resolved to the referenced value of _HT*hull.config.specific.field_c in the second pass.

hull-1.30.8

Changelog

---

[1.30.8]

CHANGES:

• added Gateway API objects in version 1.2.0-experimental as main object types to HULL: backendlbpolicy, backendtlspolicy, gatewayclass, gateway, grpcroute, httproute, referencegrant, tcproute, tlsroute and udproute. This should make it more comfortable to use them opposed to specifying them using the generic customresource object type. Thanks to suggestion from ievgenii-shepeliuk made here
• introducing sources feature for pods (pod level in the workload specifications) and containers (initContainers and containers levels in the workload specifications). Using souces enables global defaulting of pod and container properties and flexible sharing plus stacking of sets of properties for both pods and containers. Potential usages range from globally enforcing workload security settings, specifying shared minimum or special resource requirements or harmonization of all pods and containers in a chart. See the chart design guide for details. This also closes issues Add sharedContainers feature and Default security settings.
• added configurable multi-pass rendering of HULL transformations. This enables forward referencing of values in the YAML tree which was previously not possible. For example, using only a single HULL transformation rendering pass, a field .Values.hull.config.specific.field_a: _HT*hull.config.specific.field_b, where _HT*hull.config.specific.field_b: _HT*hull.config.specific.field_c, will resolve field_a to literal string _HT*hull.config.specific.field_c. This is the case because at the time when field_a is resolved the value of field_b is not yet resolved due to the alphanumeric order of HULL transformation processing. With the new multi-pass default of hull.config.general.render: 3, the field_a: _HT*hull.config.specific.field_c value is fully resolved to the referenced value of _HT*hull.config.specific.field_c in the second pass.

hull-demo-1.32.1

Changelog

---

[1.32.1]

CHANGES:

• added Gateway API objects in version 1.2.0-experimental as main object types to HULL: backendlbpolicy, backendtlspolicy, gatewayclass, gateway, grpcroute, httproute, referencegrant, tcproute, tlsroute and udproute. This should make it more comfortable to use them opposed to specifying them using the generic customresource object type. Thanks to suggestion from ievgenii-shepeliuk made here
• introducing sources feature for pods (pod level in the workload specifications) and containers (initContainers and containers levels in the workload specifications). Using souces enables global defaulting of pod and container properties and flexible sharing plus stacking of sets of properties for both pods and containers. Potential usages range from globally enforcing workload security settings, specifying shared minimum or special resource requirements or harmonization of all pods and containers in a chart. See the chart design guide for details. This also closes issues Add sharedContainers feature and Default security settings.
• added configurable multi-pass rendering of HULL transformations. This enables forward referencing of values in the YAML tree which was previously not possible. For example, using only a single HULL transformation rendering pass, a field .Values.hull.config.specific.field_a: _HT*hull.config.specific.field_b, where _HT*hull.config.specific.field_b: _HT*hull.config.specific.field_c, will resolve field_a to literal string _HT*hull.config.specific.field_c. This is the case because at the time when field_a is resolved the value of field_b is not yet resolved due to the alphanumeric order of HULL transformation processing. With the new multi-pass default of hull.config.general.render: 3, the field_a: _HT*hull.config.specific.field_c value is fully resolved to the referenced value of _HT*hull.config.specific.field_c in the second pass.

hull-1.32.1

Changelog

---

[1.32.1]

CHANGES:

• added Gateway API objects in version 1.2.0-experimental as main object types to HULL: backendlbpolicy, backendtlspolicy, gatewayclass, gateway, grpcroute, httproute, referencegrant, tcproute, tlsroute and udproute. This should make it more comfortable to use them opposed to specifying them using the generic customresource object type. Thanks to suggestion from ievgenii-shepeliuk made here
• introducing sources feature for pods (pod level in the workload specifications) and containers (initContainers and containers levels in the workload specifications). Using souces enables global defaulting of pod and container properties and flexible sharing plus stacking of sets of properties for both pods and containers. Potential usages range from globally enforcing workload security settings, specifying shared minimum or special resource requirements or harmonization of all pods and containers in a chart. See the chart design guide for details. This also closes issues Add sharedContainers feature and Default security settings.
• added configurable multi-pass rendering of HULL transformations. This enables forward referencing of values in the YAML tree which was previously not possible. For example, using only a single HULL transformation rendering pass, a field .Values.hull.config.specific.field_a: _HT*hull.config.specific.field_b, where _HT*hull.config.specific.field_b: _HT*hull.config.specific.field_c, will resolve field_a to literal string _HT*hull.config.specific.field_c. This is the case because at the time when field_a is resolved the value of field_b is not yet resolved due to the alphanumeric order of HULL transformation processing. With the new multi-pass default of hull.config.general.render: 3, the field_a: _HT*hull.config.specific.field_c value is fully resolved to the referenced value of _HT*hull.config.specific.field_c in the second pass.

hull-demo-1.32.0

Changelog

---

[1.32.0]

CHANGES:

• initial K8S 1.32 release
• deprecating 1.29 release

hull-1.32.0

Changelog

---

[1.32.0]

CHANGES:

• initial K8S 1.32 release
• deprecating 1.29 release

hull-demo-1.31.2

Changelog

---

[1.31.2]

FIXES:

• fixed printed empty string when referencing multi-line strings including line breaks using _HT*. Referenced strings via _HT* are now bytewise interpreted and printed including newlines using printf "%s" ($value | quote) instead of just $value. This transports original string as they are literally specified.
• partially fixed referencing large numbers in their original form. Previously if a string contains large numbers > 999999 or values resembling scientific notation, any reference via _HT* to the source field interpreted the strings as numbers and converted them to usually undesired scientific notation, chaning their value and meaning. Side effect of using printf "%s" ($value | quote) for string references, all strings are now transported unchanged. Essentially this makes the JSON hack mentioned in this issue obsolete when the source value is in string form.

CHANGES:

• using tpl transformations with _HT! now allows in-place serialization of the result using toJson, toPrettyJson, toRawJson, toYaml or toString. This adds another serialization possibility besides the existing _HT/ include and _HT* get transformation result serialization capabilities. Thanks ievgenii-shepeliuk for the feature request here.
• made previously required dictionary wrapping of array contents for include/_HT/ transformations obsolete by correctly making use of to fromYamlArray Helm function. If an array was to be returned by a _HT/ transformation, previously it was needed to wrap it in a dictionary and grab the result from the chosen dictionary key. For example, an transformation like _HT/result/hull.transformation.do.something would essentially return an array if the include produces a dictionary with a key result that has an array value. Starting with this version, it is possible to call _HT/hull.transformation.do.something and the resulting include can directly produce the array.
• restructured documentation on transformations in the hull/doc/transformation.md file and removed references to obsolete legacy syntax for transformations.

hull-demo-1.30.7

Changelog

---

[1.30.7]

FIXES:

• fixed printed empty string when referencing multi-line strings including line breaks using _HT*. Referenced strings via _HT* are now bytewise interpreted and printed including newlines using printf "%s" ($value | quote) instead of just $value. This transports original string as they are literally specified.
• partially fixed referencing large numbers in their original form. Previously if a string contains large numbers > 999999 or values resembling scientific notation, any reference via _HT* to the source field interpreted the strings as numbers and converted them to usually undesired scientific notation, chaning their value and meaning. Side effect of using printf "%s" ($value | quote) for string references, all strings are now transported unchanged. Essentially this makes the JSON hack mentioned in this issue obsolete when the source value is in string form.

CHANGES:

• using tpl transformations with _HT! now allows in-place serialization of the result using toJson, toPrettyJson, toRawJson, toYaml or toString. This adds another serialization possibility besides the existing _HT/ include and _HT* get transformation result serialization capabilities. Thanks ievgenii-shepeliuk for the feature request here.
• made previously required dictionary wrapping of array contents for include/_HT/ transformations obsolete by correctly making use of to fromYamlArray Helm function. If an array was to be returned by a _HT/ transformation, previously it was needed to wrap it in a dictionary and grab the result from the chosen dictionary key. For example, an transformation like _HT/result/hull.transformation.do.something would essentially return an array if the include produces a dictionary with a key result that has an array value. Starting with this version, it is possible to call _HT/hull.transformation.do.something and the resulting include can directly produce the array.
• restructured documentation on transformations in the hull/doc/transformation.md file and removed references to obsolete legacy syntax for transformations.