Is it possible to pass extra keys from a recipe to a fix?

[bsolino]

I'm currently working on a cmorizer as a fix that uses an unstructured grid, and all the information about the grid is stored on a separate file. Furthermore, this grid changes depending on the specific dataset we are accessing.

To solve this, I included an extra key in the recipe with the path to the grid file:

datasets:
  - {
      dataset: ICON,
      project: native6,
      ...
#       grid_file: grid_file.nc,
      grid_file: /absolute/path/to/dataset/grid_file.nc,
      version: v1
    }

However, I couldn't find a way to reach those keys from the fix. The only metainformation the fix receives is in the form of a VariableInfo (https://github.com/ESMValGroup/ESMValCore/blob/622366123bc57df1796a558dec7b24316c113041/esmvalcore/cmor/table.py#L459), but it seems it is information from the variable's CMOR Table.

I was wondering if there was some way to pass these extra recipe keys with the fix, or to access them from within (for example, a globally accesible Recipe object). Furthermore, to avoid having to use the absolute path, would it be possible to access the DRS information as well?

If this is not currently possible, does anybody have a strong opinion on a good way to implement it?

[senesis]

See answer here