However, these track tokens are serialized (ie token 1,2,3,4,5...), and we don't want to have to update thousands of metadata json files across each copy of a track when they all share the same metadata.
To make any token leverage the track's common metadata, we created a transformation rule on Domino's dcdata subdomain to automatically redirect a request for any token's metadata (ie .../metadata/10) to return the common metadata.json for the track. This way we only need to update two files for each track on regen: the image and it's singular metadata file.
The dynamic rule at the DNS level takes a portion of the dcdata uri path and uses it to redirect to the correct file path on R2: