Try   HackMD

Commands Scatch Pad

Storage

migrate credentials and/or claim storage, we decide based on schema.json

porter storage migrate

copy the named storage account contents (if not specified the source is the active store) to destination

porter storage copy [NAME] --destination NAME

print the name of the active storage account, the type (e.g. the plugin type) and perhaps stats on its contents

porter storage show

Config

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

porter config show

initialize a new config file with such comments, so many comments

porter config create

Credentials

resolve a credential set just like you would before injecting into a bundle

porter credentials resolve NAME

Parameters

resolve a parameter set just like you would before injecting into a bundle

porter parameters resolve NAME

Secrets

resolve a single key against a secret store, lets you figure out what's in your secret store

porter secrets resolve KEY

Home

create a PORTER_HOME, download + install porter, porter_runtime and necessary mixins, replaces install script

porter home install [--version VERSION]

Useful for running tests in an isolated PORTER_HOME in /tmp, copies the porter binaries and mixins to create a clean home

porter home copy DESTINATION [--include-storage] [--include-config]

This isn't probably the final form. But people would like to see porter ship itself somehow, either as a zip or docker image.

porter home archive FILENAME [--include-storage] [--include-config]