Skip to main content

Version 2.9.0+

These are the release notes for the v2.9.0 release of Witboost.

Please refer to the official documentation for a more in-depth overview of the released features.

Features​

APIs & CLI​

New APIs to instantiate templates​

Templates can now be instantiated programmatically via REST API, without going through the Witboost UI. This is useful for automation pipelines, CI/CD workflows, or any scenario where manual interaction is not practical. Three new endpoints are available: one to start the instantiation, one to stream live progress via Server-Sent Events, and one to poll the final status.

Check the documentation for additional information.

New Witboost CLI command to generate descriptors​

The new build-descriptor command in the Witboost CLI lets you generate a fully resolved descriptor from your local files, without ever opening the browser. You can build a single entity or an entire project (system + components), making it easy to validate your work locally before pushing changes. The command also supports environment-based resolution and can be combined with governance evaluation workflows.

Check the documentation for additional information.

Governance​

Clone policies and metrics from the UI​

Instead of creating policies and metrics from scratch, you can now clone an existing one directly from the UI and use it as a starting point. The clone copies all settings — metadata, execution configuration, severity levels, and resource perimeter — so you only need to adjust what differs, saving time and reducing manual entry errors.

Check the documentation for additional information.

Team roles​

Team Roles lets Project Owners delegate accountabilities within a Project — for example, assigning a Data Access Manager who is responsible for handling Access Control requests. When enabled, a new section appears on the Project page in the Builder showing who is responsible for what, ensuring that key responsibilities are always covered even when the Project Owner is not available.

Check the documentation for additional information.

Authentication & Security​

PAT for standard users​

Personal Access Tokens (PATs) are now available to all users, not just service accounts. You can generate a PAT directly from Settings and Profile > Advanced to authenticate with services integrated with Witboost, such as the Witboost CLI. Each user can have one active PAT at a time, with an optional expiration date.

Check the documentation for additional information.

Basic Auth with PAT​

As an alternative to Bearer token authentication, Witboost now supports Basic Authentication using access tokens (both service account tokens and PATs). When enabled, the platform automatically converts Basic Auth credentials into short-lived JWTs.

Check the documentation for additional information.

Git token for a service account, from UI​

When performing repository operations (creating repositories, committing, pushing, etc.), Witboost requires a Git token to authenticate with the Git provider. It is now possible to also configure Git credentials for a service account directly from the UI, under Administration > IAM > Service Accounts.

Check the documentation for additional information.

Content Security Policy (CSP) update​

Starting from this release, Witboost applies a stricter default Content Security Policy (CSP) by removing the unsafe-eval directive from script sources, further hardening the platform's security posture.

Check the migration notes for additional information.

UI & Configuration​

Microfrontends configuration in the UI​

Custom pages powered by microfrontends can now be configured and managed directly from the UI under Administration > Configuration > Custom pages, without editing configuration files. Changes take effect in real time, with no platform restart required.

You can also define conditions to control when a microfrontend is displayed. Conditions can be based on system or component types, as well as the usecaseTemplateId. When conditions are specified, the microfrontend is displayed only if the current entity matches the defined criteria.

Check the documentation for additional information.

Marketplace search filters configuration in the UI​

Marketplace search filters can now be configured directly from the UI under Administration > Configuration > Search filters, instead of editing the Helm values file. Existing filter configurations are automatically migrated and can be maintained from the UI going forward.

Filters now support a new option, landscapes, which is an optional array of landscape identifiers (e.g., taxonomy:default/data-mesh-taxonomy). When specified, the filter is displayed only if one of the specified landscapes is currently selected.

Check the documentation for additional information.

Template performance improvements​

Several template wizards across the Witboost UI have been optimized for better performance and responsiveness, especially when handling large numbers of array elements. Array fields now support pagination, allowing you to configure the number of items displayed per page.

Check the documentation for additional information.

Platform & Installation​

Convert HOCON sections to YAML​

If your values.yaml contains configuration blocks written in HOCON format, the Infra CLI can now automatically convert them to YAML during upgrades. A standalone convert-hocon command is also available for those who don't use the Infra CLI. Converting to full YAML is recommended to ensure all future migrations can be applied automatically.

Check the migration notes and the convert-hocon command reference for additional information.

Gateway API support​

Witboost now supports the Kubernetes Gateway API as an alternative to the traditional Ingress (NGINX) controller for traffic management. This aligns with the Kubernetes community's shift toward Gateway API as the modern, extensible successor to Ingress — the community-maintained Ingress NGINX controller is moving to best-effort maintenance mode.

By default, Ingress remains enabled and Gateway is disabled, so existing deployments are not affected. You can opt in to Gateway API by updating the Helm chart configuration. If you choose to switch, make sure to complete the required pre-requisites (Gateway API CRDs, a Gateway controller, and optionally cert-manager and external-dns updates).

Check the migration guide and the migration notes for additional information.

Issues fixed and minor improvements​

v2.9.0​

  • Accessibility improvements
  • Template Editor has been renamed to Template Studio, accessible from Administration > Templates via the context menu (three dots)
  • The "Edit Templates Form" tool in Template Studio now allows previewing the rendered edit template
  • Fixed tech adapters search
  • Fixed a bug in Supervision page stats that didn't consider logical reads from in statistics
  • Fixed sidebar in user permissions settings

v2.9.1​

  • Enhanced OpenShift compatibility for Hasura Autotracker

v2.9.2​

  • Fixed a bug that made the documentation crash if you clicked in a doc section that existed in Template 1, then headed into the documentation of Template 2 (which does not have said section)
  • Fixed a bug that was preventing the cache to be invalidated on user group changes

v2.9.3​

  • Added the possibility to configure a set of custom help links that appear in the help menu of the application
  • Fixed camel case issue in marketplace search
  • Fixes a bug where some power search documents could not be correctly collated and indexed.

v2.9.4​

  • Improved memory efficiency when provisioning large data products with hundreds of components. Furthermore, a new coordinator's 'scheduler-max-tasks-running-per-plan' configuration key (default: 10) allows capping the number of tasks running concurrently within a single execution plan, keeping resource consumption predictable for large plans. Set to 0 for unbounded concurrency. Refer to Coordinator's configuration page in the documentation for additional details.
  • Fixed a race condition in ACL processing where concurrent access approvals could overwrite each other, ensuring all granted users are correctly preserved in the final ACL list.

v2.9.5​

  • Resolved freeze on review information step with a lot of fields.
  • Fixed a bug where typing in form fields would cause the input to be reset immediately when the template included DescriptorPicker fields with field-based dependencies. Values are now preserved correctly while typing.
  • After creating a new GitLab repository via creation template, the publish step now waits for the project to become accessible via the GitLab API before proceeding. This prevents intermittent failures caused by GitLab's propagation delays, where the path-based API could return a transient 404 immediately after project creation.
  • Fixed a bug that was causing Coordinator's freezes when updating a tech adapter deployment.

v2.9.6​

  • Fixed a bug where the Edit Template wizard incorrectly displayed validation errors immediately upon entering a step, before the user had a chance to interact with the form.
  • Fixed form validation crashing with some specific schemas featuring nested dependencies.
  • Fixed Data Contract Provider system filter in EntitySearchPicker
  • Fixed custom filters migration startup action that was preventing default filters overrides to be migrated.
  • Security improvements.

v2.9.7​

  • Fixed an issue where cascading fields in scaffolder templates could appear empty on the first form load.

v2.9.8​

  • Expose management endpoints for provisioning coordinator and wcg

v2.9.9​

  • Fixed an issue where when starting editing a WCG policy its value would be reset to a wrong value in the UI
  • Fixed an issue where cascading fields in scaffolder templates could appear empty on the first form load when the template was instantiated via "Add" in system page

v2.9.10​

  • Fixed an issue where DescriptorPicker fields configured in a cascading chain did not update correctly when the parent field value changed. Now, changing the source field properly clears and repopulates the dependent field with the correct options.
  • Fixed validation for required array fields — fields that allow selecting multiple values now correctly prevent form submission when marked as required and left empty. The required indicator (asterisk) is also displayed consistently.
  • Fixed a bug where hideEmptyColumns set on true in custom view table would make some non empty columns disappear