upctl storage import should allow content-type header to be specified manually for URLs

[jpluscplusm]

Is your feature request related to a problem? Please describe.

I'm trying to import a storage image that's compressed, but where the upstream server doesn't respond with the Content-Type header required by UpCloud. Therefore I'm forced to pull the image down locally, and upload it using the CLI.

Describe the solution you'd like

I'd like the upctl storage import command to provide an option to import from a URL, whilst allowing the content-type to be specified manually.

Describe alternatives you've considered

I'm downloading the image locally, and using the CLI's undocumented filename-extension sniffing to import it with the appropriate content-type header.

Additional context

[mgajda]

@jpluscplusm Can you kindly test whether #634 works for you?

[kangasta]

Thank you for the feature request and sorry for the delay with this!

From what I understood, the desired flow would be to skip downloading the file to a intermediate machine before uploading it to UpCloud API, so #634 would solve a different issue as it adds support for setting content-type manually for local file uploads 🤔

I think that our API does not currently support overriding the content-type when using URL import source, so this is not something we can solve on the client side. I'll log a feature request to the team working with our block storages. I assume you are using external server as the import source, so you cannot control which headers are included in the response?

[jpluscplusm]

I assume you are using external server as the import source, so you cannot control which headers are included in the response?

Exactly. FWIW, I’ve been trying to get FreeBSD’s VM-IMAGES to work on upcloud (https://download.freebsd.org/releases/VM-IMAGES/15.0-RELEASE/amd64/Latest/), whose upstream URIs didn’t provide the necessary headers when I last checked.

Using these upstream images would allow one to start a FreeBSD VM considerably faster than scripting an install using upcloud’s provided ISOs; and IMHO would be conceptually cleaner than templatising an already booted machine.

[mgajda]

While I can fix client-side UpCloud Go API, as an independent developer I cannot access and fix UpCloud's server side API. Meanwhile this PR only allows upload from client's machine.
@kangasta The ball is in your court (I would update the PR when API allows).

[jpluscplusm]

@mgajda May I suggest you update your PR so it's merely

For #581

and not

Fixes #581

... given the limitations of a client-side change not being able to fully address this issue's main concern? 😀

[mgajda]

@mgajda May I suggest you update your PR so it's merely

For #581

and not

Fixes #581

... given the limitations of a client-side change not being able to fully address this issue's main concern? 😀

Done.