Create Kitchens

Create a child kitchen to do work and make modifications, without impacting the work of others. Child kitchens inherit the kitchen user list, overrides, and recipe copies from the parent kitchen.

The UI uses a multi-step wizard to create kitchens. It includes a step to add ingredients, a step for alerts, a step for vault customization, and more. To avoid the non-mandatory steps, click Skip Optionals.

Note

The underlying file for the kitchen wizard is only accessible and editable by authorized users in the DKCloudCommand interface. The UI does not provide this functionality. For more information, see the Kitchen Settings command.

How to

You can create a kitchen from any page in the UI, but only from the kitchens that you have access to.

To start, click Create Child Kitchen to the right of an existing kitchen's name.

1. Step 1: Describe the Kitchen
   1. Enter a unique name.
   2. Optional. Enter a description.
   3. When done, click Next or Skip Optionals.

2. Optional. Step 2: Configure Alerts

   Warning

   If you set any Warning or Time limit exceeded alerts, you must set thresholds to trigger those alerts per each variation.

   1. Enter an email address and select the order run events that will trigger emails.

      See Alerts for more information.

   2. Click to remove a recipient.

   3. Click Add Recipient to add another email address.
   4. If alerts are set in the parent kitchen, click Add Recipients from Parent to import the same alerts.
   5. When done, click Next or Skip Optionals.

3. Optional. Step 3: Select Recipes

   1. Check the boxes for the recipes you want to include in the child kitchen at creation.

      By default, the list includes all recipes found in version control and selects the recipes that are active in the parent kitchen.

   2. When done, click Next or Skip Optionals.

4. Optional. Step 4: Select Ingredients

   1. Select an ingredient variation from the list.

   2. To activate the ingredient variation for the kitchen creation process, check Run this ingredient.

      Note that ingredients set as mandatory are activated by default and cannot be edited.

   3. Enter details in any ingredient fields that appear.

      Note that some ingredient variations are configured to require inflowing variables.

   4. When done, click Next or Skip Optionals.

5. Optional. Step 5: Configure Vault

   1. Select a vault service.

      Note the option to inherit the vault service from the parent kitchen is available only if it is a custom vault that is configured as inheritable.

   2. When done, click Next.

6. Step 6: Summary

   1. Review the child kitchen configuration.
   2. Click Previous to return to a previous step and make modifications.
7. Click Create Kitchen.

Tip

DKCloudCommand option: Use the kitchen-create command in the command line interface.

Considerations

• Kitchen names must be unique. Your kitchen name cannot duplicate a kitchen name already in use within the Automation tenant. Object names in the system are not case-sensitive, so you cannot create "Test_Kitchen" if "test_kitchen" already exists. See Naming Conventions for more information.
• At any step, click Cancel to close the wizard without creating a child kitchen.
• Click Previous to return to a previous step in the wizard.
• There is no limit to the number of kitchens that can be created. Be mindful that an overabundance of kitchens may cause slowness in the UI. Best practice is to remove old kitchens or those no longer in use; try scheduling a kitchen cleanup once per quarter.

Next steps

After creating the child kitchen, continue by configuring the kitchen's settings. See Configure Kitchens for more information.

Visual example in Automation

Step 4: Select Ingredients