Launch Catalyst Functions Shell and Start Tunneling

Launch Catalyst function shell using the following CLI command with the –tunnel option and specify the port number in which you generated the Tunneling URL.

copy
$
catalyst functions:shell --tunnel tunnel-port-number

This command will start tunneling your functions.

catalyst_tunneling_enter_cli_command

If you trigger the function, all the calls made will be routed locally, and you will be able to view their execution logs in the Catalyst CLI. catalyst_tunneling_viewing_exec_logs_cli

If you attempt to view the Execution History of the tunneled function present in the component’s section, it will be clearly indicated that the function has been tunneled. catalyst_tunneling_view_logs_hihglight

If you further click the view-logs icon, you will be able to view details such as when and by whom the tunneling was enabled, and disabled. catalyst_tunneling_view_logs_log_section

Note: The logs will only be visible in the Catalyst CLI because the non-HTTPS or Integration function is being executed in the local machine, and not on the Catalyst cloud.

The same information can be found in the Audit Logs.

catalyst_tunneling_audit_logs

Now, execute the following CLI command to tunnel and debug your functions:

copy
$
catalyst functions:shell --tunnel tunnel-port-number --debug port-number

catalyst_tunneling_cli_command_debug

Note: Ensure you provide different port numbers for tunneling and debugging.

If you tunnel your function and choose to debug, you have to implement additional IDE configurations. You can find the steps to configure your IDE’s debugger for debugging tunneled functions from this section.

Last Updated 2024-07-23 17:40:25 +0530 +0530

ON THIS PAGE