Java

Cloud Code automatically adds an environment variable,JAVA_TOOL_OPTIONS, with the appropriate JDWP configuration toenable debugging. IfJAVA_TOOL_OPTIONS is already present,Cloud Code uses existing settings specified inJAVA_TOOL_OPTIONS.

Node.js

Depending on the structure of your application and its image buildconfiguration, you might have to help the debugger map your local sourcesto the remote sources in the container. This enables the Node debuggerto correctly process your breakpoints.

You can configure this in one of the following ways:

• Manual configuration

  Select theDevelop on Kubernetes Run Configuration from the dropdownand then clickEdit Configurations. On theDebug tab, configure thesource mapping from your local application source to the sourcelocation in the remote container.

  

  Configuration options:

  • File/directory - the local file or directory of your application running on Kubernetes.
  • Remote path - the path to the file or directory running in the container on Kubernetes.

• Automatic configuration

  You can choose to defer this mapping to Cloud Code. When youstart your debug session, Cloud Code attempts to inferthis mapping automatically. The inferred mapping is presented to you in adialog; one dialog for each artifact you are debugging.

  

  Configuration options:

  • Local path - the local path to the root of the artifact you are debugging.
  • Remote path - the path to the file or directory running in the container on Kubernetes. You can choose to override this with your own value. If you clickCancel, no mapping is applied.
  Note: Automatic mapping is a best effort guess based on heuristics.

Go

To configure your application for debugging, your app must be aGo Module-based applicationand be identified as being Go-based by setting one of thestandard Go runtime environment variablesin the container, such asGODEBUG,GOGC,GOMAXPROCS, orGOTRACEBACK.GOTRACEBACK=single is the default setting for GoandGOTRACEBACK=all is a generally useful configuration.

Optionally (but recommended), your app should be built with the-gcflags='all=-N -l' options to disable optimizations. SkaffoldProfiles are a usefuloption for this purpose and can be set with theDeployment Profilefield in your Run configuration on theBuild/Deploy tab.

Python

To configure your application for debugging, ensure you meet the followingprerequisites:

• IDE, edition, and plugin are compatible

  For compatible IDEs, editions, and plugins, seeSupported IDEs.

• Skaffold version is 1.25.0 or greater

  You can allow Cloud Code tomanage your dependencies, or point to a local Skaffold installation. SeePreferences > Tools > Cloud Code > Dependencies.

• Python interpreter is configured

  Without a Python interpreter configured in your project, debugging won't work, as there is no way to runpydevd, the underlying Python debugger.

  IDE	How to configure
  IntelliJ IDEA	Python debugging with Cloud Code requires a Python SDK to be configured for your project. Go toFile > Project Structure and add a Python SDK in theProject tab. If none exists, add one under theSDK tab.
  PyCharm	Go toFile > Settings > Project > Python Interpreter or for Mac OS X,PyCharm > Preferences > Project > Python Interpreter, and add a Python interpreter.