Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate manifest file with UUID-labeled name, not a temporary file name #74

Closed
jeff-cohere opened this issue Jul 26, 2024 · 0 comments · Fixed by #80
Closed

Generate manifest file with UUID-labeled name, not a temporary file name #74

jeff-cohere opened this issue Jul 26, 2024 · 0 comments · Fixed by #80
Labels
enhancement New feature or request

Comments

@jeff-cohere
Copy link
Collaborator

When a transfer has completed, the DTS writes a manifest file to a directory and then transfers it to it's payload's destination. Currently, this manifest file is treated as a temporary file with an autogenerated name. The name does not indicate which transfer the DTS file belongs to, so there's no way to map these files themselves to transfers.

Since each transfer is already uniquely identified by its UUID, it would be pretty easy to generate a "temporary filename" using the UUID instead of an autogenerated numeric sequence (e.g. manifest-{UUID}.json). We could also embed the transfer UUID in the manifest itself to help in cases where the file has been renamed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant