DataKitchen DataOps Documention

Usage Examples

active-serving-watcher (asw)

~ $ dk active-serving-watcher --help



Current context is: default
Usage: dk active-serving-watcher [OPTIONS]

  Watches all cooking Recipes in a Kitchen. Provide the Kitchen name as an
  argument or be in a Kitchen folder. Optionally provide a watching period
  as an integer, in seconds. Ctrl+C to terminate.

Options:
  -k, --kitchen TEXT      Kitchen name
  -i, --interval INTEGER  watching interval, in seconds
  --help                  Show this message and exit.
~/Kitchens/Dev_Sprint $ dk active-serving-watcher --interval 5


Current context is: default
YYYY-MM-DD HH:MM:SS - Watching Active OrderRun Changes in Kitchen Dev_Sprint:
watching ...
Recipe-Template(382db..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(382db..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(382db..) total-recipe-time:  HH:MM:SS
Recipe-Template(382db..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(382db..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(382db..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(382db..) node1: timing:  HH:MM:SS
Recipe-Template(cace2..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(cace2..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(cace2..) total-recipe-time:  HH:MM:SS
Recipe-Template(cace2..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(cace2..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(cace2..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(beb9b..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(beb9b..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(beb9b..) total-recipe-time:  HH:MM:SS
Recipe-Template(beb9b..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(beb9b..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(beb9b..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) total-recipe-time:  HH:MM:SS
Recipe-Template(ae62b..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(ae62b..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) node1: timing:  HH:MM:SS
Recipe-Template(2b8ea..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(2b8ea..) total-recipe-time:  HH:MM:SS
Recipe-Template(2b8ea..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(2b8ea..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(2b8ea..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(2b8ea..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(2b8ea..) node1: timing:  HH:MM:SS
watching ...
~ $ dk asw -k Dev_Sprint -i 5


Current context is: default
YYYY-MM-DD HH:MM:SS - Watching Active OrderRun Changes in Kitchen Dev_Sprint:
watching ...
Recipe-Template(382db..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(382db..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(382db..) total-recipe-time:  HH:MM:SS
Recipe-Template(382db..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(382db..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(382db..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(382db..) node1: timing:  HH:MM:SS
Recipe-Template(cace2..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(cace2..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(cace2..) total-recipe-time:  HH:MM:SS
Recipe-Template(cace2..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(cace2..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(cace2..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(beb9b..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(beb9b..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(beb9b..) total-recipe-time:  HH:MM:SS
Recipe-Template(beb9b..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(beb9b..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(beb9b..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) total-recipe-time:  HH:MM:SS
Recipe-Template(ae62b..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(ae62b..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(ae62b..) node1: timing:  HH:MM:SS
Recipe-Template(2b8ea..) end-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(2b8ea..) total-recipe-time:  HH:MM:SS
Recipe-Template(2b8ea..) start-time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(2b8ea..) synchronize-node: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(2b8ea..) synchronize-node: timing:  HH:MM:SS
Recipe-Template(2b8ea..) node1: start_time:  YYYY-MM-DD HH:MM:SS
Recipe-Template(2b8ea..) node1: timing:  HH:MM:SS
watching ...

agent-status (as)

~ $ dk agent-status --help



Current context is: default
Usage: dk agent-status [OPTIONS]

  Provides information about the agent status.

Options:
  --help  Show this message and exit.
~ $ dk agent-status



Current context is: default
YYYY-MM-DD HH:MM:SS - Getting Agent Status Information
-----------
Agent is Online
Total available memory: XXXXX MB
Total available disk space: XXXXX MB

config (c)

~ $ dk config --help



Current context is: default
Usage: dk config [OPTIONS]

  Configure Command Line.

Options:
  -f, --full     General and context configuration
  -c, --context  Context configuration
  -g, --general  General configuration
  --help         Show this message and exit.
~ $ dk config --full


Current context is: default
Enter username: <USERNAME>
Enter password: <PASSWORD>
DK Cloud Address (default https://cloud.datakitchen.io): <ENTER>
DK Cloud Port (default 443): <ENTER>
 
DK Cloud Merge Tool Template (default None):meld {{left}} {{base}} {{right}}
DK Cloud File Diff Tool Template (default None):meld {{local}} {{remote}}
Check current working path against existing contexts?[yes/No] (default No):yes
 
 
Name:           <USERNAME>
Email:          <PASSWORD>
Customer Name:      <CUSTOMER>
Support Email:      [email protected]
Role:           <ROLE>
~ $ dk c -g


Current context is: default
DK Cloud Merge Tool Template (default None):/usr/local/bin/charm merge {{left}} {{right}} {{base}}
DK Cloud File Diff Tool Template (default None):/usr/local/bin/charm diff {{local}} {{remote}}
Check current working path against existing contexts?[yes/No] (default No):yes


Configuration changed!.
~ $ dk config -c


Current context is: default
Enter username: <USERNAME>
Enter password: <PASSWORD>
DK Cloud Address (default https://cloud.datakitchen.io): <ENTER>
DK Cloud Port (default 443): <ENTER>



Configuration changed!.

config-list (cl)

~ $ dk config-list --help



Current context is: default
Usage: dk config-list [OPTIONS]

  Print the current configuration.

Options:
  --help  Show this message and exit.
~ $ dk cl


Current context is: default
Current configuration is ...
Customer Name:                  <CUSTOMER>
Context:                        default
Config Location:                {USER_HOME}/.dk/default/config.json
General Config Location:        {USER_HOME}/.dk/general-config.json
Username:                       <USERNAME>
Password:                       <PASSWORD>
Cloud IP:                       https://cloud.datakitchen.io
Cloud Port:                     443
Merge Tool:                     /usr/local/bin/charm merge {{left}} {{right}} {{base}}
Diff Tool:                      /usr/local/bin/charm diff {{local}} {{remote}}
Check Working Path:             True

context-delete (cd)

~ $ dk context-delete --help



Current context is: default
Usage: dk context-delete [OPTIONS] CONTEXT_NAME

  Deletes a context.

Options:
  -y, --yes  Force yes
  --help     Show this message and exit.
~ $ dk context-delete example_context


Current context is: default
Credential information will be lost.
Are you sure you want to delete context test? [yes/No]yes
Deleting context example_context  ...

Done!
~ $ dk cd example_context -y


Current context is: default
Deleting context example_context  ...

Done!

context-list (xl)

~ $ dk context-list --help



Current context is: default
Usage: dk context-list [OPTIONS]

  List available contexts.

Options:
  --help  Show this message and exit.
~ $ dk xl


Current context is: default
Available contexts are ...

Context1
Context2
Context3
default

context-switch (cs)

~ $ dk context-switch --help



Current context is: default
Usage: dk context-switch [OPTIONS] CONTEXT_NAME

  Create or switch to a new context.

Options:
  -y, --yes  Force yes
  --help     Show this message and exit.
~ $ dk context-switch new_context

Current context is: default
Context does not exist. Are you sure you want to create context new_context? [yes/No]yes
Switching to context new_context ...

Enter username: <USERNAME>
Enter password: <PASSWORD>
DK Cloud Address (default https://cloud.datakitchen.io): <ENTER>
DK Cloud Port (default 443): <ENTER>



Context switch done.
Use dk user-info and dk config-list to get context details.
~ $ dk cs new_context2 -y


Current context is: default
Switching to context new_context2 ...

Enter username: <USERNAME>
Enter password: <PASSWORD>
DK Cloud Address (default https://cloud.datakitchen.io): <ENTER>
DK Cloud Port (default 443): <ENTER>



Context switch done.
Use dk user-info and dk config-list to get context details.
~ $ dk context-switch other_context
Current context is: default
Switching to context other_context ...
Context switch done.
Use dk user-info and dk config-list to get context details.

file-compile (fc)

~ $ dk file-compile --help



Current context is: default
Usage: dk file-compile [OPTIONS]

  Apply variables to a file based on a provided Variation.

Options:
  -v, --variation TEXT  variation name  [required]
  -f, --file TEXT       file path  [required]
  --help                Show this message and exit.
~/Kitchens/Feature_Sprint/Recipe1 $ dk fc -v Variation1 -f resources/s3-to-redshift.sql


Current context is: default
YYYY-MM-DD HH:MM:SS - Get the Compiled File of Recipe Recipe1.Variation1 in Kitchen Feature_Sprint
DKCloudCommand.get_compiled_file succeeded:
SET search_path TO hwproduction;

DROP TABLE if exists DEMO_SUPERSTORE_CUSTOMER_SEGMENT CASCADE;
CREATE TABLE DEMO_SUPERSTORE_CUSTOMER_SEGMENT
(
  Customer_ID      VARCHAR(100),
  Sales            NUMERIC(14,3),
  Profit           NUMERIC(14,3),
  Segment          VARCHAR(50)
);


copy DEMO_SUPERSTORE_CUSTOMER_SEGMENT
from 's3://dk-hello-world/superstore/customer/segment'
credentials 'aws_iam_role=arn:aws:iam::${vault://aws/account_id}:role/DKRedshift-for-HelloWorld'
ignoreheader 1
TRIMBLANKS delimiter '|';

select count(*) from DEMO_SUPERSTORE_CUSTOMER_SEGMENT;

file-delete (fd)

~ $ dk file-delete --help



Current context is: default
Delete one or more Recipe files. If you are not in a recipe path, provide
  the file path(s) relative to the recipe root. Separate multiple file paths
  with spaces.  File paths need no preceding backslash.

  To delete the directory, delete all files in that directory and then the
  directory will automatically be deleted.

  Example...

  dk file-delete -m "my delete message" file1.json dir2/file2.json

Options:
  -k, --kitchen TEXT  kitchen name
  -r, --recipe TEXT   recipe name
  -m, --message TEXT  change message  [required]
  --help              Show this message and exit.
~/Kitchens/Dev_Sprint/Demo_Recipe $ dk file-delete --message "Change message." file1.json resources/file2.sql node1/file3.json


Current context is: default
YYYY-MM-DD HH:MM:SS - Deleting ((u'file1.json', u'resources/file2.sql')) in
Recipe (Recipe1) in kitchen(Feature_Sprint) with message (Change message)
DKCloudCommand.delete_file for file1.json succeed on local delete
DKCloudCommand.delete_file for file1.json succeed on remote delete
DKCloudCommand.delete_file for resources/file2.sql succeed on local delete
DKCloudCommand.delete_file for resources/file2.sql succeed on remote delete
~ $ dk fd -k Feature_Sprint -r Recipe1 -m "Change message" file1.json


Current context is: default
YYYY-MM-DD HH:MM:SS - Deleting ((u'file1.json',)) in Recipe (Recipe1) in 
kitchen(Feature_Sprint) with message (Change message)
DKCloudCommand.delete_file for file1.json succeed on local delete
DKCloudCommand.delete_file for file1.json succeed on remote delete

file-diff (fdi)

~ $ dk file-diff --help



Current context is: default
Usage: dk file-diff [OPTIONS] FILEPATH

  Show differences with remote version of the file.

Options:
  -k, --kitchen TEXT kitchen name
  -r, --recipe TEXT  recipe name
  --help                      Show this message and exit.
~/Kitchens/Feature_Sprint/Recipe1/resources $ dk file-diff test.sql


Current context is: default
YYYY-MM-DD HH:MM:SS - File Diff for file test.sql, in Recipe (Recipe1) in Kitchen (Feature_Sprint)
Executing command: /usr/local/bin/charm diff ~/Kitchens/Feature_Sprint/Recipe1/variables.json {USER_HOME}/.dk/diffs/Feature_Sprint/Recipe1/variables.json

File diff done.
~/Kitchens $ dk fdi -k Feature_Sprint -r Recipe1 variables.json


Current context is: default
YYYY-MM-DD HH:MM:SS - File Diff for file variables.json, in Recipe (Recipe1) in Kitchen (Feature_Sprint)
Executing command: /usr/local/bin/charm diff ~/Kitchens/Feature_Sprint/Recipe1/variables.json {USER_HOME}/.dk/diffs/Feature_Sprint/Recipe1/variables.json

File diff done.

file-get (fg)

~ $ dk file-get --help



Current context is: default
Usage: dk file-get [OPTIONS] FILEPATH

  Get the latest version of a file from the server and overwrite your
  local copy.

Options:
  --help  Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk fg variables.json


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting File (variables.json) to Recipe (Recipe1) in Kitchen (Testing)
DKCloudCommand.file_get for variables.json success

file-history (fh)

~ $ dk file-history --help



Current context is: default
Usage: dk file-history [OPTIONS] FILEPATH

  Show file change history.

Options:
  -cc, --change_count INTEGER  Number of last changes to display
  --help                       Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk fh --cc 5


Current context is: default
YYYY-MM-DD HH:MM:SS - Retrieving file history
DKCloudCommand.file_history succeeded:
Author:	John Smith <[email protected]>
Date:	YYYY-MM-DD HH:MM:SS
Commit: 1325768c8048f96ed15350b9374fc95f3cefeb1f
Message:Merge Feature_Sprint Kitchen into Dev_Sprint Kitchen

Author:	John Smith <[email protected]>
Date:	YYYY-MM-DD HH:MM:SS
Commit: 585d9667c7442e53b953bae3a50908619d378eb7
Message:Update graph.json nodes and edges

Author:	John Smith <[email protected]>
Date:	YYYY-MM-DD HH:MM:SS
Commit: b7edf5434a8a3e362f3f1c69452494cefd597bd4
Message:Recipe update for new node

Author:	John Smith <[email protected]>
Date:	YYYY-MM-DD HH:MM:SS
Commit: 71e2d76a7b0c46e53a51bb196d62cdb24f1ee182
Message:Update graph.json

Author:	John Smith <[email protected]>
Date:	YYYY-MM-DD HH:MM:SS
Commit: f0db74b10545050344fa2180eff13ede33e2a05e
Message:Debug graph.json syntax

file-merge (fm)

~ $ dk file-merge --help



Current context is: default
Usage: dk file-merge [OPTIONS] FILEPATH

  To be used after kitchen-merge-preview command. Launch the merge tool of
  choice, to resolve conflicts. File path needs to be stated as it is coming
  from kitchen-merge-preview output.

Options:
  -sk, --source_kitchen TEXT  source (from) kitchen name  [required]
  -tk, --target_kitchen TEXT  target (to) kitchen name  [required]
  --help                      Show this message and exit.
~/Kitchens/Feature_Sprint $ dk file-merge --target_kitchen Dev_Sprint Recipe1/variables.json


Current context is: default
YYYY-MM-DD HH:MM:SS - File Merge for file Recipe1/variables.json, source kitchen (Feature_Sprint), target kitchen(Dev_Sprint)
Executing command: /usr/local/bin/charm merge {USER_HOME}/.dk/merges/Feature_Sprint_to_Dev_Sprint/Recipe1/variables.json.left {USER_HOME}/.dk/merges/Feature_Sprint_to_Dev_Sprint/Recipe1/variables.json.base {USER_HOME}/.dk/merges/Feature_Sprint_to_Dev_Sprint/Recipe1/variables.json.right

File merge done. Remember to mark the file as resolved with the command: dk file-resolve
~/Kitchens $ dk fm -sk Feature_Sprint -tk Dev_Sprint Recipe1/variables.json


Current context is: default
YYYY-MM-DD HH:MM:SS - File Merge for file Recipe1/variables.json, source kitchen (Feature_Sprint), target kitchen(Dev_Sprint)
Executing command: /usr/local/bin/charm merge {USER_HOME}/.dk/merges/Feature_Sprint_to_Dev_Sprint/Recipe1/variables.json.left {USER_HOME}/.dk/merges/Feature_Sprint_to_Dev_Sprint/Recipe1/variables.json.base {USER_HOME}/.dk/merges/Feature_Sprint_to_Dev_Sprint/Recipe1/variables.json.right

File merge done. Remember to mark the file as resolved with the command: dk file-resolve

file-resolve (fr)

~ $ dk file-resolve --help



Current context is: default
Usage: dk file-resolve [OPTIONS] FILEPATH

  Mark a conflicted file within a Recipe as resolved, so that a merge 
  can be completed.

Options:
  -sk, --source_kitchen TEXT  source (from) kitchen name
  -tk, --target_kitchen TEXT  target (to) kitchen name  [required]
  --help  		      Show this message and exit.
~/Kitchens/Feature_Sprint/Recipe1 $ dk fr variables.json


Current context is: default
YYYY-MM-DD HH:MM:SS - Resolving conflicts:

1 conflict resolved
	Conflicted files in recipe 'Recipe1'
		Recipe1/variables.json

file-update (fu)

~ $ dk file-update --help



Current context is: default
Usage: dk file-update [OPTIONS] FILEPATH...

  Update the server copy of one or more existing Recipe files based on you
  local  changes, or add one or more new Recipe files.  Requires inclusion of
  a change message.
  
Example...

dk file-update -m "my update message" file1.json dir2/file2.json

Options:
  -k, --kitchen TEXT  kitchen name
  -r, --recipe TEXT   recipe name
  -m, --message TEXT  change message  [required]
  --help              Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk file-update --message "Change message" variables.json


Current context is: default
YYYY-MM-DD HH:MM:SS - Updating File(s):
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Message:  Change message
 
DKCloudCommand.update_file for variables.json succeeded
~ $ dk fu -k Dev_Sprint -r Recipe1 -m "Change message" variables.json variations.json resources/newfile.json


Current context is: default
YYYY-MM-DD HH:MM:SS - Updating File(s):
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Message:  Change message

Adding: resources/newfile.json
 
DKCloudCommand.update_file for variables.json succeeded
DKCloudCommand.update_file for variations.json succeeded
DKCloudCommand.update_file for resources/newfile.json succeeded

git-setup (gs)

~ $ dk git-setup



Current context is: default
Usage: dk git-setup [OPTIONS]

  Set up a GIT repository for DK CLI.  Authentication will remain via GIT user
  but commits will be tagged with DK username and email address.

Options:
  --help  Show this message and exit.
~/New_Repository $ dk git-setup



Current context is: default

kitchen-config (kf)

~ $ dk kitchen-config --help



Current context is: default
Usage: dk kitchen-config [OPTIONS]

  Get and set Recipe variable overrides. 
  
  Example:
  dk kf -k Dev_Sprint -a kitchen_override 'value1'

Options:
  -k, --kitchen TEXT      kitchen name
  -a, --add TEXT          Add a new override to this kitchen. This will update 
                          an existing override variable.
                          Usage:  --add VARIABLE VALUE
                          Example:  -a kitchen_override 'value1'
  -g, --get TEXT          Get the value for an override variable.
  -u, --unset TEXT        Delete an override variable.
  -la, --listall          List all variables and their values.
  --help                  Show this message and exit.
~/Kitchens/Dev_Sprint $ dk kitchen-config --listall


Current context is: default
Recipe Overrides
 Variable Name            Value                   
 ----------------         ----------------        
 override1            		value1                 
 override2             		value2
 override3            		value3
~/Kitchens/Dev_Sprint $ dk kitchen-config --get override1


Current context is: default
value1
~ $ dk kf -k Dev_Sprint -u override1


Current context is: default
override1 unset
~ $ dk kf -k Dev_Sprint -a kitchen_override 'value1'


Current context is: default
kitchen_override added with value 'value1'

kitchen-create (kc)

~ $ dk kitchen-create --help



Current context is: default
Usage: dk kitchen-create [OPTIONS] KITCHEN

  Create and name a new child Kitchen. Provide parent Kitchen name.

Options:
  -p, --parent TEXT  name of parent kitchen  [required]
  -d, --description  Kitchen description
  --help             Show this message and exit.
~ $ dk kc -p Dev_Sprint -d "Personal dev Kitchen." Feature_Sprint


Current context is: default
YYYY-MM-DD HH:MM:SS - Creating Kitchen Feature_Sprint from Parent Kitchen Dev_Sprint

DKCloudCommand.create_kitchen created Dev_Sprint
~ $ dk kc -p Dev_Sprint -d "Personal dev Kitchen." Feature_Sprint


Current context is: default
YYYY-MM-DD HH:MM:SS - Creating Kitchen 'Feature_Sprint' from Parent Kitchen 'Dev_Sprint'

There are recipe overrides at the parent Kitchen, which were inherited by the new Kitchen:
Variable: sample-override

DKCloudCommand.create_kitchen created Dev_Sprint

kitchen-delete (kd)

~ $ dk kitchen-delete --help



Current context is: default
Usage: dk kitchen-delete [OPTIONS] KITCHEN

  Delete the server copy of a Kitchen.

Options:
  -y, --yes           Force yes
  --help  Show this message and exit.
~ $ dk kd Dev_Sprint -y


Current context is: default
The following child kitchens to parent Dev_Sprint will be orphaned:
+---- Feature_Sprint_1
+---- Feature_Sprint_2

YYYY-MM-DD HH:MM:SS - Deleting remote copy of kitchen Dev_Sprint.  Local files will not change.
><
Kitchen Dev_Sprint has been deleted
~ $ dk kitchen-delete Feature_Sprint


Current context is: default
Children kitchens for kitchen Feature_Sprint:
No children kitchens found.

Are you sure you want to delete the Kitchen? [yes/No]yes

YYYY-MM-DD HH:MM:SS - Deleting remote copy of kitchen Feature_Sprint. Local files will not change.
><
Kitchen Feature_Sprint has been deleted
~ $ dk kitchen-delete Kitchen_Parent --yes



Current context is: default
The following child kitchens to parent Kitchen_Parent will be orphaned:
+---- Kitchen_Child 

YYYY-MM-DD HH:MM:SS - Deleting remote copy of kitchen Kitchen_Parent. Local files will not change.
Error: Kitchen Kitchen_Parent has child kitchens inheriting vault config, delete child kitchens first

kitchen-get (kg)

~ $ dk kitchen-get --help



Current context is: default
Usage: dk kitchen-get [OPTIONS] KITCHEN_NAME

  Get an existing Kitchen locally. You may also get one or multiple Recipes
  from the Kitchen.

Options:
  -r, --recipe TEXT  Get the recipe along with the kitchen. Multiple allowed
  -a, --all          Get all recipes along with the kitchen.
  --help             Show this message and exit.
~/Kitchens $ dk kitchen-get Dev_Sprint


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting kitchen 'Dev_Sprint'
Got Kitchen 'Dev_Sprint'
~/Kitchens $ dk kitchen-get --kitchen Dev_Sprint --recipe Recipe1 --recipe Recipe2


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting kitchen 'Dev_Sprint'
list_recipe - elapsed: 0
Got Kitchen 'Dev_Sprint'
DKCloudCommand.get_recipe has 4 sections
  Recipe1/node1
  Recipe1/resources
  Recipe1
  Recipe1/node2
  
 DKCloudCommand.get_recipe has 6 sections
  Recipe2/node1
  Recipe2/resources
  Recipe2
  Recipe2/node2
  Recipe2/action-node
  Recipe2/action-node/actions
~/Kitchens $ dk kg Dev_Sprint -a


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting kitchen 'Dev_Sprint'
list_recipe - elapsed: 0
Got Kitchen 'Dev_Sprint'
DKCloudCommand.get_recipe has 4 sections
  Recipe1/node1
  Recipe1/resources
  Recipe1
  Recipe1/node2
  
 DKCloudCommand.get_recipe has 6 sections
  Recipe2/node1
  Recipe2/resources
  Recipe2
  Recipe2/node2
  Recipe2/action-node
  Recipe2/action-node/actions  
  
 DKCloudCommand.get_recipe has 9 sections
  Recipe3/node1
  Recipe3/resources
  Recipe3
  Recipe3/node2
  Recipe3/action-node
  Recipe3/action-node/actions
  Recipe3/data-source-container-node
  Recipe3/data-source-action-node/actions
  Recipe3/data-source-action-node/actions/docker-share

kitchen-history (kh)

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.
~/Kitchens $ dk kitchen-history --kitchen Dev_Sprint --count 3

YYYY-MM-DD HH:MM:SS - Getting kitchen history for kitchen Dev_Sprint.
--
author  : [email protected]
date    : YYYY-MM-DDTHH:MM:SSZ
message : Merge from Feature_Sprint to Dev_Sprint
sha     : adcfa6aae8ee7935881e1bd3a151efed5cbd033d
--
author  : [email protected]
date    : YYYY-MM-DDTHH:MM:SSZ
message : Files updated in recipe 'parallel-recipe-test': C3
sha     : f2051eccf2b08b1098e3b7ca2b2b94190f5e46d9
--
author  : [email protected]
date    : YYYY-MM-DDTHH:MM:SSZ
message : Merge from Dev_Sprint to Feature_Sprint
sha     : f57fa041595b0371db84a8267d2825a43b8de0a9
~/Kitchens $ dk kh --k Dev_Sprint --c 3

YYYY-MM-DD HH:MM:SS - Getting kitchen history for kitchen Dev_Sprint.
--
author  : [email protected]
date    : YYYY-MM-DDTHH:MM:SSZ
message : Merge from Feature_Sprint to Dev_Sprint
sha     : adcfa6aae8ee7935881e1bd3a151efed5cbd033d
--
author  : [email protected]
date    : YYYY-MM-DDTHH:MM:SSZ
message : Files updated in recipe 'parallel-recipe-test': C3
sha     : f2051eccf2b08b1098e3b7ca2b2b94190f5e46d9
--
author  : [email protected]
date    : YYYY-MM-DDTHH:MM:SSZ
message : Merge from Dev_Sprint to Feature_Sprint
sha     : f57fa041595b0371db84a8267d2825a43b8de0a9

kitchen-list (kl)

~ $ dk kitchen-list --help



Current context is: default
Usage: dk kitchen-list [OPTIONS]

  List all Kitchens to which you have access.

Options:
  --help  Show this message and exit.
~ $ dk kl


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the list of kitchens
kitchen-list returned 3 kitchens
+---- master
    +---- Dev_Sprint
        +---- Feature_Sprint
    +---- No_Access_Parent_Kitchen (closed)
        +---- No_Access_Child_Kitchen_1 (closed)
~ $ dk kl


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the list of kitchens
kitchen-list returned 3 kitchens
+---- master
    +---- Dev_Sprint
        +---- Feature_Sprint
    +---- No_Access_Parent_Kitchen (closed)
        +---- No_Access_Child_Kitchen_1 (closed)
        
Orphan Kitchens:

+---- (No parent)
        +---- No_Access_Child_Kitchen_2 (closed)

kitchen-merge (km)

~ $ dk kitchen-merge --help



Current context is: default
Usage: dk kitchen-merge [OPTIONS]

  Merge two Kitchens. Provide the names of the Source and Target Kitchens.

Options:
  -sk, --source_kitchen TEXT  source (from) kitchen name
  -tk, --target_kitchen TEXT  target (to) kitchen name  [required]
  -y, --yes           				Force yes  
  --help                      Show this message and exit.
~ $ dk kitchen-merge --source_kitchen Feature_Sprint --target_kitchen Dev_Sprint


Current context is: default
Are you sure you want to merge the Source Kitchen Feature_Sprint into the 
Target Kitchen Dev_Sprint? [yes/No]yes

YYYY-MM-DD HH:MM:SS - Merging Kitchen Feature_Sprint into Kitchen Dev_Sprint
looking for merged (.base) files in temporary directory
~/.dk/merges/Feature_Sprint_to_Dev_Sprint 
Calling Merge ...

 variations.json         0                 
1 files changed, 0 insertions(+), 0 deletions(-)
~ $ dk km -sk Feature_Sprint -tk Dev_Sprint -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Merging Kitchen Feature_Sprint into Kitchen Dev_Sprint
looking for merged (.base) files in temporary directory
~/.dk/merges/Feature_Sprint_to_Dev_Sprint 
Calling Merge ...

 variations.json         0                 
1 files changed, 0 insertions(+), 0 deletions(-)
~ $ dk km -sk Feature_Sprint -tk Dev_Sprint -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Merging Kitchen Feature_Sprint into Kitchen Dev_Sprint
looking for merged (.base) files in temporary directory
~/.dk/merges/Feature_Sprint_to_Dev_Sprint 
Calling Merge ...

1 conflict found
	Conflicted files in Recipe 'Recipe1'
		Recipe1/variables.json
~/Kitchens/Feature_Sprint $ dk kmp -tk Dev_Sprint -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Merging Kitchen Feature_Sprint into Kitchen Dev_Sprint
Error: DKCloudCommandRunner Error.
Please run kitchen-merge-preview command before running kitchen-merge

kitchen-merge-preview (kmp)

~ $ kitchen-merge-preview



Current context is: default
Usage: dk kmp [OPTIONS]

  Preview the merge of two Kitchens. No change will actually be applied.
  Provide the names of the Source (Child) and Target (Parent) Kitchens.

Options:
  -sk, --source_kitchen TEXT  source (from) kitchen name
  -tk, --target_kitchen TEXT  target (to) kitchen name  [required]
  -cpr, --clean_previous_run  Clean previous run of this command
  --help                      Show this message and exit.
~/Kitchens/Dev_Sprint $ dk kitchen-merge-preview --target_kitchen Feature_Sprint --clean_previous_run


Current context is: default
YYYY-MM-DD HH:MM:SS - Previewing merge Kitchen Dev_Sprint into Kitchen Feature_Sprint
Merge Preview Results (only changed files are being displayed):
--------------------------------------------------------------

      ok                Recipe-Template/description.json
      ok                Recipe-Template/variables.json

Kitchen merge preview done.
~/Kitchens $ dk kmp -sk Feature_Sprint -tk Dev_Sprint -cpr


Current context is: default
YYYY-MM-DD HH:MM:SS - Previewing merge Kitchen Feature_Sprint into Kitchen Dev_Sprint
Merge Preview Results (only changed files are being displayed):
--------------------------------------------------------------

      ok                Recipe-Template/graph.json
      conflict          Recipe-Template/variables.json      
      ok                Recipe-Template/variations.json
      ok                Recipe-Template/description.json

Kitchen merge preview done.
~/Kitchens $ dk kmp -sk Feature_Sprint -tk Dev_Sprint


Current context is: default
YYYY-MM-DD HH:MM:SS - Previewing merge Kitchen Feature_Sprint into Kitchen Dev_Sprint
Merge Preview Results (only changed files are being displayed):
--------------------------------------------------------------

      ok                Recipe-Template/graph.json
      resolved          Recipe-Template/variables.json      
      ok                Recipe-Template/variations.json
      ok                Recipe-Template/description.json

Kitchen merge preview done.

kitchen-revert (kr)

Use Kitchen Revert with Caution!

Note that the Kitchen Revert command line feature to rollback previous updates and merges can be dangerous! The kitchen-revert command should be used only with extreme caution!

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.
~ $ dk kitchen-revert --kitchen Dev_Sprint

YYYY-MM-DD HH:MM:SS - Reverting kitchen Dev_Sprint to previous state. Local files will not change.
After this operation, run recipe-get -o in the related recipes.
Done!
~ $ dk kr --k Dev_Sprint --y

YYYY-MM-DD HH:MM:SS - Reverting kitchen Dev_Sprint to previous state. Local files will not change.
After this operation, run recipe-get -o in the related recipes.
Done!

kitchen-settings-get (ksg)

~ $ kitchen-settings-get --help



Current context is: default
Usage: dk kitchen-settings-get [OPTIONS]

  Get Kitchen Settings (kitchen-settings.json) for your customer account.  
  This file is global to all Kitchens.  Your role must equal "IT" to get 
  the kitchen-settings.json file.

Options:
  --help  Show this message and exit.
~/Kitchens $ dk ksg


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting a local copy of kitchen-settings.json 
DKCloudCommand.kitchen_settings_get succeeded

kitchen-settings-update (ksu)

~ $ dk kitchen-settings-update --help



Current context is: default
Usage: dk kitchen-settings-update [OPTIONS] FILEPATH...

  Upload Kitchen Settings (kitchen-settings.json) for your customer account.  
  This file is global to all Kitchens.  Your role must equal "IT" to upload 
  the kitchen-settings.json file.

Options:
  --help              Show this message and exit.
~/Kitchens $ dk ksu kitchen-settings.json


Current context is: default
YYYY-MM-DD HH:MM:SS - Updating Kitchen settings

kitchen-which (kw)

~ $ dk kitchen-which --help



Current context is: default
Usage: dk kitchen-which [OPTIONS]

  What Kitchen am I working in based on my working directory?

Options:
  --help  Show this message and exit.
~/node1 $ dk kw

	
Current context is: default
YYYY-MM-DD HH:MM:SS
~/Kitchens/Dev_Sprint/Recipe1/node1

You are in kitchen 'Dev_Sprint'

order-delete (od)

~ $ dk order-delete --help



Current context is: default
Usage: dk order-delete [OPTIONS]

  Delete one Order or all Orders in a Kitchen.  Deleting an Order also
  deletes all associated OrderRuns.

Options:
  -a, --all		Delete all Orders
  -k, --kitchen TEXT   Kitchen name
  -o, --order_id TEXT  Order ID
  -y, --yes            Force yes
  --help               Show this message and exit.
~/Kitchens/Dev_Sprint $ dk order-delete --order_id c9dc1bd2-4ef6-11e8-a766-080027aceabc


Current context is: default
Are you sure you want to delete the Order? [yes/No]yes

YYYY-MM-DD HH:MM:SS - Delete an Order:
Kitchen:	Dev_Sprint
Order ID:	c9dc1bd2-4ef6-11e8-a766-080027aceabc

Deleted Order c9dc1bd2-4ef6-11e8-a766-080027aceabc
~ $ dk od -k Dev_Sprint -o c9dc1bd2-4ef6-11e8-a766-080027aceabc


Current context is: default
YYYY-MM-DD HH:MM:SS - Delete an Order:
Kitchen:	Dev_Sprint
Order ID:	c9dc1bd2-4ef6-11e8-a766-080027aceabc

Deleted Order c9dc1bd2-4ef6-11e8-a766-080027aceabc
~ $ dk od -k Dev_Sprint -a -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Delete all Orders:
Kitchen:	Dev_Sprint

Deleted 5 Orders in Kitchen 'Dev_Sprint'
  c9dc1bd2-4ef6-11e8-a766-080027aceabc
  271848fa-3d97-11e8-b513-0242ac110002
  c34b7438-419b-11e8-9702-0242ac110002
  370b358a-f7cc-11e7-988e-0242ac110002
  d202a7c0-f589-11e7-bff7-0242ac110002

order-list (ol)

~ $ dk order-list --help



Current context is: default
Usage: dk order-list [OPTIONS]

  List Orders in a Kitchen.

  Examples:

  1) Basic usage with no paging, 5 orders, 3 order runs per order.

  dk order-list

  2) Get first, second and third page, ten orders per page, two order runs
  per order.

  dk order-list --start 0  --order_count 10 --order_run_count 2

  dk order-list --start 10 --order_count 10 --order_run_count 2

  dk order-list --start 20 --order_count 10 --order_run_count 2

  3) Get first five orders per page, two order runs per order, for recipe
  recipe_name

  dk order-list --recipe recipe_name --order_count 5 --order_run_count 2

Options:
  -k, --kitchen TEXT              Filter results for kitchen only
  -s, --start INTEGER             Start offset for displaying orders
  -oc, --order_count INTEGER      Number of orders to display
  -orc, --order_run_count INTEGER
                                  Number of order runs to display, for each
                                  order
  -r, --recipe TEXT               Filter results for this recipe only
  --help                          Show this message and exit.
~/Kitchens/Dev_Sprint $ dk order-list


Current context is: default
YYYY-MM-DD HH:MM:SS - Get Order information for Kitchen Dev_Sprint:

ORDER SUMMARY (order ID: c9dc1bd2-4ef6-11e8-a766-080027aceabc)
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Variation:	Variation1
Schedule:	now
Status:		COMPLETED_ORDER

  1.  ORDER RUN	(OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S


ORDER SUMMARY (order ID: 271848fa-3d97-11e8-b513-0242ac110002)
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Variation:	Variation1
Schedule:	now
Status:		COMPLETED_ORDER

  1.  ORDER RUN	(OrderRun ID: b447a270-f58a-11e7-ac1f-1273f4bf185a)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S

  2.  ORDER RUN	(OrderRun ID: d90f4f0c-b9be-11e7-b221-12d21ed7aa80)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S


ORDER SUMMARY (order ID: c34b7438-419b-11e8-9702-0242ac110002)
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Variation:	Variation1
Schedule:	now
Status:		COMPLETED_ORDER

  1.  ORDER RUN	(OrderRun ID: 
c907d856-b5e3-11e7-af23-12d21ed7aa80)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S
~ $ dk ol -k Dev_Sprint


Current context is: default
YYYY-MM-DD HH:MM:SS - Get Order information for Kitchen Dev_Sprint:

ORDER SUMMARY (order ID: c9dc1bd2-4ef6-11e8-a766-080027aceabc)
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Variation:	Variation1
Schedule:	now
Status:		COMPLETED_ORDER

  1.  ORDER RUN	(OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S


ORDER SUMMARY (order ID: 271848fa-3d97-11e8-b513-0242ac110002)
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Variation:	Variation1
Schedule:	now
Status:		COMPLETED_ORDER

  1.  ORDER RUN	(OrderRun ID: b447a270-f58a-11e7-ac1f-1273f4bf185a)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S

  2.  ORDER RUN	(OrderRun ID: d90f4f0c-b9be-11e7-b221-12d21ed7aa80)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S


ORDER SUMMARY (order ID: c34b7438-419b-11e8-9702-0242ac110002)
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Variation:	Variation1
Schedule:	now
Status:		COMPLETED_ORDER

  1.  ORDER RUN	(OrderRun ID: 
c907d856-b5e3-11e7-af23-12d21ed7aa80)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S
~ $ dk ol -k Dev_Sprint -r Recipe1 -s 0 -oc 2


Current context is: default
YYYY-MM-DD HH:MM:SS - Get Order information for Kitchen Dev_Sprint:

ORDER SUMMARY (order ID: c9dc1bd2-4ef6-11e8-a766-080027aceabc)
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Variation:	Variation1
Schedule:	now
Status:		COMPLETED_ORDER

  1.  ORDER RUN	(OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S


ORDER SUMMARY (order ID: 271848fa-3d97-11e8-b513-0242ac110002)
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Variation:	Variation1
Schedule:	now
Status:		COMPLETED_ORDER

  1.  ORDER RUN	(OrderRun ID: b447a270-f58a-11e7-ac1f-1273f4bf185a)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S

  2.  ORDER RUN	(OrderRun ID: d90f4f0c-b9be-11e7-b221-12d21ed7aa80)
	OrderRun Status OrderRun Completed
	Start time:	YYYY-MM-DD HH:MM:SS
	End time:	YYYY-MM-DD HH:MM:SS
	Duration:	H:M:S

order-run (or)

~ $ dk order-run --help



Current context is: default
Usage: dk order-run [OPTIONS] VARIATION

  Run an Order: cook a Recipe Variation.  Run an Order for a single, specific 
  Recipe graph node using the --node option.

Options:
  -k, --kitchen TEXT  Kitchen name
  -r, --recipe TEXT   Recipe name
  -n, --node TEXT     Name of the node to run
  -p, --params TEXT   Overrides passed as parameters
  -y, --yes           Force yes
  --help              Show this message and exit.
~Kitchens/Dev_Sprint/Recipe1 $ dk order-run Variation1


Current context is: default
Are you sure you want to create an Order with:
	Kitchen: Dev_Sprint
	Recipe: Recipe1
	Variation: Variation1 ? [yes/No] yes
YYYY-MM-DD HH:MM:SS - Create an Order:
	Kitchen: Dev_Sprint
	Recipe: Recipe1
	Variation: Variation1
  
Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc
~Kitchens/Dev_Sprint/Recipe1 $ dk order-run Variation1


Current context is: default
Are you sure you want to create an Order with:
	Kitchen: Dev_Sprint
	Recipe: Recipe1
	Variation: Variation1 ? [yes/No] yes
YYYY-MM-DD HH:MM:SS - Create an Order:
	Kitchen: Dev_Sprint
	Recipe: Recipe1
	Variation: Variation1
  
Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc
The following variables will be overridden:
VARIABLE_NAME
~ $ dk or -k Dev_Sprint -r Recipe1 Variation1 -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Create an Order:
	Kitchen: Dev_Sprint
	Recipe: Recipe1
	Variation: Variation1
  
Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc
~ $ dk or -k Dev_Sprint -r Receipe1 Variation1 -n node2 -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Create an Order:
	Kitchen: Dev_Sprint
	Recipe: Recipe1
	Variation: Variation1
  	Node: node2
  
Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc
~ $ dk or -k Dev_Sprint -r Recipe1 Variation1 -p '{"email":"[email protected]","schema":"alt_schema"}' -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Create an Order:
	Kitchen: Dev_Sprint
	Recipe: Recipe1
	Variation: Variation1
  
The following variables will be overridden:
schema: alt_schema
email: [email protected]
Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc

order-stop (os)

~ $ dk order-stop --help



Current context is: default
Usage: dk order-stop [OPTIONS]

  Stop an order - Turn off the serving generation ability of an order.  Stop
  any running jobs.  Keep all state around.

Options:
  -k, --kitchens	Kitchen name
  -o, --order_id TEXT  Order ID  [required]
  -y, --yes           Force yes  
  --help               Show this message and exit.
~/Kitchens/Dev_Sprint $ dk order-stop --order_id Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc --yes


Current context is: default
Are you sure you want to stop an Order:
	Kitchen: Dev_Sprint
	Recipe: Recipe1
	Variation: Variation1 
  Order ID: Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc
  ? [yes/No] yes
  
YYYY-MM-DD HH:MM:SS - Stop Order ID:
Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc
Stopped Order
Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc
~ $ dk os -k Dev_Sprint -o Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Stop Order ID:
Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc
Stopped Order
Order ID is: c9dc1bd2-4ef6-11e8-a766-080027aceabc

orderrun-copy (orc)

~ $ dk orderrun-copy --help



Current context is: default
Usage: dk orderrun-copy [OPTIONS]

  Copy one or more OrderRuns from a Source Kitchen to a Target Kitchen.

Options:
  -ori, --order_run_id TEXT  OrderRun ID to copy [required]
  -sk, --source_kitchen TEXT  source (from) kitchen name  [required]
  -tk, --target_kitchen TEXT  target (to) kitchen name  [required]
  -y, --yes           Force yes
  --help  Show this message and exit.
~ $ dk orderrun-copy --source_kitchen Dev_Sprint --target_kitchen master --order_run_id 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80 --order_run_id b447a270-f58a-11e7-ac1f-1273f4bf185a


Current context is: default
Are you sure you want to copy OrderRuns? [yes/No]yes
YYYY-MM-DD HH:MM:SS - Copying OrderRuns:
Source Kitchen:	Dev_Sprint
Target Kitchen:	master
OrderRun IDs:
3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
b447a270-f58a-11e7-ac1f-1273f4bf185a
~ $ dk orc -sk Dev_Sprint -tk master -ori 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80 -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Copying OrderRuns:
Source Kitchen:	Dev_Sprint
Target Kitchen:	master
OrderRun IDs:
3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80

orderrun-delete (ord)

~ $ dk orderrun-delete --help
Current context is: default


Current context is: default
Usage: dk orderrun-delete [OPTIONS] ORDERRUN_ID

  Delete the OrderRun specified by the OrderRun ID argument.

Options:
  -k, --kitchen   Kitchen name
  -y, --yes       Force yes
  --help  	  Show this message and exit.
~/Kitchens/Dev_Sprint $ dk orderrun-delete 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80


Current context is: default
Are you sure you want to delete the OrderRun:
Kitchen: Dev_Sprint
OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
[yes/no]yes

YYYY-MM-DD HH:MM:SS - Deleting OrderRun: 
3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
DKCloudCommand.delete_orderrun 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80 succeeded
~/Kitchens $ dk orderrun-delete --kitchen Dev_Sprint 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80


Current context is: default
Are you sure you want to delete the OrderRun:
Kitchen: Dev_Sprint
OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
[yes/no]yes

YYYY-MM-DD HH:MM:SS - Deleting OrderRun: 
3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
DKCloudCommand.delete_orderrun 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80 succeeded
~/Kitchens/Dev_Sprint $ dk ord 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80 -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Deleting OrderRun 
3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
DKCloudCommand.delete_orderrun 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80 succeeded

orderrun-info (ori)

~ $ dk orderrun-info --help
Current context is: default

Current context is: default
Usage: dk orderrun-info [OPTIONS]

  Display information about an OrderRun in a Kitchen.

Options:
  -k, --kitchen TEXT         kitchen name
  -o, --order_id TEXT        Order ID
  -ori, --order_run_id TEXT  OrderRun ID to display
  -s, --summary              display run summary information
  -ns, --nodestatus          display node status info
  -l, --log                  display log info
  -t, --timing               display timing results
  -q, --test                 display test results
  --runstatus                display status of the run (single line)
  --disp_chronos_id          display the chronos id (single line)
  --disp_mesos_id            display the mesos id (single line)
  -at, --all_things          display all information
  --help                     Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk orderrun-info --order_run_id 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80


Current context is: default
YYYY-MM-DD HH:MM:SS - Display Order-Run details from Kitchen Dev_Sprint:

ORDER RUN SUMMARY

Order ID:	271848fa-3d97-11e8-b513-0242ac110002
Order Run ID:	3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
Status:		COMPLETED_SERVING
Kitchen:	Dev_Sprint
Recipe:		Recipe1
Variation:	Variation1
Start time:	YYYY-MM-DD HH:MM:SS
Run duration:	(H:M:S)
~ $ dk ori -k Dev_Sprint -r Recipe1 -t


Current context is: default
YYYY-MM-DD HH:MM:SS - Display Order-Run details from Kitchen Dev_Sprint:


TIMING RESULTS

  DKRecipe timing (Recipe1), status = DKNodeStatus_in_production 
   total recipe execution time|None
   Node (node1), status = DKNodeStatus_completed_production, timing is||0:00:01.032
     (node1) Notebook elapsed time is|0:00:00.005
   Node (node2), status = DKNodeStatus_ready_for_production, timing is||None
    (node2) Data Source(DKDataSource_Container) timing is||None
     (node2) Notebook elapsed time is|None
   Node (node3), status = DKNodeStatus_ready_for_production, timing is||None
    (node3) Data Source(load-segment) timing is||None
     (node3) Notebook elapsed time is|None
   Node (node4), status = DKNodeStatus_ready_for_production, timing is||None
    (node4) Data Source(DKDataSource_Container) timing is||None
     (node4) Notebook elapsed time is|None
   Node (node5), status = DKNodeStatus_in_production, timing is||None
     (node5) Notebook elapsed time is|None
~ $ dk ori -k Dev_Sprint -r Recipe1 -q


Current context is: default
YYYY-MM-DD HH:MM:SS - Display Order-Run details from Kitchen Dev_Sprint:

TEST RESULTS

Tests: Failed
	No Tests Failed

Tests: Warning
	No Tests Gave Warning Messages

Tests: Log
	No Tests Gave Log Messages

Tests: Passed
   Step (node1)
      1. test_load_data (1589 greater-than-equal-to 1589)
   Step (node2)
      1. get-test-data-count (51289 greater-than 10000)
   Step (node3)
      1. get-test-data-count (10993497 greater-than 10993495
~ $ dk ori -k Dev_Sprint -r Recipe1 --runstatus


Current context is: default
ACTIVE_SERVING
~ $ dk ori -k Dev_Sprint -r Recipe1 -ns


Current context is: default
YYYY-MM-DD HH:MM:SS - Display Order-Run details from Kitchen Dev_Sprint:

STEP STATUS

node1	DKNodeStatus_completed_production
node2	DKNodeStatus_completed_production
node3	DKNodeStatus_completed_production
node4	DKNodeStatus_completed_production
node5	DKNodeStatus_completed_production
~/Kitchens $ dk ori -k Dev_Sprint_1 -ori 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80


Current context is: default
YYYY-MM-DD HH:MM:SS - Display Order-Run details from kitchen Dev_Sprint_1

ORDER RUN SUMMARY

Order ID:       271848fa-3d97-11e8-b513-0242ac110002
Order Run ID:   3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
Status:         COMPLETED_SERVING
Kitchen:        Dev_Sprint_1
Recipe:         Recipe1
Variation:      Variation1
Start time:     YYYY-MM-DD HH:MM:SS
Run duration:	(H:M:S)

orderrun-resume (orr)

~ $ dk orderrun-resume --help


Current context is: default
Usage: dk orderrun-resume [OPTIONS] ORDERRUN_ID

  Resumes an OrderRun that was stopped manually or due to the failure 
  of an implemented test.

Options:
  -k, --kitchen	   Kitchen name
  -y, --yes          Force yes
  --help  Show this message and exit.
~/Kitchens/Dev_Sprint $ dk orderrun-resume 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80


Current context is: default
Are you sure you want to resume the OrderRun:
  Kitchen:		Feature_Sprint
  Recipe:			Recipe1
  Variation:	Variation1[yes/No]yes
  OrderRun:	  3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80

YYYY-MM-DD HH:MM:SS - Resuming OrderRun:
  Kitchen:		Feature_Sprint
  Recipe:			Recipe1
  Variation:	Variation1[yes/No]yes
  OrderRun:	  3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
~ $ dk orr -k Feature_Sprint 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80 -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Resuming OrderRun:
  Kitchen:		Feature_Sprint
  Recipe:			Recipe1
  Variation:	Variation1[yes/No]yes
  OrderRun:	  3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80

orderrun-stop (ors)

~ $ dk orderrun-stop  --help


Current context is: default
Usage: dk orderrun-stop [OPTIONS]

  Stop an OrderRun in progress.  Keeps all state around.

Options:
  -k, --kitchen 		Kitchen name
  -ori, --order_run_id TEXT  OrderRun ID  [required]
  -y, --yes           Force yes  
  --help                     Show this message and exit.
~/Kitchens/Feature_Sprint $ dk orderrun-stop --order_run_id 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80


Current context is: default
Are you sure you want to stop an OrderRun:
  Kitchen:		 Feature_Sprint
	Recipe:			 Recipe1
	Variation:	 Variation1 
  OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
  ? [yes/No]yes

YYYY-MM-DD HH:MM:SS - Stopping Order ID:
  Kitchen:		 Feature_Sprint
	Recipe:			 Recipe1
	Variation:	 Variation1 
  OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80

Stopped OrderRun
3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
~/Kitchens $ dk orderrun-stop --kitchen Feature_Sprint --order_run_id 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80


Current context is: default
Are you sure you want to stop an OrderRun:
  Kitchen:		 Feature_Sprint
	Recipe:			 Recipe1
	Variation:	 Variation1 
  OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
  ? [yes/No]yes

YYYY-MM-DD HH:MM:SS - Stopping Order ID:
  Kitchen:		 Feature_Sprint
	Recipe:			 Recipe1
	Variation:	 Variation1 
  OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80

Stopped OrderRun
3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80
~/Kitchens/Feature_Sprint $ dk ors -ori 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80 -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Stopping Order ID:
  Kitchen:		 Feature_Sprint
	Recipe:			 Recipe1
	Variation:	 Variation1 
  OrderRun ID: 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80

Stopped OrderRun
 3ae83e0a-f7cc-11e7-9d16-12d21ed7aa80

recipe-compile (rc)

~ $ dk recipe-compile --help


Current context is: default
Usage: dk recipe-compile [OPTIONS]

  Apply variables to a Recipe and get local copies of the compiled 
  files to a new /compiled-recipe directory.  If no local copy of the
  Recipe exists one will be created.

Options:
  -v, --variation TEXT  variation name  [required]
  -k, --kitchen TEXT    kitchen name
  -r, --recipe TEXT     recipe name
  --help                Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk recipe-compile --variation Variation1


Current context is: default
YYYY-MM-DD HH:MM:SS - Compiling Recipe:
Kitchen:		Dev_Sprint
Recipe: 		Recipe1
Variation:		Variation1

DKCloudCommand.get_compiled_serving succeeded, compiled recipe stored in folder 'compiled-recipe'
~ $ dk rc -k Dev_Sprint -r Recipe1 -v Variation1


Current context is: default
YYYY-MM-DD HH:MM:SS - Compiling Recipe:
Kitchen:		Dev_Sprint
Recipe: 		Recipe1
Variation:		Variation1

DKCloudCommand.get_compiled_serving succeeded, compiled recipe stored in folder 'compiled-recipe'

recipe-copy (ry)

~ $ dk recipe-copy --help


Current context is: default
Usage: dk recipe-copy [OPTIONS] SOURCE NAME

  Create a new Recipe based on the given recipe.

  Example: dk ry -k my_kitchen existing_recipe my_brand_new_recipe

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

recipe-create (re)

~ $ dk recipe-create --help


Current context is: default
Usage: dk recipe-create [OPTIONS] NAME

  Create a new Recipe.

  Available templates: qs1, qs2, qs3

Options:
  -k, --kitchen TEXT  	Kitchen name	
  -tm, --template TEXT	Recipe template
  --help              	Show this message and exit.
~/Kitchens/Dev_Sprint $ dk recipe-create Recipe2


Current context is: default
YYYY-MM-DD HH:MM:SS - Creating Recipe 'Recipe2' for Kitchen 'Dev_Sprint'
list_recipe - elapsed: 0
DKCloudCommand.recipe_create created recipe Recipe2
DKCloudCommand.get_recipe has 7 sections
  Recipe1/node1
  Recipe1
  Recipe1/resources
  Recipe1/resources/email-templates
  Recipe1/action-node
  Recipe1/do-nothing-node
  Recipe1/action-node/actions
~ $ dk re -k Dev_Sprint -tm qs1 Recipe2


Current context is: default
YYYY-MM-DD HH:MM:SS - Creating Recipe 'Recipe2' for Kitchen 'Dev_Sprint'
list_recipe - elapsed: 0
DKCloudCommand.recipe_create created recipe Recipe2

recipe-delete (rd)

~ $ dk recipe-delete --help


Current context is: default
Usage: dk recipe-delete [OPTIONS] NAME

  Deletes the local and remote copies of the given Recipe.

Options:
  -k, --kitchen TEXT  kitchen name
  -y, --yes           Force yes
  --help              Show this message and exit.
~/Kitchens/Dev_Sprint $ dk recipe-delete Recipe1


Current context is: default
This command will delete the local and remote copies of Recipe 'Recipe1' for Kitchen 'Dev_Sprint'.
Are you sure you want to delete the local and remote copies of Recipe 'Recipe1'? [yes/No]yes
YYYY-MM-DD HH:MM:SS - Deleting Recipe 'Recipe1' for Kitchen 'Dev_Sprint'
Deleting remote copy of recipe ...
Done.
Deleting local copy of recipe ...
Done.
DKCloudCommand.recipe_delete deleted recipe Recipe1
~ $ dk rd -k Dev_Sprint Recipe2 -y


Current context is: default
This command will delete the local and remote copies of Recipe 'Recipe2' for Kitchen 'Dev_Sprint'.
YYYY-MM-DD HH:MM:SS - Deleting Recipe 'Recipe1' for Kitchen 'Dev_Sprint'
Deleting remote copy of recipe ...
Done.
Deleting local copy of recipe ...
Done.
DKCloudCommand.recipe_delete deleted recipe Recipe2

recipe-get (rg)

~ $ dk recipe-get --help


Current context is: default
Usage: dk recipe-get [OPTIONS] [RECIPE]

  Get the latest remote versions of Recipe files. Changes will be auto-
  merged to local where possible. Conflicts will be written to local such
  that the impacted files contain full copies of both remote and local
  versions for the user to manually resolve. Local vs remote conflicts can
  be viewed via the file-diff command.

Options:
  -d, --delete_local  Deletes Recipe files that only exist on local.
  -o, --overwrite     Overwrites local version of Recipe files if said files
                      exist on remote.
  -y, --yes           Force through the command's subprompt.
  --help              Show this message and exit.
~/Kitchens/Dev_Sprint $ dk rg Recipe1


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the latest version of Recipe 'Recipe1' in Kitchen 'Dev_Sprint'

DKCloudCommand.get_recipe has 7 sections
  Recipe1/node1
  Recipe1
  Recipe1/resources
  Recipe1/resources/email-templates
  Recipe1/action-node
  Recipe1/do-nothing-node
  Recipe1/action-node/actions
~/Kitchens/Dev_Sprint/Recipe1 $ dk recipe-get --overwrite


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the latest version of Recipe 'Recipe1' in Kitchen 'Dev_Sprint'
Getting from remote 'variables.json'
~/Kitchens/Dev_Sprint $ dk rg -d


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the latest version of Recipe 'Recipe1' in Kitchen 'Dev_Sprint'
The following local only files will be deleted...

        .../Kitchens/Dev_Sprint/Recipe1/resources/test.txt

Are you sure you want to delete these local items? [yes/No]yes
deleting local file: .../Kitchens/Dev_Sprint/Recipe1/resources/test.txt

recipe-ingredient-list (ril)

~ $ dk recipe-ingredient-list --help


Current context is: default
Usage: dk recipe-ingredient-list [OPTIONS]

  Shows the available Ingredients for the current Recipe in a Kitchen.

Options:
  --help		Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk ril


Current context is: default
YYYY-MM-DD HH:MM:SS - Listing Ingredients:
Kitchen:	Dev_Sprint
Recipe:		Recipe1

Ingredients:
	Ingredient1: Description.
	Ingredient2: Description.
	Ingredient3: Description.
	Ingredient4: Description.

recipe-list (rl)

~ $ dk recipe-list --help


Current context is: default
Usage: dk recipe-list [OPTIONS]

  List the Recipes in a Kitchen.

Options:
  -k, --kitchen TEXT  kitchen name
  --help              Show this message and exit.
~Kitchens/Dev_Sprint $ dk recipe-list


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the list of Recipes for Kitchen 'Dev_Sprint'
list_recipe - elapsed: 0
DKCloudCommand.list_recipe returned 3 recipes
  Recipe1
  Recipe2
  Recipe3
~ $ dk rl -k Dev_Sprint


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the list of Recipes for Kitchen 'Dev_Sprint'
list_recipe - elapsed: 0
DKCloudCommand.list_recipe returned 3 recipes
  Recipe1
  Recipe2
  Recipe3

recipe-status (rs)

~ $ dk recipe-status --help


Current context is: default
Usage: dk recipe-status [OPTIONS]

  Compare local Recipe to remote Recipe for the current Recipe.

Options:
  --help  Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk rs


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the status of Recipe 'Recipe1' in Kitchen 'Dev_Sprint'
	versus directory '~/Kitchens/Dev_Sprint/Recipe-Template'
1 files are modified on local:
	graph.json

25 files are unchanged

recipe-update (ru)

~ $ dk recipe-update --help


Current context is: default
Usage: dk recipe-update [OPTIONS]

  Update all of the changed files for this Recipe
  

Options:
  -d, --delete_remote	Delete remote files to match local
  -m, --message TEXT	Change message  [required]
  --help	        Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk recipe-update --message "Change message"


Current context is: default
YYYY-MM-DD HH:MM:SS - Updating all changed files in Recipe (Recipe1) in Kitchen (Dev_Sprint) with message (Change message)
Update results:

New files:
	resources/newfile.json
Updated files:
	variables.json
Deleted files:
	None

Issues:

No issues found
~/Kitchens/Dev_Sprint/Recipe1 $ dk ru -m "Change message"


Current context is: default
YYYY-MM-DD HH:MM:SS - Updating all changed files in Recipe (Recipe1) in Kitchen (Dev_Sprint) with message (Change message)

Unable to update files due to errors in recipe:

graph.json:
	Error: Node bad_node does not exist in recipe. Check the existence of bad_node folder in recipe path. 
	Error: Node good_node declared in edge node1 -> good_node does not exist

recipe-validate (rv)

~ $ dk recipe-validate --help


Current context is: default
Usage: dk recipe-validate [OPTIONS]

  Validates local copy of a Recipe, returning a list of errors and warnings.
  If there are no local changes, will only validate remote files.

Options:
  -v, --variation		Variation name  [required]
  --help			Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk recipe-validate --variation Variation1


Current context is: default
YYYY-MM-DD HH:MM:SS - Validating recipe/variation Recipe-1.Variation1 in Kitchen DevSprint
There are no local changes. Validating recipe with remote version.
DKCloudCommand.recipe_validate succeeded
No recipe issues identified.
~/Kitchens/Dev_Sprint/Recipe1 $ dk rv -v Variation1


Current context is: default
YYYY-MM-DD HH:MM:SS - Validating recipe/variation Recipe1.Variation1 in Kitchen Dev_Sprint
Validating recipe with local changes applied
Recipe issues identified with the following files:
graph.json:
        Error: Cannot parse the file, please check.

recipe-variation-list (rvl)

~ $ dk recipe-variation-list --help


Current context is: default
Usage: dk recipe-variation-list [OPTIONS]

  Shows the available Variations for a Recipe in a Kitchen.

Options:
  -k, --kitchen TEXT    kitchen name
  -r, --recipe TEXT     recipe name
  --help  		Show this message and exit.
~/Kitchens/Dev_Sprint/Recipe1 $ dk rvl



YYYY-MM-DD HH:MM:SS - List Variations:
	Kitchen:  	Dev_Sprint
	Recipe:		Recipe1
	Variations:	Variation1
  			Variation2
  			Variation3
  			Variation4
  			Variation5

secret-delete (sd)

~ $ dk secret-delete --help
Current context is: default


Usage: dk secret-delete [OPTIONS] PATH

  Delete one secret.

Options:
  -y, --yes  Force yes
  --help     Show this message and exit.
~ $ dk secret-delete standalone-credential


Current context is: default
Are you sure you want to delete the secret? [yes/No]yes
YYYY-MM-DD HH:MM:SS - Deleting secret
secret_write - elapsed: 0
Secret deleted.
~ $ dk sd group/credential -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Deleting secret
secret_write - elapsed: 0
Secret deleted.

secret-exists (se)

~ $ dk secret-exists --help


Current context is: default
Usage: dk secret-exists [OPTIONS] PATH

  Checks if a single Secret exists in the Vault.

Options:
  --help  Show this message and exit.
~ $ dk secret-exists standalone-credential


Current context is: default
YYYY-MM-DD HH:MM:SS Checking secret
secret_exists - elapsed: 0
True
~ $ dk se group/credential


Current context is: default
YYYY-MM-DD HH:MM:SS Checking secret
secret_exists - elapsed: 0
True

secret-list (sl)

~ $ dk secret-list --help


Current context is: default
Usage: dk secret-list [OPTIONS] [PATH]

  List all Vault Secrets.  Use the recursive option to show 
  secrets grouped in Vault sub-directories.

Options:
  -rc, --recursive  Recursive
  --help            Show this message and exit.
~ $ dk secret-list


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the list of secrets
secret_list - elapsed: 0
secret-list returned 10 secrets
	dockerhub/
	github-password
	github-url
	github-username
	mongodb-password
	mongodb-url
	mongodb-username
	postgresql/
	s3_schema/
	tableau_online/
~ $ dk sl -rc


Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the list of secrets
secret_list - elapsed: 0
secret-list returned 21 secrets
	vault://dockerhub/email
	vault://dockerhub/namespace
	vault://dockerhub/password
	vault://dockerhub/username
	vault://github-password
	vault://github-url
	vault://github-username
	vault://mongodb-password
	vault://mongodb-url
	vault://mongodb-username
	vault://postgresql/database
	vault://postgresql/hostname
	vault://postgresql/password
	vault://postgresql/port
	vault://postgresql/username
	vault://s3_schema/bucket
	vault://s3_schema/s3-access-key
	vault://s3_schema/s3-secret-key
	vault://tableau_online/password
	vault://tableau_online/url
	vault://tableau_online/username

secret-write (sw)

~ $ dk secret-write --help



Current context is: default
Usage: dk secret-write [OPTIONS] ENTRY

  Write one secret to the Vault. Spaces are not allowed.

	Example:
	dk secret-write my-key=my-value

Options:
  -y, --yes		Force yes to overwrite
  --help		Show this message and exit.
~ $ dk secret-write standalone-credential=test-credential


Current context is: default
YYYY-MM-DD HH:MM:SS - Writing secret
secret_write - elapsed: 0
Secret written.
~ $ dk secret-write standalone-credential=test-credential


Current context is: default
Are you sure you want to delete the secret? [yes/No]yes
YYYY-MM-DD HH:MM:SS - Writing secret
secret_write - elapsed: 0
Secret written.
~ $ dk sw group/credential=test-credential -y


Current context is: default
YYYY-MM-DD HH:MM:SS - Writing secret
secret_write - elapsed: 0
Secret written.
~ $ dk secret-write standalone-file-as-secret=@example-file.pem



YYYY-MM-DD HH:MM:SS - Writing secret
secret_write - elapsed: 0
Secret written.

user-info (ui)

~ $ dk user-info --help


Current context is: default
Usage: dk user-info [OPTIONS]

  Get information about this user.

Options:
  --help  Show this message and exit.
~ $ dk ui


Current context is: default
Name:           John Smith
Email:          [email protected]
Role:           Data Engineer
Customer Name:  Acme, Inc.
Support Email:  [email protected]

vault-config (vc)

~ $ dk vault-config --help



Current context is: default
Usage: dk vault-config [OPTIONS]

  Configure vault. Your role must be "IT" or "ADMIN" to run global vault
  configuration.

  Examples:

          1) Global vault config
          dk vault-config --url http://dummy-vault-url:8200 --token my-vault-token

          2) Kitchen vault config with default service
          dk vault-config --kitchen my-kitchen --service default

          3) Kitchen vault config with configuration inherited from parent
          dk vault-config --kitchen my-kitchen --inherit

          4) Kitchen vault config with custom service
          dk vault-config --kitchen my-kitchen \
              --prefix my-kitchen-prefix \
              --private True \
              --service custom \
              --token my-vault-token \
              --inheritable True \
              --url http://dummy-vault-url:8200

          Note: To continue the command in next line, use
              \ (in Linux)
              or
              ^ (in Windows)

Options:
  -k, --kitchen TEXT      Kitchen name
  -h, --inherit           Configuration inherited from parent kitchen
  -s, --service TEXT      Service can be custom or default
  -u, --url TEXT          Vault url (with port)
  -t, --token TEXT        Vault token
  -r, --prefix TEXT       Vault prefix, if exist
  -p, --private TEXT      Whether vault is private or not
  -i, --inheritable TEXT  Whether vault Values are Inheritable or not
  -y, --yes               Force yes
  --help                  Show this message and exit.
~ $ dk vault-config --url [VAULT_URL] --token [VAULT_TOKEN]




~ $ dk vault-config -k Kitchen_Name -s custom -p True -i False -u [VAULT_URL] -t [VAULT_TOKEN]



Current context is: default
YYYY-MM-DD HH:MM:SS - Setting the vault info
Done.

vault-delete (vd)

~ $ dk vault-delete --help



Current context is: default
Usage: dk vault-delete [OPTIONS]

  Delete kitchen vault configuration.

  Example:

          dk vault-delete -k my-kitchen

Options:
  -k, --kitchen TEXT  Kitchen name  [required]
  -y, --yes           Force yes
  --help              Show this message and exit.
~/Kitchens/Kitchen_Name $ dk vault-delete



Current context is: default
You are deleting kitchen vault config for kitchen Kitchen_Name!. Are you sure you want to proceed? [yes/No]yes
YYYY-MM-DD HH:MM:SS - Deleting the vault configuration for kitchen Kitchen_Name
Done.
~ $ dk vd -k Kitchen_Name -y



Current context is: default
YYYY-MM-DD HH:MM:SSS - Deleting the vault configuration for kitchen Kitchen_Name
Done.

vault-info (vi)

~ $ dk vault-info --help



Current context is: default
Usage: dk vault-info [OPTIONS]

  List vault info

  Examples:

          1) Get global vault info
          dk vault-info

          2) Get kitchen specific vault info
          dk vault-info -k my-kitchen

          3) Get kitchen specific and global vault info
          dk vault-info -g -k my-kitchen

Options:
  -k, --kitchen TEXT    Kitchen name
  -g, --global-secrets  list global secrets
  --help                Show this message and exit.
~/Kitchens $ dk vault-info --global



Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the vault info

---- global config ----
 prefix                 
 private                True
 service                custom
 token                  ******
 url                    http://12.345.678.9:1234
~/Kitchens/Kitchen_Name $ dk vault-info



Current context is: default
YYYY-DD-MM HH:MM:SS - Getting the vault info

---- Kitchen_Name config ----
(Inherited from Parent Kitchen Kitchen_Name_Parent)
 prefix                 vault_path_prefix
 private                True
 service                custom
 token                  ******
 url                    http://12.345.678.9:1234
 inheritable            True
~ $ dk vi -k Kitchen_Name -g



Current context is: default
YYYY-MM-DD HH:MM:SS - Getting the vault info

---- global config ----
 prefix                 
 private                True
 service                custom
 token                  ******
 url                    http://12.345.678.9:1234

---- Kitchen_Name config ----
(Inherited from Parent Kitchen Kitchen_Name_Parent)
 prefix                 vault_path_prefix
 private                True
 service                custom
 token                  ******
 url                    http://98.765.432.1:9876
 inheritable            True

Updated 9 days ago


Usage Examples


Suggested Edits are limited on API Reference Pages

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