Readonly configOptional options: HttpHandlerOptionsOptional data: CreateCoreCommandOutputOptional data: CreateCoreCommandOutputOptional options: HttpHandlerOptionsOptional data: DeleteCoreCommandOutputOptional data: DeleteCoreCommandOutputOptional options: HttpHandlerOptionsOptional data: DescribeCoreCommandOutputOptional data: DescribeCoreCommandOutputOptional options: HttpHandlerOptionsOptional data: DescribeEventStoreCommandOutputOptional data: DescribeEventStoreCommandOutputDestroy underlying resources, like sockets. It's usually not necessary to do this. However in Node.js, it's best to explicitly shut down the client's agent when it is no longer needed. Otherwise, sockets might stay open for quite a long time before the server terminates them.
Optional options: HttpHandlerOptionsOptional data: DisableEventStoreCommandOutputOptional data: DisableEventStoreCommandOutputOptional options: HttpHandlerOptionsOptional data: EnableEventStoreCommandOutputOptional data: EnableEventStoreCommandOutputOptional options: HttpHandlerOptionsOptional data: UpdateCoreCommandOutputOptional data: UpdateCoreCommandOutputOptional options: HttpHandlerOptionsOptional data: UpdateEventStoreCommandOutputOptional data: UpdateEventStoreCommandOutput
The resolved configuration of CoresClient class. This is resolved and normalized from the constructor configuration interface.