Releases: gestalt-config/gestalt
v0.35.1 Fix Module issues with RunTimeConfigNodeProcessor.
fix: module issues with RunTimeConfigNodeProcessor.
Updates tests to use latest Gestalt
Update benchmark results with new regression fixes.
Full Changelog: v0.35.0...v0.35.1
v0.35.0 Fix performance regression with cache and Kotlin 2.1.0
perf: fix performance regression with cache since we added getConfigResult, as we were caching the GResultOf. This was causing extra calls to get the result after getting data from the cache. We now have a separate cache for the normal flow and one for GResultOf.
dep: update to Kotlin 2.1.0
Update several other dependencies.
Full Changelog: v0.34.0...v0.35.0
v0.34.0 Runtime evaluation of string substitution and A/B Testing.
What's Changed
- feat: Differentiate between immediate evaluation at load time and deferred evaluation when getting the configuration. #226 by @credmond-git in #227
- feat: A/B Testing: Use a comma-separated list, where each element is a colon-separated pair of a threshold and its corresponding value. If an element has no threshold, it is treated as the default. For example, the format "10:red,30:green,blue" defines ranges and outcomes for random distributions: numbers from 1 to 10 correspond to red, 11 to 30 correspond to green, and all numbers above 30 default to blue. #219
Full Changelog: v0.33.1...v0.34.0
v0.33.1 Publish to https://central.sonatype.com
- Publish to https://central.sonatype.com instead of https://oss.sonatype.org
- No code changes
Full Changelog: v0.33.0...v0.33.1
v0.33.0 Annotations
What's Changed
- Feat/annotations by @credmond-git in #225
Certain annotations can be applied to a configuration using @{annotation}
, this will covert the annotation to metadata that can be applied to the node. Then the metadata is used to apply the intended behaviour to the node.
For example, we can apply the temporary node feature on a node by using the annotation @{temp:1}
my.password=abcdef@{temp:1}
annotation | parameter | description |
---|---|---|
temp | (int) Number of times this temp node can be read | restrict the number of times a value can be read before it is released |
encrypt | (boolean) if we should apply to this node | Encrypts the node in memory. |
nocache | (boolean) if we should apply to this node | Will not cache the node. If a node is part of a object the whole object will not be cached. |
secret | (boolean) if we should apply to this node | Treats the node as a secret, so it will not print it out in errors or the debug print. |
Trim Whitespace
By default, white spaces before and after the annotation are trimmed. You can disable this feature using the gestalt builder and setting setAnnotationTrimWhiteSpace(false)
GestaltBuilder builder = new GestaltBuilder();
Gestalt gestalt = builder
.addSource(MapConfigSourceBuilder.builder()
.setCustomConfig(configs)
.build())
.setAnnotationTrimWhiteSpace(false)
.build();
Full Changelog: v0.32.2...v0.33.0
v0.32.2
What's Changed
- Feat/207 node include source factories by @credmond-git in #214
- Add additional node include sources:
- URL Config Source
- Env Vars
- Kubernetes
- System
- S3 (AWS)
- Blob (Azure)
- git
- Google Cloud Storage
- Add additional node include sources:
- test: additional git tests. by @credmond-git in #217
Full Changelog: v0.32.1...v0.32.2
v0.32.1 CDI Default Support
What's Changed
- docs: Update key features with string and node substitution. by @credmond-git in #206
- test: Add additional CDI tests. by @credmond-git in #210
- feat: Better support for defaults with CDI. by @credmond-git in #211
- feat: Additional tests for gestalt-git by @credmond-git in #212
- chore: Update dependencies.
Full Changelog: v0.32.0...v0.32.1
v0.32.0 Node Substitution (include nodes)
$include Keyword Enhancements
The $include keyword allows you to merge a referenced config node tree into a specified path. By default, the node is merged under the current node. The order can be controlled with a numeric value:
< 0: Included below the current node.
> 0: Included above the current node.
0: Root node inclusion (default).
Nodes with identical orders have undefined behavior, and multiple nodes must have unique orders to avoid data loss. Nested includes and root/sub-node inclusions are supported.
Each include must specify a source and its parameters.
v0.31.3
What's Changed
Full Changelog: v0.31.2...v0.31.3