Skip to content

6 July 2020 Release Notes

Version 1.1.173

Feature Highlights

New Commands Enable Kitchen Merge Rollbacks

This release introduces two new commands in the DataKitchen command line interface, DKCloudCommand. The kitchen-history and kitchen-revert commands are both associated with improvements to kitchen merge operations across the platform. Together, they provide a process for rolling back the results of a kitchen merge to prevent bad code from affecting production environments.

Similar to the Kitchen History page in the web app, the output of the kitchen-history (kh) command shows the record of kitchen updates, or Git commits, associated with a kitchen's Git branch. When users revert a kitchen merge, the history report is vital for confirming the outcome. See Kitchen History Page and Commands & Options XREFHERE for more information.

dk kitchen-history --help
Usage: dk kitchen-history [OPTIONS]

  Get Kitchen history

Options:
  -k, --kitchen TEXT   kitchen name
  -c, --count INTEGER  Number of commits to display
  --help               Show this message and exit.

The new kitchen-revert command and its shortcut kr enable users to rollback any kitchen to its previous state. It can revert kitchen merges—with or without merge conflict resolutions—or single updates. See Revert Kitchens and Commands & Options XREFHERE for more information. [DEV-6455]

dk kitchen-revert --help
Usage: dk kitchen-revert [OPTIONS]

  Revert latest kitchen commit (can be a merge or a simple commit)

Options:
  -k, --kitchen TEXT  kitchen name
  -y, --yes           Force yes
  --help              Show this message and exit.

Other Fixes & Enhancements

New System Variables Added: This release introduces two new system variables. These variables will not appear in variables drop-down lists in the web app until a future release, but users may manually write them in and use them via the command line interface. See System Variables Reference for more information. [DEV-6387, DEV-6136]

  • {{ParentKitchen}} can be compiled any time and resolves to the name of the parent kitchen of the kitchen in which the variable is called.
  • ResumedOrderRunId is compiled at runtime of a resumed order and resolves to the order run ID of the original failed order run.

Report Issue Form Working: A recent update caused errors in the support request form accessed from the help icon in the web app. This issue has been resolved; the form works as expected. [DEV-6587]

()

The Report Issue form that opens from this menu is working properly.

Kitchen Names Can Start with Underscores: When users created kitchens named with initial underscore characters, they received errors when running orders. This issue has been resolved, and the platform allows the use of initial underscores in naming kitchens. [DEV-6301]

()

Kitchen names can begin with underscore characters.

Step Validation Corrected for Action Nodes: When users added a step to an action node and selected "None" for the Result Type, they saw an error icon on the Steps tab and could not update the node. The system was incorrectly detecting the result type selection as invalid. This issue has been resolved by updating the validation rules. [DEV-6607]

Node Editor Recognizes No Updates: Under certain circumstances, users who opened a node in the Node Editor and then left the page without making changes encountered an Unsaved Changes dialog. This issue has been resolved with an update to the Node Editor. [DEV-6572]

System Executes Empty Script Files: Users who added a script file to a container node but left the script empty found that the node failed at runtime with a logged error, "No such file or directory." This issue has been resolved with an enhanced check for empty files that allows empty scripts to execute normally. [DEV-3374]