fixing lint errors

mohamadaldawamnah · mohamadaldawamnah · commit 5b7b8006f204 · 2025-07-18T11:27:09.000+01:00
diff --git a/pkg/apis/configuration/v1/types.go b/pkg/apis/configuration/v1/types.go
@@ -116,7 +116,7 @@ type PolicyReference struct {
 
 // Upstream defines an upstream.
 type Upstream struct {
-	//The name of the upstream. Must be a valid DNS label as defined in RFC 1035. For example, hello and upstream-123 are valid. The name must be unique among all upstreams of the resource.
+	// The name of the upstream. Must be a valid DNS label as defined in RFC 1035. For example, hello and upstream-123 are valid. The name must be unique among all upstreams of the resource.
 	Name string `json:"name"`
 	// The name of a service. The service must belong to the same namespace as the resource. If the service doesn’t exist, NGINX will assume the service has zero endpoints and return a 502 response for requests for this upstream. For NGINX Plus only, services of type ExternalName are also supported (check the prerequisites ).
 	Service string `json:"service"`
@@ -164,7 +164,7 @@ type Upstream struct {
 	Queue *UpstreamQueue `json:"queue"`
 	// The SessionCookie field configures session persistence which allows requests from the same client to be passed to the same upstream server. The information about the designated upstream server is passed in a session cookie generated by NGINX Plus.
 	SessionCookie *SessionCookie `json:"sessionCookie"`
-	//Enables using the Cluster IP and port of the service instead of the default behavior of using the IP and port of the pods. When this field is enabled, the fields that configure NGINX behavior related to multiple upstream servers (like lb-method and next-upstream) will have no effect, as NGINX Ingress Controller will configure NGINX with only one upstream server that will match the service Cluster IP.
+	// Enables using the Cluster IP and port of the service instead of the default behavior of using the IP and port of the pods. When this field is enabled, the fields that configure NGINX behavior related to multiple upstream servers (like lb-method and next-upstream) will have no effect, as NGINX Ingress Controller will configure NGINX with only one upstream server that will match the service Cluster IP.
 	UseClusterIP bool `json:"use-cluster-ip"`
 	// Allows proxying requests with NTLM Authentication. See the ntlm directive. In order for NTLM authentication to work, it is necessary to enable keepalive connections to upstream servers using the keepalive field. Note: this feature is supported only in NGINX Plus.
 	NTLM bool `json:"ntlm"`
@@ -179,9 +179,9 @@ type Upstream struct {
 // UpstreamBuffers defines Buffer Configuration for an Upstream.
 type UpstreamBuffers struct {
 	// Configures the number of buffers. The default is set in the proxy-buffers ConfigMap key.
-	Number int    `json:"number"`
+	Number int `json:"number"`
 	// Configures the size of a buffer. The default is set in the proxy-buffers ConfigMap key.
-	Size   string `json:"size"`
+	Size string `json:"size"`
 }
 
 // UpstreamTLS defines a TLS configuration for an Upstream.
@@ -233,7 +233,7 @@ type HealthCheck struct {
 // Header defines an HTTP Header.
 type Header struct {
 	// The name of the header.
-	Name  string `json:"name"`
+	Name string `json:"name"`
 	// The value of the header.
 	Value string `json:"value"`
 }
@@ -304,7 +304,7 @@ type ActionRedirect struct {
 type ActionReturn struct {
 	// The status code of the response. The allowed values are: 2XX, 4XX or 5XX. The default is 200.
 	Code int `json:"code"`
-	//The MIME type of the response. The default is text/plain.
+	// The MIME type of the response. The default is text/plain.
 	Type string `json:"type"`
 	// The body of the response. Supports NGINX variables*. Variables must be enclosed in curly brackets. For example: Request is ${request_uri}\n.
 	Body string `json:"body"`
@@ -524,13 +524,13 @@ type UpstreamQueue struct {
 // VirtualServerRouteStatus defines the status for the VirtualServerRoute resource.
 type VirtualServerRouteStatus struct {
 	// Represents the current state of the resource. There are three possible values: Valid, Invalid and Warning. Valid indicates that the resource has been validated and accepted by the Ingress Controller. Invalid means the resource failed validation or NGINX
-	State             string             `json:"state"`
+	State string `json:"state"`
 	// The reason of the current state of the resource.
-	Reason            string             `json:"reason"`
+	Reason string `json:"reason"`
 	// The message of the current state of the resource. It can contain more detailed information about the reason.
-	Message           string             `json:"message"`
+	Message string `json:"message"`
 	// Defines how other resources reference this resource.
-	ReferencedBy      string             `json:"referencedBy"`
+	ReferencedBy string `json:"referencedBy"`
 	// Defines the IPs, hostnames and ports used to connect to this resource.
 	ExternalEndpoints []ExternalEndpoint `json:"externalEndpoints,omitempty"`
 }
@@ -558,19 +558,19 @@ type GlobalConfigurationSpec struct {
 // Listener defines a listener.
 type Listener struct {
 	// The name of the listener. The name must be unique across all listeners.
-	Name     string `json:"name"`
+	Name string `json:"name"`
 	// The protocol of the listener. For example, HTTP.
 	Protocol string `json:"protocol"`
 	// The port on which the listener will accept connections.
-	Port     int    `json:"port"`
+	Port int `json:"port"`
 	// Custom SNI processing for listener. Allows listener to be used as a passthrough for SNI processing
 	PassSNI bool `json:"passSNI"`
 	// ipv4 and ipv6 addresses that NGINX will listen on. Defaults to listening on all available IPv4 and IPv6 addresses.
-	IPv4     string `json:"ipv4"`
+	IPv4 string `json:"ipv4"`
 	// ipv6 addresses that NGINX will listen on.
-	IPv6     string `json:"ipv6"`
+	IPv6 string `json:"ipv6"`
 	// Whether the listener will be listening for SSL connections
-	Ssl      bool   `json:"ssl"`
+	Ssl bool `json:"ssl"`
 }
 
 // +k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object
@@ -599,31 +599,31 @@ type TransportServer struct {
 	metav1.TypeMeta   `json:",inline"`
 	metav1.ObjectMeta `json:"metadata,omitempty"`
 	// spec field of the TransportServer resource
-	Spec   TransportServerSpec   `json:"spec"`
+	Spec TransportServerSpec `json:"spec"`
 	// status field of the TransportServer resource
 	Status TransportServerStatus `json:"status"`
 }
 
 // TransportServerSpec is the spec of the TransportServer resource.
 type TransportServerSpec struct {
 	// Specifies which Ingress Controller must handle the VirtualServer resource.
-	IngressClass       string                    `json:"ingressClassName"`
+	IngressClass string `json:"ingressClassName"`
 	// The TLS termination configuration.
-	TLS                *TransportServerTLS       `json:"tls"`
+	TLS *TransportServerTLS `json:"tls"`
 	// Sets a custom HTTP and/or HTTPS listener. Valid fields are listener.http and listener.https. Each field must reference the name of a valid listener defined in a GlobalConfiguration resource
-	Listener           TransportServerListener   `json:"listener"`
+	Listener TransportServerListener `json:"listener"`
 	// Sets a custom snippet in server context. Overrides the server-snippets ConfigMap key.
-	ServerSnippets     string                    `json:"serverSnippets"`
+	ServerSnippets string `json:"serverSnippets"`
 	// Sets a custom snippet in the stream context. Overrides the stream-snippets ConfigMap key.
-	StreamSnippets     string                    `json:"streamSnippets"`
+	StreamSnippets string `json:"streamSnippets"`
 	// The host (domain name) of the server. Must be a valid subdomain as defined in RFC 1123, such as my-app or hello.example.com. When using a wildcard domain like *.example.com the domain must be contained in double quotes. The host value needs to be unique among all Ingress and VirtualServer resources. See also Handling Host and Listener Collisions.
-	Host               string                    `json:"host"`
+	Host string `json:"host"`
 	// A list of upstreams.
-	Upstreams          []TransportServerUpstream `json:"upstreams"`
+	Upstreams []TransportServerUpstream `json:"upstreams"`
 	// The UpstreamParameters are set on stream context
-	UpstreamParameters *UpstreamParameters       `json:"upstreamParameters"`
+	UpstreamParameters *UpstreamParameters `json:"upstreamParameters"`
 	// The parameters of the session to be used for the Server context
-	SessionParameters  *SessionParameters        `json:"sessionParameters"`
+	SessionParameters *SessionParameters `json:"sessionParameters"`
 	// The action to perform for a request.
 	Action *TransportServerAction `json:"action"`
 }
@@ -636,7 +636,7 @@ type TransportServerTLS struct {
 // TransportServerListener defines a listener for a TransportServer.
 type TransportServerListener struct {
 	// The name of a listener defined in a GlobalConfiguration resource.
-	Name     string `json:"name"`
+	Name string `json:"name"`
 	// The protocol of the listener.
 	Protocol string `json:"protocol"`
 }
@@ -724,9 +724,9 @@ type TransportServerAction struct {
 // TransportServerStatus defines the status for the TransportServer resource.
 type TransportServerStatus struct {
 	// Represents the current state of the resource. There are three possible values: Valid, Invalid and Warning. Valid indicates that the resource has been validated and accepted by the Ingress Controller. Invalid means the resource failed validation or
-	State   string `json:"state"`
+	State string `json:"state"`
 	// The reason of the current state of the resource.
-	Reason  string `json:"reason"`
+	Reason string `json:"reason"`
 	// The message of the current state of the resource. It can contain more detailed information about the reason.
 	Message string `json:"message"`
 }
@@ -755,17 +755,17 @@ type Policy struct {
 	metav1.TypeMeta   `json:",inline"`
 	metav1.ObjectMeta `json:"metadata,omitempty"`
 	// spec field of the Policy resource
-	Spec   PolicySpec   `json:"spec"`
+	Spec PolicySpec `json:"spec"`
 	// status field of the Policy resource
 	Status PolicyStatus `json:"status"`
 }
 
 // PolicyStatus is the status of the policy resource
 type PolicyStatus struct {
 	// Represents the current state of the resource. There are three possible values: Valid, Invalid and Warning. Valid indicates that the resource has been validated and accepted by the Ingress Controller. Invalid means the resource failed validation or
-	State   string `json:"state"`
+	State string `json:"state"`
 	// The reason of the current state of the resource.
-	Reason  string `json:"reason"`
+	Reason string `json:"reason"`
 	// The message of the current state of the resource. It can contain more detailed information about the reason.
 	Message string `json:"message"`
 }
@@ -990,18 +990,18 @@ type SecurityLog struct {
 	LogDest string `json:"logDest"`
 }
 
-// The API Key policy configures NGINX to authorize requests which provide a valid API Key in a specified header or query param.
+// The APIKey policy configures NGINX to authorize requests which provide a valid API Key in a specified header or query param.
 type APIKey struct {
 	// The location of the API Key. For example, $http_auth, $arg_apikey, $cookie_auth. Accepted variables are $http_, $arg_, $cookie_.
-	SuppliedIn   *SuppliedIn `json:"suppliedIn"`
+	SuppliedIn *SuppliedIn `json:"suppliedIn"`
 	// The key to which the API key is applied. Can contain text, variables, or a combination of them. Accepted variables are $http_, $arg_, $cookie_.
-	ClientSecret string      `json:"clientSecret"`
+	ClientSecret string `json:"clientSecret"`
 }
 
 // SuppliedIn defines the locations API Key should be supplied in.
 type SuppliedIn struct {
 	// The location of the API Key as a request header. For example, $http_auth. Accepted variables are $http_.
 	Header []string `json:"header"`
 	// The location of the API Key as a query param. For example, $arg_apikey. Accepted variables are $arg_.
-	Query  []string `json:"query"`
+	Query []string `json:"query"`
 }
