Developing with Terra UI

When developing a new feature, it may be useful to point a local Terra UI at a local WDS.

WDS

Activate the local and local-cors profiles. local-cors will allow cross-origin requests from the Terra UI server running on a different port. Note that data-plane is also required for WDS.

export SPRING_PROFILES_ACTIVE=local,local-cors,data-plane

Set WORKSPACE_ID to the ID of a workspace in your workspaces list. Terra UI will use the workspace ID as the collection ID for WDS, so it must match an existing workspace.

export WORKSPACE_ID=aaaabbbb-cccc-dddd-0000-111122223333

Start WDS

Terra UI

Set the TERRA_UI_USE_LOCAL_WDS_FOR_WORKSPACE environment variable to have Terra UI automatically mock the Leo list apps response for the given workspace and replace the WDS proxy URL with the URL for the local WDS.

export TERRA_UI_USE_LOCAL_WDS_FOR_WORKSPACE=$WORKSPACE_ID

Start Terra UI

Terra UI will make a request to WDS to create an instance for the workspace if one does not already exist. To do this, you must be logged in in Terra UI. If you are not, you'll see an error in the console. Log in and refresh the page to set up the mock response.

Navigate to the Data tab of the configured workspace.