In terms of the job ads.
The JobRouter is the equivalent of your example and those values will end up in the *routed* ad. i.e. the classad on the batch schedd.
Those extra values do not get brought back to the CE resource classad.
You could probably inject them back into the CE ads with hooks but Iâve never bothered.
I just have PER_JOB_HISTORY_DIR set up on the batch schedds anyway and use that one, which allows me access to the routed classad attributes. i.e. hepspec, datacentre etc.
Description: S/MIME cryptographic signature