Repository navigation
LiteGate v2.15.2
Artifacts
| Artifact | Get it |
|---|---|
| Docker image | docker pull ghcr.io/brtydse100/litegate:2.15.2GHCR |
| Live demo | Current demo |
| Docs | Versioned documentation |
| Source | Source |
| License | MIT license |
What's Changed
- Add hierarchy JSON file input and Helm ConfigMap mounts by @brtydse100 in #41
Hierarchy JSON file input
Load the existing {"levels": [...]} hierarchy from a UTF-8 JSON file with
organization_hierarchy_file / ORGANIZATION_HIERARCHY_FILE. Relative paths
resolve against backend/. The file loads once at startup and uses the same
hierarchy validation, SSO email/ID/group matching, and inherited budgets as inline
configuration. Missing, unreadable, malformed, and invalid files fail startup.
Nonempty inline hierarchy levels cannot be combined with a file.
Helm's top-level organizationHierarchyFile selects an existing namespace
ConfigMap, with key: organization.json and
mountPath: /etc/litegate/organization.json defaults. It mounts the key read-only
with subPath and sets the file environment variable. Changing file options
triggers rollout; changing external ConfigMap contents requires an explicit
rollout restart. Docker Compose supports an optional read-only JSON mount.
Upgrade
The feature defaults off. Existing inline YAML and environment JSON remain
supported. This adds an input for the existing hierarchy; it does not restore
the removed standalone organization email-mapping schema or change authentication,
email verification, identity bindings, or budget policy. See
organization configuration for setup.
Full Changelog: v2.15.1...v2.15.2
Contributors
Thanks to @brtydse100 for the changes in this release.