Development & Commands Overview
Solution CLI development flow
The usual develoment flow consists of several steps performed by diffrent Solution CLI commands
Solution CLI commands
The available command that are commonly used in the Solution CLI are the following:
Command | Description |
fss clone | Cloning a solution that was modeled in the Solution Designer of the current setup stage to the local file system. It requires two parameters: the solution which consists of the group key and he solution acronym, and the git provider alias. |
fss compile | To compile project files. |
fss help | Displays documentation |
fss install | Install/update NPM dependencies |
fss lint | To check project files for linting errors. |
fss login-envoy | Used to login to Solution Envoy environment for debug / test support. It will ask for the Solution Envoy credentials. |
fss login | It will ask for the same credentials as the Solution Designer, the login is usually valid for a longer period, as defined by your company policies. |
fss prepare-debug | Used to prepare debug session against the configured Solution Envoy environment. It will ask for the Solution Envoy credentials. |
fss pull | Pull in the latest changes of the current branch from the GIT Repository you are on. |
fss push | Add, commit and push changes to the GIT Repository |
fss setup-envoy | Setup the Solution CLI to work with a Solution Envoy Environment Installation |
fss setup | It is used to setup the Solution CLI to work with a Solution Designer Installation, it takes all configuration as a base64 encoded string. |
fss test | Run tests within this solution |
fss upgrade-framework |
Automatically migrates implementation code from an older framework version to a newone. |
fss upgrade-cli | Upgrade the Solution CLI to the latest version |
fss version | Displays the current version of Solution CLI. |
Attention: By using
--help
after a command you will get
detailed information on the expected syntax.