• lpf init // inti project
• lpf login // login to site
• lpf get functions // get list of functions
• lpf pull [faas function name] // pull function in functions folder, secrets in settings.json
• NOTE: use LP faas UI to create secret so lpf can download in correct format, this can be used for local dev
• lpf invoke [function name] -l // invoke local instance with -l
• lpf push [function name] // push to account
• lpf deploy [fun]tion name // deploy to account

use lpf init

They are in .vscode/faas-snippets.code-snippets

in a js file, F1, search snippet or code snippet

or

lpf login -a 90412079 -u [email protected] -p pwd

you need to do this to install snippets

• terminal in faas folder, 1 level above functions[function name] folder
• do lpf invoke [function name] -l (-l for local)

• including secrets
• do not include sensitive data init
• add sensitive data in settings.json.local for local dev

Preparation for Debugging 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_ID with your accountId Example with BRAND_ID and debug command: BRAND_ID=123456789 lpf debug TestFunction Debugging with VSC Set a breakpoint in your desired function. Run the debugger (two options available) lpf debug Open command palette -> Tasks: Run Task -> Debug Function Run Attach FaaS Debugger from the launch.json. The debugger will start and pause at the auto-generated code. Use IntelliJ debugger to navigate through your code.

• you can set config.json and invoke the deployed version in the cloud with local config.json
• use console.info("debug message"); it will be part of the result payload

{
    "result": "Hello Worldundefined",
    "logs": [
        {
            "level": "Info",
            "message": "debug message",
            "extras": [],
            "timestamp": 1664568751806
        }
    ]
}