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

Use a friendly file name when downloading files (e.g. support package) #9634

Open
labo-flg opened this issue Jan 17, 2025 · 0 comments
Open
Assignees
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team

Comments

@labo-flg
Copy link
Member

labo-flg commented Jan 17, 2025

Use case

When a file is generated by the platform, most of the time we use a generated UUID for the file name.
This is the case for the support packages, or the exclusion lists for instance.

When the user download these files, a direct link is generated to the storage, and thus the filename is preserved : it's an unfriendly UUID.
We have all the required context to improve this and use a meaningful name, such as the support package date-time, or the exclusion list name.

Current Workaround

No workaround

Proposed Solution

Proper solution would be to introduce a new API downloadSupportPackage for instance that will build the right file specs and push it for download.

@labo-flg labo-flg added the feature use for describing a new feature to develop label Jan 17, 2025
@labo-flg labo-flg added this to the Release 6.5.0 milestone Jan 17, 2025
@labo-flg labo-flg self-assigned this Jan 17, 2025
@labo-flg labo-flg added the needs triage use to identify issue needing triage from Filigran Product team label Jan 20, 2025
@labo-flg labo-flg modified the milestones: Release 6.5.0, Release 6.4.9 Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
Projects
None yet
Development

No branches or pull requests

1 participant