-
Notifications
You must be signed in to change notification settings - Fork 79
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
Consider merging hcloud-upload-image in this tool #825
Comments
I'd like to add that as an alternative, the possibility to directly upload snapshot images via the API would be much appreciated. |
Technically this is not an issue, I did a very quick port last week after the point was made in your docs PR. I am not sure yet if we want to officially support this, as the risk with leftover paid servers is there. Also if an official API is added we would immediately deprecate/remove the workaround. I have asked the team responsible for Servers and Images for their opinion on this and also added votes to the "Upload Image API" card in our internal feedback tracker. |
I'm wondering if they had any opinion that could be shared. |
Bad news, we do not want to provide official support for the workaround CLI for the foreseeable future. The teams opinion matched my own:
If we add an official API, it will be immediately supported in the CLI & hcloud-go. |
TL;DR
Hey folks,
For Fedora CoreOS, we are looking at using https://github.com/apricote/hcloud-upload-image to document how to setup Fedora CoreOS on Hetzner Cloud.
https://github.com/apricote/hcloud-upload-image is currently marked as not officially supported by Hetzner / not an official Hetzner Cloud product.
We would appreciate if you could consider making it an official tool or merging it in this tool.
That would increase our (and our user's) confidence in this process and thus let us display Hetzner as a supported platform for Fedora CoreOS.
Thanks!
Expected behavior
https://github.com/apricote/hcloud-upload-image becomes an official tool in some form.
The text was updated successfully, but these errors were encountered: