$ sk app ls [--numbers] [--details]
$ sk app add <repo>|.
$ sk app rm <id>|--repo <repo>|--index <index>|.
$ sk app use <id>|--repo <repo>|--index <index>|.
$ sk app info [<id>|--repo <repo>|--index <index>|.] [--get...|--set...] ## configure app settings
$ sk app envs [<id>|--repo <repo>|--index <index>|.]
$ sk env ls [--numbers] [--details]
$ sk env add <name> <branch>|.
$ sk env rm <name>
$ sk env use <name>
$ sk env info [<name>|.] [--get...|--set...]
$ sk env domain <name>
$ sk deploy ls [--numbers] [--details]
$ sk deploy pubish [<id>|<index>] # with notthing use latest
$ sk deploy preview [<id>|<index>]
$ sk deploy details [<id>|<index>]
$ sk deploy rm [<id>|<index>]
$ sk deploy [<env_name> [<branch>]]
$ sk logs
# need help of which operation write
$ sk remote-config ls [--numbers] [--details]
$ sk remote-config add <name> [--description <description>] [--experiment-id <experiment-id>]
$ sk remote-config rm <name>|<index>|<id>
$ sk remote-config info <name>|<index>|<id> [--set|--get]
$ sk remote-config value ls
$ sk remote-config value add <name>|<index>|<id> <value> [--percentile <percentile>] [--segment <segment>] [--version <version>]
$ sk remote-config value rm <name>|<index>|<id>
$ sk remote-config value info <name>|<index>|<id> [--set|--get]
remote config aliases:
- rc
- param
sk monitor
$ sk snippet ls
$ sk snippet add <name> [--content <string>|--content-file <path>] [--preappend|--append(default)] [--body|--head(default)] [--enabled]
$ sk snippet rm <name>|<index>|<id>
$ sk snippet info <name>|<index>|<id> [--get|--set]
Option 2 is very cool. Great Job 🙏
I have a question regarding the
use
parameter. What doessk app use
andsk env use
do?Also, even though in the backend it is called
remote-config
, I like thesk param
alias as well. Perhaps we can create an alias forparam
andrc
(remote config).