Skip to main content

Release Notes for Styra DAS

This page describes the release notes for Styra DAS delivered in February 2022.

Release Summary

Styra is built on the Open Policy Agent (OPA), a popular and widely deployed open source project developed by the founders of Styra. With primary credibility for the underlying technology, the Styra team and technology are both proven in production across verticals. Styra enables enterprises to define, enforce, validate, and continually monitor security, compliance and operational policies across the cloud-native application stack. Styra has reinvented the authorization solutions to mitigate customer risk, and reinforce commitment to trust and transparency in safeguarding customers’ data. Styra’s Declarative Authorization Service (DAS) is a sophisticated management plane that provides context-based guardrails, built from a graphical policy library to mitigate risk, reduce human error and accelerate development. Styra makes it possible for enterprises to implement policy-as-code controls and to prove their effectiveness to both internal and external security and compliance audiences.

February 22, 2022

This Styra DAS 20220222 release delivers the following new enhancements.

New Features and Enhancements

This section describes the new enhancements in Styra DAS 20220222.


  • This release adds an option in Your Workspace >> Settings >> Decision Export configuration page to allow decision exports to Kafka.


  • This release updates the OPA version used in DAS and for systems deployment to 0.37.2.

  • By default, OPA containers run as root. Starting with this release, the install instructions use rootless OPA images.

February 14, 2022

This Styra DAS 20220214 release delivers the following new enhancements.

New Features and Enhancements

This section describes the new enhancements in Styra DAS 20220214.


  • This release significantly increases the speed of policy bundle compilation. Now, a bundle is available in less than a minute after publishing any policy updates.

Data Sources

  • Starting with this release, AWS S3, Git Content and HTTP data sources support the XML files. AWS S3 and Git Content data sources checks the file's extensions and converts all .xml files into JSON representation.HTTP data source additionally sends text/xml and application/xml as accepted types and parses the response by converting into JSON representation. For example, XML: <foo attr="bar"><xyz>main</xyz></foo> is converted to JSON: {"foo": {"@attr": "bar", "xyz": {"#text": "main"}}}.


  • Policy library rule snippets now supports the same autocomplete functionality as the policy editor. All existing fields that expects a string will be quoted to match the exact Rego string in the policy editor. Initially, typing a field that expects a string will be automatically quoted. When the quotes are deleted, autocomplete is enabled and behaves like autocomplete in policy editor.

  • Kubernetes policy rule snippets now has a new filter button, which moved filter items from the previous ... menu to the new filter menu.

Styra Local Control Plane (SLP)

  • Styra releases the 0.4.2 version of SLP. This version brings in changes required to support the latest OPA features, such as the in keyword.

February 8, 2022

This Styra DAS 20220208 release delivers the following new enhancement.

New Features and Enhancements

This section describes the new enhancement in Styra DAS 20220208.


  • Starting with this release, Styra Local Plane (SLP) instances are now StatefulSets rather than Deployments. This allows the SLP instance to store policies and decision logs across restarts. It can also improve resilience in situations, where the DAS is temporarily unavailable (for example, due to a network outage) and the SLP container needs to be restarted.

If you want to upgrade to the new system types then delete the existing SLP installations. In the DAS, navigate to your System >> Settings >> Uninstall, then run the command labeled uninstall SLP before performing the upgrade by following the Download and deploy SLP from the Install menu.

If you want to avoid downtime then run the Download and deploy SLP command for the system, then manually delete the old SLP deployment after the new StatefulSet begins running. To achieve this task, use kubectl get deployments, identifying the SLP deployment name, and then running kubectl delete deployment <deployment name>.