-
Notifications
You must be signed in to change notification settings - Fork 18
Feature: allow to pass the image URL directly to the devices #400
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
base: master
Are you sure you want to change the base?
Conversation
b-rowan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine to me, simple enough fix.
|
Can you squash those commits into one, then I will merge. |
|
I don‘t quite understand why this is needed. We already support hosting files on an external server without having to go through gooseBit to download them. |
easybe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would have to look, but any backend shouldn't change the behavior of the remote server, so I would assume this is a regression. |
|
I commented on the issue: #399 (comment). @jkuri are you around to help us out here? |
I'll check later today, but as far as I recall I did fix the CDN issue later after this was introduced. |
|
I am not sure what is wrong with this fix @easybe? I would rather just simplify it without additional props in configuration; parsed_uri = urlparse(software.uri)
if parsed_uri.scheme in ("http", "https"):
href = software.uri
else:
# this still handles files prefixed with s3:// or file:// like before
href = str(request.url_for("download_artifact", dev_id=device.id)) |
Yes, that looks fine to me. Definitely no additional setting for this. |
Fix for #399