[Bug]: server/v2/api/grpc: Server disregards Config's Enable field

[mark-rushakoff]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

I was writing some tests with simd/v2, and the start command was failing because the gRPC server component could not bind to port 9090. I did not need the gRPC server for my test, so I set the config to Enable=false, but it still tried to bind to 9090.

The (*GRPCServer).Start method is short enough that it is easy to see it does not respect the Enable setting:

cosmos-sdk/server/v2/api/grpc/server.go

Lines 73 to 94 in d426a5d

	func (g *GRPCServer[AppT, T]) Start(ctx context.Context) error {
	listener, err := net.Listen("tcp", g.config.Address)
	if err != nil {
	return fmt.Errorf("failed to listen on address %s: %w", g.config.Address, err)
	}
	errCh := make(chan error)
	// Start the gRPC in an external goroutine as Serve is blocking and will return
	// an error upon failure, which we'll send on the error channel that will be
	// consumed by the for block below.
	go func() {
	g.logger.Info("starting gRPC server...", "address", g.config.Address)
	errCh <- g.grpcSrv.Serve(listener)
	}()
	// Start a blocking select to wait for an indication to stop the server or that
	// the server failed to start properly.
	err = <-errCh
	g.logger.Error("failed to start gRPC server", "err", err)
	return err
	}

For my purposes, setting Address=127.0.0.1:0 to bind to an anonymous port is a sufficient workaround, although Enabled=false would be preferable.

Cosmos SDK Version

main

How to reproduce?

No response