Recorders added to newly added virtual services when created through API v3

Products

• Service Virtualization

Issue/Introduction

We are currently leveraging creation of virtual services through API v3.

The services are created with custom port number but for each service, a recorder is attached. Our efforts have been unsuccessful for checking how does the recorder get attached. Below is an example of the config we are using while using the v3 API: 

As seen in the image above, we are not using any recording endpoint inside the config file but still a recorder with same port is getting added. Please instruct me on how to disable recordings when deploying new services.

Environment

All supported DevTest releases.

Cause

N/A

Resolution

The recorder getting attached is by default when the virtual service is deployed. 

But you can remove entries in the vsBuilderSessions and vseRecording folders.