This topic provides instructions about how to iterate on your function using the VMware Tanzu Developer Tools extension for Visual Studio Code. This extension enables live updates of your application while running on the cluster, and allows you to debug your application directly on the cluster.
The Tanzu Developer Tools extension currently only supports Java Functions.
Before you can iterate on your function, you must have:
Before iterating on your application, you must configure the Tanzu Developer Tools extension as follows:
Open your function as a project within your VSCode IDE.
To ensure your extension assists you with iterating on the correct project, configure its settings as follows:
In Visual Studio Code, navigate to Preferences > Settings > Extensions > Tanzu.
In the Local Path field, provide the path to the directory containing your function project. The current directory is the default.
In the Source Image field, provide the destination image repository to publish an image containing your workload source code. For example,
You are now ready to iterate on your application.
Deploy your function application to view it updating live on the cluster. This demonstrates how code changes will behave on a production cluster early in the development process.
To live update your application:
Open the Command Palette by pressing ⇧⌘P.
From the Command Palette, type in and select Tanzu: Live Update Start. You can view output from Tanzu Application Platform and from Tilt indicating that the container is being built and deployed.
Live Update starting… in the status bar at the bottom right.
Live update can take 1 to 3 minutes while the workload deploys and the Knative service becomes available.
Depending on the type of cluster you use, you might see an error message similar to the following:
ERROR: Stop! cluster-name might be production. If you're sure you want to deploy there, add allow_k8s_contexts('cluster-name') to your Tiltfile. Otherwise, switch k8scontexts and restart Tilt.
If you see this error, add the line
allow_k8s_contexts('CLUSTER-NAME') to your Tiltfile, where
CLUSTER-NAME is the name of your cluster.
When the Live Update status in the status bar is visible and says
Live Update Started, navigate to
http://localhost:8080 in your browser and view your running application.
Enter the IDE and make a change to the source code.
The container is updated when the logs stop streaming. Navigate to your browser and refresh the page.
View the changes to your workload running on the cluster.
When using Live Update, hot reload of your function on your cluster might not display changes made to your function. To manually push changes to the cluster, run the
If necessary, continue making changes to the source code.
When you have finished making changes, stop and deactivate the Live Update. To do so, open the command palette by pressing ⇧⌘P, type
Tanzu, and select Tanzu: Live Update Stop.
Debug your cluster either on the application or in your local environment.
To debug your cluster:
Set a breakpoint in your code.
Right-click the file
workload.yaml within the
config directory, and select Tanzu: Java Debug Start.
In a few moments, the workload is redeployed with debugging enabled. You will see the Deploy and Connect task complete and the debug menu actions available to you, indicating that the debugger has attached.
http://localhost:8080 in your browser. This hits the breakpoint within VSCode. Play to the end of the debug session using VSCode debugging controls.