So I understand this likely isn't possible due to circular dependencies, but is it possible to access a parameters value in a omegaconf resolver? For context, I have a dictionary in a parameter file with a list of countries and some features I need later for that country. I would like to use the list of keys (the country names) in a query for when I pull the data, the solution I have would be to access this parameter as part of the resolver and add the keys to a list so I don't have to duplicate changes in multiple places

As you said accessing the values from

OmegaConf

could lead to circular dependencies so it isn't standard practice. Not sure if there is a way.