add endpoint information at startup.

[balamurugana]

No description provided.

[nitisht]

Can we put this info in the log.json, that will be more helpful I think. Something like

{SERVER_ENDPOINT: "", ACCESS_KEY: "", ENABLE_HTTPS: "", SERVER_REGION: "",
MINT_DATA_DIR: "", MINT_MODE: ""}

as the first entry and then the test logs?

[balamurugana]

Adding into log.json would make dynamic json file i.e. the first log entry is not compatible with other known json structure. Is this expected?

[nitisht]

Adding into log.json would make dynamic json file i.e. the first log entry is not compatible with other known json structure.

Yes that is true. But is that a problem? I mean while parsing logs we can start from second entry.

Also, we can add an entry called timestamp like

{SERVER_ENDPOINT: "", ACCESS_KEY: "", ENABLE_HTTPS: "", SERVER_REGION: "",
MINT_DATA_DIR: "", MINT_MODE: "", TEST_RUN_TIME:""}

It will help keep track of multiple mint runs happening in automation.

[balamurugana]

You can skip first line. This needs to be documented. According to JSON it is multi-lined document. This requires more discussion and I would recommend your requirement needs to be fixed in different PR

[nitisht]

This requires more discussion and I would recommend your requirement needs to be fixed in different PR

Okay I will create an issue with the details.

[poornas]

Seems like it would be good to separate sdk level "detail" logs from run summary logs - the env flags used by Mint would fall in the latter category along with details like average runtime for the sdk.

[kannappanr]

Is there any way for us to pass MINT_DATA_DIR? If not, should we log it here?

[kannappanr]

I see that the value for MINT_DATA_DIR can be passed via environment variable.

[balamurugana]

Yes. for non-docker env i.e. when we run it by hand

[kannappanr]

LGTM