DataKitchen DataOps Documention

Kitchen Staff

Introduction

Every kitchen is defined in part by a Kitchen Staff, which dictates the specific users that may enter the kitchen to perform specific operations.

UI Access and Management

From the Kitchens page, click the wrench icon adjacent to a kitchen to edit its kitchen staff.

From the Kitchens page, click the wrench icon adjacent to a kitchen to edit its kitchen staff.

On the Recipe page, click the wrench icon adjacent to the kitchen name to configure the kitchen staff.

On the Recipe page, click the wrench icon adjacent to the kitchen name to configure the kitchen staff.

Access may be granted to all users or to a specific subset.

Access may be granted to all users or to a specific subset.

CLI Access and Management

~ $

Distinct Version Control

The kitchen staff configuration is stored outside of a kitchen's underlying version control branch. As a result, recipes may be merged across kitchens without impacting the kitchen staffs of the source and target kitchens involved with a merge or deployment. In other words, recipes are portable across kitchens and release environments.

Closed Kitchens

Kitchens are closed to users who do not hold kitchen staff rights.

If a user is not a member of a kitchen staff, that kitchen is closed to her, and she cannot grant herself kitchen staff membership.

If a user is not a member of a kitchen staff, that kitchen is closed to her, and she cannot grant herself kitchen staff membership.

~ $ dk kitchen-list
Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the list of kitchens
kitchen-list returned 11 kitchens

+---- master (closed)
    +---- demo_production (closed)
        +---- demo_dev 
            +---- demo_dev_priya 
            +---- demo_dev_veric (closed)
    +---- marketing_production (closed)
        +---- marketing_dev 
    +---- template_production (closed)
        +---- template_dev 
            +---- template_dev_priya 
            +---- template_dev_veric 
~ $ dk recipe-list --kitchen master
Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the list of Recipes for Kitchen 'master'
Error: Could not get the requested data.
Insufficient Permission to Access kitchen 'master'.

Protected Deployments

Users may merge recipes from a source to target kitchen either via the DataKitchen UI or command line tool. When the source and target kitchens are pointed at different release environments, the merge is known as a Deployment.

All merges, including deployments, are blocked if the user executing the merge is not a member of the target kitchen's staff.

~ $ dk kitchen-merge-preview --source_kitchen demo_dev --target_kitchen demo_production
Current context is: default
The root path for your kitchens was not found, skipping local checks.
YYYY-MM-DD HH:MM:SS - Previewing merge Kitchen demo_dev into Kitchen demo_production
Error: DKCloudCommandRunner Error.
Could not get the requested data.
Insufficient Permission to Access kitchen 'demo_production'. 

Protected Merges may be Available via the Opposite Direction

If a user does not hold membership in the source kitchen's staff but is a member of the target kitchen's staff, they can execute a merge.

For example, a user may have no rights or access to a kitchen pointed at a Production Release Environment, so he or she cannot deploy from a kitchen pointed at a Development Release Environment to the production-associated Kitchen. Still, he or she can merge changes downward from Production to their development-associated kitchen when needed.

Kitchen Staff Rights

As discussed, without kitchen staff membership, users may not enter kitchens via the UI, edit the kitchen's staff, or merge/deploy changes to the kitchen. Kitchen staff membership also provides users the ability to:

Manage Associated Agents

Edit Vault Connections or Secrets

Edit Toolchain Connection Configurations

View or Edit Recipes (UI)

Get Local Copies of Recipes (CLI)

Cook Orders or Alter Existing Orders

Edit Alert Configurations

Updated 5 days ago


Next Up:

Toolchain

Kitchen Staff


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.