Skip to content

22 December 2022 Release Notes

Version 1.1.259

Feature highlights

Warning

The kitchen roles release notes are specific to DataKitchen DataOps Automation configurations that have previously activated kitchen roles phase 1. Customers who use kitchen roles phase 1 may experience some downtime in their environment on the 22n as we incorporate the updates for phase 2.

Make kitchens more secure with kitchen roles phase 2!

Earlier this year, DataKitchen released the limited availability kitchen roles feature as a way for customers to be more granular with kitchen user access. This release introduces updates to the kitchen roles feature.

Summary of updates

  • Available user roles have been expanded from two to any number of custom roles, created on request.
  • Roles can be configured, by request, with custom combinations of permissions from a fixed list.
  • The system setting, Kitchen Creator, can be assigned a pre-defined kitchen role, so users who create child kitchens have a specific set of permissions upon creation.
  • Only users with the appropriate permissions can manage a kitchen's user list.
  • Users cannot remove their own accounts from a kitchen list.
  • Available actions, such as deleting a kitchen or changing recipes, are hidden or disabled for users who do not have the correct permissions.
  • All kitchens with kitchen roles activated are now tagged with a type. Kitchens are sandbox by default but can be changed to static by users with the necessary permissions.
  • Static kitchens cannot be deleted by users unless a user has the necessary permissions to do so.

For complete details, see Manage Kitchen Access, Kitchen Security, Set Kitchen Type, and Delete Kitchens.

Visual examples in Automation

The kitchen Users list includes role options set up for your Automation environment.

(Screenshot of kitchen user list)

Users with the correct permissions can tag a kitchen as static in the Advanced tab.

(Screenshot of kitchen type settings)

Other fixes and enhancements

  • Previously, if a recipe variation included a conditional node, order runs would log a storage error and the order status would not update as expected when the order run finished. The issue has been fixed and the order status now updates as expected. Users will now have no issues running orders for recipe variations that use conditional nodes. [DEV-9913]
  • We applied general fixes to reduce errors and made various improvements to our user experience. Our help documentation has been updated to reflect these changes.

Automation library upgrades

This section of release notes reports changes made to Python, AngularJS, and other libraries used by Automation.

No changes were made in this release.