Closed patrick-austin closed 3 years ago
Having looked at this further, it seems these functions are only used by Atlas functions (e.g. scratchdisk lifetime). Most places use a usual config_get()
function (which doesn't cache). Atlas will not be running m-VO, so no change should be needed. Closing.
Motivation
Currently we cache 3 values related to the policy specified in rucio.cfg without including the VO in their key. This may cause an issue in actual use, but it may not. Whether it does is dependent on the policy package changes being made by James.
Modification
Look at the policy package updates and see if a change is required or not. If so, then simply including the VO in the cache key should be sufficient to prevent any issues.