LivePerson Functions is a Function as a Service (FaaS) platform which enables brands to develop custom behaviors within LivePerson’s conversational platform, to better tailor the system to their specific needs. By offering these capabilities, Functions enables developers to write a simple function, deploy it to LivePerson's infrastructure and make it available to their LivePerson account in minutes. This allows you to create custom logic inside our conversational platform.
The LivePerson Functions Command Line Interface (CLI) is an open-source command-line tool provided by LivePerson that enables developers to create, edit and process their functions on their local development machines, in their favorite IDE of their choice. That way it’s very easy to keep the source code under version control in any Source Control Management (SCM).
The CLI offers nearly all functionality from the platform (e.g. deploy, undeploy and invoke).
Besides that it offers many commands to support developers during the development of a function (e.g. pull, push and debug).
For more information about LivePerson Functions see developers.liveperson.com
Before you start using lpf, you have to make it available on your computer. Even if it's already installed, it's probably a good idea to update to the latest version. You can install it as a npm package.
> npm install -g liveperson-functions-cli
Please make sure you have all user rights on your computer or run the commands with sudo or the cmd as admin, otherwise some operations will fail due to missing rights
| Command | Description |
|---|---|
| Init | Initialize the project with the necessary files. If the project is already initialized it will add a new function. |
| Login | Performs the login with LiveEngage Credentials. |
| Logout | Performs the logout. |
| Pull | Pulls a function from the LivePerson functions platform. |
| Push | Pushes a function to the LivePerson functions platform. |
| Deploy | Deploys a function on the LivePerson functions platform. If the passed function is already deployed, it will be redeployed. |
| Undeploy | Undeploys a function on the LivePerson functions platform. |
| Invoke | Invokes a function (remote or local). |
| Debug | Starts a debug port in the range of 30500 - 31000 for a passed function. |
| Get | Get information about the passed domain. Possible domains are deployments, functions and account. |
| Help | Shows help for the cli and the supported commands. |
| Autocomplete | Displays autocomplete instructions (only supports zsh and bash). |
| Version | Shows the current installed version. |
Initialize the project with the necessary files. If the project is already initialized it will add a new function with the passed function name.
The folder name has to be same as the function name (saved in the config.json).
In the config.json of a function you can change the description, event, related input and environment variables of the function.
For the event field please use lpf get events to get the related event and paste the eventId as event.
Following files will be created:
- README: Contains information about the usage of the CLI
- .gitignore: Specifies intentionally untracked files to ignore (Link)
- .vscode: VS code settings and tasks for the local debugger (do not change these files!)
- bin: Local toolbelt, rewire requirements and debugger (do not change these files!)
- functions: Contains the different functions folder
- settings: Contains the secrets and whitelisting.
- functions folder:
- index.js: Contains the function
- config.json: Contains the function name and event and the related input and environment variables.
Folder structure
README.md
.gitignore
.vscode/
├── launch.json
└── task.json
bin/
├── lp-faas-toolbelt/
├── //Toolbelt functions
└── package.json
├── rewire.js
└── faas-debugger.js
functions/
settings.json
exampleFunction/
├── index.js
└── config.json
customFunction/
├── index.js
└── config.json
Usage
> lpf init [parameter]
Options
| Parameter | Description |
|---|---|
| function name | Adds a function with the passed name (multiple possible) |
| Flag | Description |
|---|---|
| -h --help | Show help for the init command |
Example
> lpf init <function name>
> lpf init <function name> <function name>
Performs the login with LiveEngage Credentials.
After a successful login, it is valid for 8 hours. After this period of time a new login has to be performed. It is also possible to have multiple logins saved, but only one at a time is active.
The command will create a temp file with the credentials in the node temp dir (see doc). The file is encrypted with aes256.
To switch between accounts just run the login command again and select your desired account. If the login is not valid anymore for this account you have to pass again the credentials.
If you want to add a new account just run the login command and select other.
Usage
> lpf login [--flag]
Options
| Flag | Description |
|---|---|
| -h --help | Show help for the login command |
| -a --accountId | AccountId |
| -u --username | Username |
| -p --password | Password |
Example
> lpf login
> lpf login --accountId 123456789 --username user@liveperson.com --password p4ssw0rd
> lpf login -a 123456789 -u user@liveperson.com -p p4ssw0rd
Currently the CLI login is restricted to the user login. To use the login with an SSO enabled account you have to fetch the token and userId from the FaaS UI.
It is advisable to create a separate account for the CLI, because with each new login on a different page the token expires in the CLI (only one login per account is possible).
To get the token and the userId do following steps:
- Open the FaaS UI and login.
- Open the developer tools of your browser.
- Go to the tab 'Application'.
- Open the session storage with the key 'houston.'.
- Copy token and userId.
- Token: 'glob'
- UserId: 'config.userId'
- Run the login command as follows:
lpf login --token <bearer> --accountId <accountId> --userId <userId>
Note: If you get a message that the token is not valid anymore, you have to perform step 1 - 6 again.
Performs the logout
After a successful logout the token for the selected account will be set to null. You can pass an accountId as flag, so no selection will be triggered.
Futhermore it's possible to provide a delete flag, then the account will be deleted from the temp file.
Usage
> lpf logout [--flag]
Options
| Flag | Description |
|---|---|
| -h --help | Show help for the login command |
| -a --accountId | Account which will be logged out |
| -d --delete | Deletes the account credentials from the local machine |
Example
> lpf logout
> lpf logout --accountId 123456789
> lpf logout --accountId 123456789 --delete
> lpf logout -a 123456789 -d
Pulls a function from the LivePerson functions platform (function has to exist on the platform).
You will be asked, if you want to overwrite your local state with the one from the platform.
The confirmation can be skipped by passing the --yes flag.
You can pass the --all flag, if you want to pull all functions from the platform.
Usage
> lpf pull [parameter] [--flag]
Options
| Parameter | Description |
|---|---|
| function name | Pass the function for pull (multiple possible) |
| Flag | Description |
|---|---|
| -h --help | Show help for the pull command |
| -y --yes | Agrees to the approval of the pull and prevents the confirmation dialog |
| -w --no-watch | Hide information about the pull process |
| -a --all | Pulls all functions from the platform |
Example
> lpf pull exampleFunction
> lpf pull exampleFunction --yes --no-watch
> lpf pull exampleFunction1 exampleFunction2 -y -w
Pushes a function to the LivePerson functions platform.
You will be asked, if you want to overwrite your remote state with the one from your local machine.
The confirmation can be skipped by passing the --yes flag.
If it's a new function, which is not created on the platform, the CLI will create this one.
You can pass the --all flag, if you want to push all local functions to the platform.
Usage
> lpf push [parameter] [--flag]
Options
| Parameter | Description |
|---|---|
| function name | Pass the function for push (multiple possible) |
| Flag | Description |
|---|---|
| -h --help | Show help for the push command |
| -y --yes | Agrees to the approval of the push and prevents the confirmation dialog |
| -w --no-watch | Hide information about the push process |
| -a --all | Pushes all local functions |
Example
> lpf push exampleFunction
> lpf push exampleFunction --yes --no-watch
> lpf push exampleFunction1 exampleFunction2 -y -w
Deploys a function on the LivePerson functions platform.
To deploy a function it has to exist on the LivePerson functions platform. You can use the push command in order to ensure this.
If the passed function is already deployed, it will be redeployed.
The command can be run from the root directory or functions folder, then it's necessary to pass a function name. If the user runs the command inside a functions folder, it's not necessary and the command will take the function of the current directory.
Usage
> lpf deploy [parameter] [--flag]
Options
| Parameter | Description |
|---|---|
| function name | Pass the function for deployment (multiple possible) |
| Flag | Description |
|---|---|
| -h --help | Show help for the deploy command |
| -y --yes | Agrees to the approval of the deployment and prevents the confirmation dialog |
| -w --no-watch | Hide information about the deployment process |
Example
> lpf deploy exampleFunction
> lpf deploy exampleFunction --yes --no-watch
> lpf deploy exampleFunction1 exampleFunction2 -y -w
Undeploys a function on the LivePerson functions platform.
To undeploy a function it has to exist on the LivePerson functions platform. You can use the push command in order to ensure this.
The command can be run from the root directory or functions folder, then it's necessary to pass a function name. If the user runs the command inside a functions folder, it's not necessary and the command will take the function of the current directory.
Usage
> lpf undeploy [parameter] [--flag]
Options
| Parameter | Description |
|---|---|
| function name | Pass the function for undeployment (multiple possible) |
| Flag | Description |
|---|---|
| -h --help | Show help for the deploy command |
| -y --yes | Agrees to the approval of the undeployment and prevents the confirmation dialog |
| -w --no-watch | Hide information about the undeployment process |
Example
> lpf undeploy exampleFunction
> lpf undeploy exampleFunction --yes --no-watch
> lpf undeploy exampleFunction1 exampleFunction2 -y -w
Invokes a function (remote or local).
If you pass the --local flag the function will be invoked locally. Otherwise it will be invoked on the functions platform.
For both cases it will use the input from the related function config.json.
The local invocation uses the mocked
faas-toolbeltso please have a look at Preparation for further information.
Usage
> lpf invoke [parameter] [--flag]
Options
| Parameter | Description |
|---|---|
| function name | Pass the function to invoke |
| Flag | Description |
|---|---|
| -h --help | Show help for the invoke command |
| -l --local | Invokes the function on the local machine |
Example
> lpf invoke exampleFunction
> lpf invoke exampleFunction --local
> lpf invoke exampleFunction1 -l
Starts a debug port in the range of 30500 - 31000 for a passed function.
Usage
> lpf debug [parameter] [--flag]
Options
| Parameter | Description |
|---|---|
| function name | Pass the function to debug |
| Flag | Description |
|---|---|
| -h --help | Show help for the debug command |
Example
> lpf debug exampleFunction
Get information about the passed domain. Possible domains are deployments, functions, account and events.
The following information will be displayed:
- Deployment: Name, Undeployed changes from, Last successful deployment, deployed by, deployment state
- Function: Name, Status, last changed at, last changed by, Event
- Account: Offers insights that are currently generated by the welcome page
- Events: Event name and eventId
Usage
> lpf get [parameter] [--flag]
Options
| Parameter | Description |
|---|---|
| domain | Pass a valid domain (multiple possible) |
| Flag | Description |
|---|---|
| -h --help | Show help for the get command |
Example
> lpf get account
> lpf get functions deployments
> lpf get functions deployments account
> lpf get functions deployments account events
Get logs from function.
Usage
> lpf logs [parameter] [--flag]
Options
| Parameter | Description |
|---|---|
| function | function name to fetch logs from |
| Flag | Description |
|---|---|
| -h --help | Show help for the get command |
| -s, --start=start | (required) start timestamp |
| -e, --end=end | end timestamp |
| -l, --levels=Info | Warn |
| -r, --removeHeader | Removes the header of the logs |
Example
> lpf logs exampleFunction --start=1626156400000
> lpf logs exampleFunction --start=1626156400000 --end=1626157400000
> lpf logs exampleFunction --start=1626156400000 --levels=Info Warn
Fetching logs via cronjob every 10 minutes (delayed by 1 minute to be sure no logs are missed) and write it to a file::
MacOS:
1/10 * * * * lpf logs exampleFunction --start=$(date -v0S -v-11M +%s000) --end=$(date -v0S -v-1M +%s000) >> exampleFunction.log
Get invocation metrics of a function. Optionally export them as json or CSV for additional processing. The cli will automatically aggregate invocations into buckets appropriate to the queried time span.
Usage
> lpf metrics [parameter] [--flag]
Options
| Parameter | Description |
|---|---|
| function | function name to fetch logs from |
| Flag | Description |
|---|---|
| -h --help | Show help for the get command |
| -s, --start=start | Start timestamp |
| -e, --end=end | End timestamp (Default: Current Timestamp) |
| -l, --last=Xh | Xd |
| -o, --output=json | csv |
Example
> lpf metrics exampleFunction --last=7d
> lpf metrics exampleFunction --start=1626156400000
> lpf metrics exampleFunction --end=1626156400000 --last=7d
> lpf metrics exampleFunction --start=1626156400000 --end=1626157400000',
> lpf metrics exampleFunction --last=7d --output=csv',
Fetching metrics via cronjob every 24 hours and write it to a file:
MacOS:
0 0 * * * lpf metrics exampleFunction -l=1d -o=csv >> exampleFunction.csv
If you ever need help while using lpf, there are three equivalent ways to get the comprehensive manual page (manpage) help for any of the lpf commands:
> lpf help
> lpf help <command>
> lpf <command> --help -h
For example, you can get the manpage help for the lpf login command by running
> lpf help login
Displays autocomplete instructions (only supports zsh and bash)
Usage
> lpf autocomplete [--flag]
Options
| Flag | Description |
|---|---|
| -h --help | Show help for the login command |
| -r --refresh | Refresh cache (ignores displaying instructions) |
Example
> lpf autocomplete
> lpf autocomplete bash
> lpf autocomplete zsh
> lpf autocomplete --refresh-cache
The version command shows the current installed version of the CLI. If a newer version is available the user will see an update information which shows his current version, the new version and a information about how to update to the new version.
The update notification will appear one time and then it's muted for two days.
Example
> lpf version
> lpf -v
> lpf --version
The CLI provides a way to debug and develop functions locally.
For the best developer experience it's recommended to use Visual Studio Code (VSC) or IntelliJ, because a configuration for the integrated debugger is provided by the CLI.
During the debugging process all console outputs will be printed to your terminal. At the end a history with all printed console outputs will be displayed.
We include a number of snippets (vscode) and Live-Templates (IntelliJ IDEA) for you to ease development. Your vscode should automatically detect faas-snippets.code-snippets in the .vscode folder. Meanwhile you will have to manually import the settings_live_templates.zip from the .idea folder to use the same functionality inside IntelliJ IDEA.
Once setup you can use the following snippets/Live-Templates:
- HTTP Snippet
- Read/Update Secret Snippets
- Create/Read/Update/Delete Context Session Store Snippet
- Conversation Util Snippet
- GDPR Util Snippet
- SDE Util Snippet
- Salesforce Snippet
It's necessary to run the lpf init command to initialize the project structure and to install all required packages for the local faas-toolbelt.
To get started with the local development and debugging some preparation is needed:
- Local secrets and whitelisting can be stored in the settings.json
- Local environment variables and input can be stored in the config.json in the functions folder
- The Debugger will use a mocked
faas-toolbelt - To have access to the LivePerson services it's necessary to be logged in or set an environment variable called
BRAND_IDwith youraccountId- Example with BRAND_ID and debug command:
BRAND_ID=123456789 lpf debug TestFunction
- Example with BRAND_ID and debug command:
- Set a breakpoint in your desired function.
- Run the debugger (two options available)
lpf debug <function name>- Open command palette ->
Tasks: Run Task->Debug Function
- Run
Attach FaaS Debuggerfrom thelaunch.json. - The debugger will start and pause at the auto-generated code.
- Use IntelliJ debugger to navigate through your code.
- Set a breakpoint in your desired function.
- Run the debugger (two options available)
- Use the built-in bar at the right top corner or
- Click on
Run->Run...
- Select
Start FaaS Debuggerand run the command. - Select
Attach FaaS Debuggerand run the command. - The debugger will start and pause at the auto-generated code.
- Use IntelliJ debugger to navigate through your code.
- Set a breakpoint in your desired function.
- Run the debugger (two options available)
- Run
lpf debug <function name>or - Run
node ../bin/debug.js <function name>
- Run
- A debug port will start on the port 1337
- Attach your favorite IDE or debugger to this port
- Use the debugger to navigate through your code.
If the envar HTTPS_PROXY or https_proxy is set the lpf command will use the respective URLs to forward all calls.