Steps to reproduce

1.  Create a link to an S3 asset within content (see attached image jcr) (this requires using the s3 external dam connector)
2.  Try to retrieve this content via a delivery endpoint (see attached image endpoint) with this s3 link resolved and metadata included

Expected results

The @link node has the s3 URL without a datetimestamp appended to it.

Actual results

The @link node has the s3 URL with a datetimestamp appended to it. The timestamp is equal to time.now

Example:

"albumImage": {
"@name": "LCWorship_Gloria_AlbumImage.jpg",
"@path": "magnolia-cms-live/Media/Worship/gloria/LCWorship_Gloria_AlbumImage.jpg",
"@id": "s3:magnolia-cms-live/Media/Worship/gloria/LCWorship_Gloria_AlbumImage.jpg",
"@link": "https://magnolia-cms-live.s3.amazonaws.com/Media/Worship/gloria/LCWorship_Gloria_AlbumImage.jpg?1636056437809",
"metadata":

}

Workaround

None that I could find.

Development notes

This ticket comes from EXTDAM-326 to fix the issue with the timestamp only.