Skip to content

22 February 2022 Release Notes

Version 1.1.242. Note that versions 1.1.237 through 1.1.241 were deployed to DataKitchen testing environments only.

Feature Highlights

Delete Kitchen Function Relocated

Recent redesigns of the delete kitchen process made it much easier for users to delete their temporary workspaces. It also, however, made it much easier for users to mistakenly delete other, more permanent kitchens to which they have access!

To address this risk, DataKitchen has moved the delete function from kitchen tools and from the merge kitchens process to a tab in the Configure Kitchen page. Users will notice that the trash can button no longer appears among the tools, and the dialogs for merging a child kitchen up to its parent do not offer the options to delete the child kitchen after the merge or execute rollback ingredients. See Configure Kitchens, Merge Kitchens, and Delete Kitchens for more information. [DEV-9537]

()   ()

Delete Kitchen buttons have been removed from the Kitchens page and green toolbar.

()

The option to delete the child kitchen and execute rollback ingredients have been removed from the Merge Kitchen process.

()

The delete kitchen function has moved to the Configure Kitchen page.

Variations Can Require Runtime Overrides of Variables

Because a production engineer running a variation may not be the DataOps recipe builder who configured the variation, that engineer may not know which variable values are required for the variation to run properly. He or she may not know that default variables may require override values for a particular use case, or that empty variables may require value inputs for any run to avoid ending on errors.

This product release helps prevent this confusion with updates to the variables tables on the Variation page and in the Run Variation dialog. Now, a user of the Automation webapp can set the following order override constraints for any variable. The command line interface (CLI) does not yet support these constraints.

Value Entry Restrictions

  • Optional override value: (Default setting) The user may enter an override value at runtime or not.
  • Required override value: The user must enter an override value for this variable at runtime. Required variables do not need to have default values defined.
  • Locked to order overrides: The users cannot override the value of this variable at runtime.
  • Hidden at runtime: The user will not see this variable in the Run Variation dialog when submitting an order.

Data Formats

  • Data type: Select String, Number, Boolean, JSON to require a specific format for an order override. The default value is the current data type of the base, variation override, or kitchen override variable. Data types are not displayed for variables with the locked and hidden constraints.

Page Previews

Take a quick tour of the updates to the Variation page and the Run Variation dialog.

()

The new Order Override Constraints column in the Variables tab allows you to set requirements for runtime value entry.

Note

Default Constraints for Existing Variables: The platform sets all variables that are already configured in variations at the time of this release with the default "Optional" constraint for order override values. The data type is set to the type of the current value of each variable.

()

Along side the search field, a new filter function enables users to find variables fast.

()

Labels and highlights in the Run Variation dialog call out required overrides and variable values that have been edited.

Other Fixes & Enhancements

Errors Logged for File and Connection Problems: A user encountered an unexpected error during node processing that seemed to be related to vault secrets. After investigation, it became clear that an attempt to download an Amazon S3 source file failed because the file was not present. Upon further investigation, the support team found that problems reading files from certain data sources, problems writing files to SFTP, and problems connecting to MySQL were not properly logged. This issue has been resolved by printing log entries when any of these issues occur. [DEV-9705]