Epi CLI Task
This extension setup the Epi CLI used for publish website to Optimizely DXP. After installation, you will have access to the following commands:
$ epi -h
Usage: epi.exe [OPTIONS] <COMMAND>
Commands:
Name |
Description |
storage |
Storage command [aliases: blob ] |
deployment |
Deployment command [aliases: deploy ] |
project |
Project command |
db |
Database command [aliases: database ] |
log |
Log commands |
notification |
Notification commands [aliases: noti , notify ] |
cleanup |
The cleanup commnad [aliases: clean , clear ] |
help |
Print this message or the help of the given subcommand(s) |
Options:
Shortname |
Name |
Description |
-r |
--root <ROOT> |
Directory to use as root of project [default: . ] |
|
--pause |
Pause the program after execution [aliases: wait ] |
|
--pause-if-error |
Pause the program after execution if an error occurs [aliases: wait-if-error ] |
|
--proxy <PROXY> |
Proxy server to use |
|
--verbose <VERBOSE> |
Verbose output [default: false ] [possible values: true , false ] |
-h |
--help |
Print help |
-V |
--version |
Print version |
Storage commands
$ epi storage -h
Storage command
Usage: epi.exe storage <COMMAND>
Commands:
Name |
Description |
get-container |
Retrieves list of blob storage containers for specified project id and environment |
get-sas-link |
Retrieves SAS link for specified project id, environment, blob storage container and retention hours |
help |
Print this message or the help of the given subcommand(s) |
Options:
Shortname |
Name |
Description |
-h |
--help |
Print help |
Deployment commands
$ epi deployment -h
Deployment command
Usage: epi.exe deployment <COMMAND>
Commands:
Name |
Description |
get |
Retrieves deployments that have been triggered via the deployment api for the specified project id |
complete |
This function will complete the specified code deployment |
start |
Starts a code deployment for the specified project |
reset |
Resets or completes resetting the specified deployment |
add-package |
Will upload the specified file to the code package container by using a SAS link |
get-package-location |
Retrieves the location where deployment packages can be uploaded |
help |
Print this message or the help of the given subcommand(s) |
Options:
Shortname |
Name |
Description |
-h |
--help |
Print help |
Project commands
$ epi project -h
Project command
Usage: epi.exe project <COMMAND>
Commands:
Command |
Description |
list |
List projects |
get |
Get project details |
add |
Add a DXP project [aliases: connect ] |
remove |
Remove project |
help |
Print this message or the help of the given subcommand(s) |
Options:
Shortname |
Name |
Description |
-h |
--help |
Print help |
Database commands
$ epi db -h
Database command
Usage: epi.exe db <COMMAND>
Commands:
Name |
Description |
export |
Starts a database export for the specified project, environment and database combination |
get-export |
Retrieves information for the specified database export |
help |
Print this message or the help of the given subcommand(s) |
Options:
Shortname |
Name |
Description |
-h |
--help |
Print help |
Log commands
$ epi log -h
Log commands
Usage: epi.exe log <COMMAND>
Commands:
Name |
Description |
export |
Get logs for the specified project [aliases: get ] |
get-edge-logs-location |
Retrieves the location of the edge logs [aliases: get-edge-logs ] |
convert |
Convert log file from JSON format to text format |
clear-empty-lines |
Clear empty lines [aliases: trim ] |
help |
Print this message or the help of the given subcommand(s) |
Options:
Shortname |
Name |
Description |
-h |
--help |
Print help |
| |