[trafficcontrol-trafficops-types] 01/02: Fix request-context servers not allowed to specify tcpPort, tcpPort not allowed to be null in server details

[oc...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ocket8888 pushed a commit to branch 3.x
in repository https://gitbox.apache.org/repos/asf/trafficcontrol-trafficops-types.git

commit d68ab43a52748b789bec198153cf0f6845ea058a
Author: ocket8888 <oc...@apache.org>
AuthorDate: Mon Jan 30 19:05:30 2023 -0700

    Fix request-context servers not allowed to specify tcpPort, tcpPort not allowed to be null in server details
    
    (cherry picked from commit aed9cf57b7c757c02bc49eeb2090aa6fd2b80914)
---
 src/server.ts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/server.ts b/src/server.ts
index 30b94c9..4f1eb0f 100644
--- a/src/server.ts
+++ b/src/server.ts
@@ -345,6 +345,8 @@ export interface RequestServer {
 	routerPortName?: string | null;
 	/** An integral, unique, identifier for the Server's Status. */
 	statusId: number;
+	/** A port on which the Server listens for TCP connections. */
+	tcpPort?: number | null;
 	/** An integral, unique identifier for the Type of this Server. */
 	typeId: number;
 }
@@ -516,7 +518,7 @@ export interface ServerDetails  {
 	routerHostName: string;
 	routerPortName: string;
 	status: string;
-	tcpPort: number;
+	tcpPort: number | null;
 	type: string;
 	xmppId: string;
 	xmppPasswd: string;