cluster-create
should pull existing config if directory doesn't exist
#136
Labels
bug
Something isn't working
Capture Configurability
Work to make capture configurable and handle changes in configuration
Description
If the user calls
cluster-create
on an existing cluster but has deleted their local config directory or otherwise doesn't have it in the local directory tree, the code will create the config directory with default configuration rather than what is currently deployed.Blocked By
Acceptance Criteria
cluster-create
should pull the currently deployed configuration and unpack it locally if called on an existing cluster and the user doesn't have a config directory for the cluster alreadyThe text was updated successfully, but these errors were encountered: