Skip to main content

Release Notes for Styra DAS

This page provides Styra DAS SaaS Release Notes for March 2025.

March 26, 2025

The Styra DAS 20250326 release delivers the following changes.

New UI Additions

Datasource configuration accepts units

In the new UI, the datasource configuration for refresh now accepts numbers or numbers with time units.

System decision export settings

The new UI now supports the same configuration for decision export at the system level as the legacy UI.

Fixed Issues

WorkspaceViewer allowed to create user invitations

Changed the behavior to require a user to have the WorkspaceAdministrator role to invite a new user to a tenant.

Delete dialog in policy editor

After deleting a file in the policy editor, the confirmation dialog could remain open.

New UI replaying with too many drafts

In the new UI, reverted back to the legacy UI behavior of including only the current draft in the request.

New UI data.json package

In the new UI, creating a data.json file could sometimes cause a UI error.

New UI datasource deletion

In the new UI, there were cases where a datasource deletion was not immediately rendered in the datasource list.

March 19, 2025

The Styra DAS 20250319 release delivers the following changes.

New Features and Changes

New UI Additions

Persist decision log filters between sessions. Hide non-relevant read-only and meta files from the policy builder view.

Fixed Issues

Workspace monitoring tab errors

In the legacy UI, in some cases accessing the monitoring tab at the Workspace level could result in a UI error.

New UI duplicate SSO claims with multiple providers

In the new UI, when multiple SSO providers were configured, SSO claims for all providers were shown for each provider.

March 12, 2025

The Styra DAS 20250312 release delivers the following changes.

New Features and Changes

New UI Additions

Added compliance violation charts to Systems and Stacks with compliance monitoring. Added Kubernetes system compliance dashboard. Added access to original decision during decision replay. Added option to download datasource contents. Added JSON parsing error indication to policy editor inputs and mocks. Additional policy editor performance improvements. Modified behavior when switching between Systems, Stacks, and Libraries to navigate to the dashboard. Policy editor displays closest file or package which made the decision during decision replay.

Policy editor auto-import specific keyword

To prevent accidental migration of a policy to Rego v1 syntax, the policy editor auto-import behavior has been changed to import the specific keyword added to the policy (e.g., in, every, etc.) rather than the rego.v1 import.

Fixed Issues

Systems API minimum_opa_version query parameter does not return expected results

On the Systems API, when the minimum_opa_version query parameter was set on the API call, the returned results did not reflect the set option.

Incorrect decisions returned in new UI decision log when using customer policy type filter

In the new UI, using the custom policy type filter in the decision log could return additional decisions beyond those which matched the filter.

Repetitive Git branch API calls in new UI policy editor when viewing a metadata policy

In the new UI policy editor, viewing a metadata policy for a System or Stack (e.g., Stack selectors) could result in repetitive Git branch fetch API calls.

March 5, 2025

The Styra DAS 20250305 release delivers the following changes.

New Features and Changes

New UI Additions

Update decision log URL with search filters to allow sharing decision searches. Policy editor performance improvements. Show add file icon on package hover in policy editor.

Fixed Issues

New UI policy editor input and mock cleared after switching to validation tab

In the New UI policy editor, switching from the Preview tab to the Validation tab cleared any user-defined input or mock in the Preview tab.

Missing input from replayed Workspace-level decision in New UI

In the New UI, replaying a decision from the Workspace level in some cases did not populate the input in the Preview tab of the policy editor.