We may want to resolve URIs later, but as if in a older point in time, using a timestamp.
So that latest would resolve to the latest at that point in time - not now.
Problems
This is needed for generating the "pinning" for AYON USD Resolver if a USD file is written later (e.g. on farm) but user wants to pin it to the point in time when they submitted job initially. This is because e.g. Houdini USD Render jobs export the USD on the farm - hence it does not exist yet at the time the artist is working with the stage.
Proposal
Add a timestamp argument to the resovle endpoint.
TODO
[ ] Add timestamps argument to endpoint.
[ ] Should we care about the edge case where someone "publishes into an existing version". What happens with that timestamp?
Story
We may want to resolve URIs later, but as if in a older point in time, using a timestamp. So that
latest
would resolve to the latest at that point in time - not now.Problems
This is needed for generating the "pinning" for AYON USD Resolver if a USD file is written later (e.g. on farm) but user wants to pin it to the point in time when they submitted job initially. This is because e.g. Houdini USD Render jobs export the USD on the farm - hence it does not exist yet at the time the artist is working with the stage.
Proposal
Add a
timestamp
argument to the resovle endpoint.TODO
timestamps
argument to endpoint.Attachments
Note
This is just a proposal for now