Reference environment variables from Trinity config

[vadimkantorov]

Currently we have to adjust/specify in the config various IP addresses which actually tend to change dynamically, and this is very error-prone:

      path: 'postgresql://postgres@10.1.1.1:5432/postgres'

Is it possible to reference from YAML config environment variables? (or maybe pass in a separate config-override .yml file or accept the overrides as part of command-line arguments for the launcher)

I did not find any mention for this in https://modelscope.github.io/Trinity-RFT/main/tutorial/trinity_configs.html

Thank you!

[pan-x-c]

Trinity-RFT uses OmegaConf to load YAML files, and OmegaConf supports accessing environment variables, as described in the official doc

According to the documentation, you can modify your configuration as follows (assuming that the environment variable PG_HOST has already been set):

      path: 'postgresql://postgres@${oc.env:PG_HOST}/postgres'

We will add some examples to the Trinity-RFT configuration tutorial to show how to use environment variables.

[vadimkantorov]

Also, maybe please consider joining into a single config file the trinity and verl config. I think this is already supported, would be great to have it as the recommended way, and in configs in examples in trinity. One config file is a bit easier to version than two

[vadimkantorov]

Could it be possible to replace things like /PATH/TO/CHECKPOINT/ or /PATH/TO/MODEL/ in https://github.com/modelscope/Trinity-RFT/blob/main/examples/grpo_gsm8k/gsm8k.yaml with environment variable references? or some other way which can make possible running these configs without having to modify them even for the basic, smoke-test run?

It would also be nice to show the recommended way of passing these environment variables via ray job submit (via runtime-env?)

[pan-x-c]

Good suggestion, we will optimize example config files this week.