Tool Support

If a bug in the BaaS developer tool appears or if there is an environment issue, there are commands in the extension that may help identify the issue.

Capture Support Information

If you experience a bug in the extension or if Visual Studio Code crashes, there is a way to capture the relevant information in an archive file that should be attached to the issue report. Ensure that the client log level is set to trace in settings and try to re-create the bug. Press F1 select 'BaaS: Open Settings'.

To capture the relevant information, run the support zip command and answer the questions. If Visual Studio Code crashed, select the option to include relevant VS Code log files. Press F1 select 'BaaS: Create Support Zip File'.

In some cases, the payload and response to a service call can be of interest for investigating an issue. The latest payload and response are stored but never included in the support archive. The files can be accessed by running a command that opens the folder in Explorer/Finder. Press F1 select 'BaaS: Open Latest Zip File Location'.

Environment Issue

To verify the configuration and that the API is reachable, run the ping command. The command requires no authentication. Press F1 select 'BaaS: Ping API to check connectivity'.

To see information what API is the current target run the what command. Press F1 select 'BaaS: What API is the target'.

To see when the current access token expires. run the status command. Press F1 select 'BaaS: Login Status for API'.

To access BaaS related files in the Extension global storage, open the GSL command. Press F1 select 'BaaS: Open Global Storage Location'.

To put the current portal URL into the Clipboard, run the copy command. Press F1 select 'BaaS: Copy Current Portal URL to Clipboard',

To copy all portal URLs added into the Extension, run the copy command. Press F1 select 'BaaS: Copy Portal URLs to Clipboard',

Development Environment Issue

The health check command examines the BaaS related extensions and software installations. Press F1 select 'BaaS: Health Check'.

Documentation Issue

The documentation is downloaded when needed and stored in a versioned structure. Download of documentation requires authentication. The documentation is stored in the temporary storage of the file system and may be cleaned up. To examine the storage folder in Explorer/Finder, run the open DSL command. Press F1 select 'BaaS: Open Documentation Storage Location'.

To clear all documentation downloaded and stored in the Extension, run the clear command. Press F1 select 'BaaS: Clear Documentation Storage Location'.

BaaS Extension Log File

The extension log file contains information. A new log file is created each day with the date as part of the filename. A sequence of ###### characters in the log file indicates a value that has been redacted for security reasons.

To open the log file, run the view command. Press F1 select 'BaaS: View Log'.

To access older log files or remove old ones. open the folder in Explorer/Finder with the open LFL command. Press F1 select 'BaaS: Open Log File Location'.