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

File downloading #148

Merged
merged 3 commits into from
Mar 7, 2024
Merged

File downloading #148

merged 3 commits into from
Mar 7, 2024

Conversation

rebkwok
Copy link
Contributor

@rebkwok rebkwok commented Mar 6, 2024

Uses the existing contents_url, and the default for the download filename (i.e. uses the existing filename). I don't think there's a need to include group names or paths in the downloaded filename.

As discussed, only output-checkers can download release request files, and only for requests that they did not author. We don't restrict the types of files that can be downloaded by output-checkers. No workspace files can be downloaded by anyone.

Fixes #126

airlock/views/helpers.py Dismissed Show dismissed Hide dismissed
Copy link
Member

@bloodearnest bloodearnest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good.

Where did we land on the "only downloading csv files" question?

@rebkwok
Copy link
Contributor Author

rebkwok commented Mar 7, 2024

Where did we land on the "only downloading csv files" question?

We said we'd allow any files to be downloaded, given that CSV is the most high-risk anyway, and we're limiting it to output-checkers and release request files only

@rebkwok rebkwok merged commit 7ad669f into main Mar 7, 2024
8 checks passed
@rebkwok rebkwok deleted the file-downloading branch March 7, 2024 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support downloading files to remote desktop in secure environment
2 participants