migrate credentials and/or claim storage, we decide based on schema.json
copy the named storage account contents (if not specified the source is the active store) to destination
print the name of the active storage account, the type (e.g. the plugin type) and perhaps stats on its contents
View https://github.com/deislabs/porter/issues/1077
dump all active configuration from config file and env vars and flags. Print the active plugins, list defined stores
initialize a new config file with such comments, so many comments
resolve a credential set just like you would before injecting into a bundle
resolve a parameter set just like you would before injecting into a bundle
resolve a single key against a secret store, lets you figure out what's in your secret store
create a PORTER_HOME, download + install porter, porter_runtime and necessary mixins, replaces install script
Useful for running tests in an isolated PORTER_HOME in /tmp, copies the porter binaries and mixins to create a clean home
This isn't probably the final form. But people would like to see porter ship itself somehow, either as a zip or docker image.