added optional dbName in header for tls

[manishkuri]

In the case of a TLS-enabled environment, our Istio service needs a dbName in the header to route the request. In all our environments, we don't necessarily keep a "default" database, so we want to send something from the UI to it.

Without it, the Attu connection breaks on milvusClient.healthCheck().
With this code change it works fine.

[shanghaikid]

I don't think you need this here. you can set the process.env.DATABASE. it will be passed from the client.

But still, you need to pass the database to the MilvusClient.

like this：

const clientConfig: ClientConfig = {
        address: milvusAddress,
        token,
        username,
        password,
        logLevel: process.env.ATTU_LOG_LEVEL || 'info',
        database: database || this.DEFAULT_DATABASE,
      };

[shanghaikid]

Thanks for the patch.

[manishkuri]

I don't think you need this here. you can set the process.env.DATABASE. it will be passed from the client.

But still, you need to pass the database to the MilvusClient.

like this：

const clientConfig: ClientConfig = {
        address: milvusAddress,
        token,
        username,
        password,
        logLevel: process.env.ATTU_LOG_LEVEL || 'info',
        database: database || this.DEFAULT_DATABASE,
      };

hi @shanghaikid , didn't get this.
i am assigning this to clientConfig.database inside if statement. i see in SDK that clientConfig has a optional field database. it is also working this way.
I did not understood your comment here

[shanghaikid]

database should be passed from the client to the server side.
The client will read process.env.DATABASE .

Yes, you can setup new DB_NAME env here, but it will be a conflict with process.env.DATABASE

[manishkuri]

got it, updated.
thanks @shanghaikid