cli icon indicating copy to clipboard operation
cli copied to clipboard

Unified hcloud experience over all hetzner products (S3 Object Storage, Dns, Storage Box, ...)

Open c33s opened this issue 1 year ago • 11 comments

TL;DR

providing a unified, consistent experience for developers across all hetzner products would be such a win for your customers. we dream of having one tool to rule them all! 😉

Expected behavior

the DNS API is not Part of the Hetzner Cloud product. Therefore there are no plans to integrate the DNS API into the hcloud CLI.

https://github.com/hetznercloud/cli/issues/321#issuecomment-830798363

All our integrations rely on the Hetzner Cloud public API, which is available with a certain level of stability. Since the features you are requesting are not in the public API, we cannot implement them.

https://github.com/hetznercloud/cli/issues/880#issuecomment-2476414492

as a developer, i don’t really mind which product an api belongs to, as long as it’s from the same provider. ideally, these details (which department or team is responsible) should be managed internally. from our perspective, we just want seamless support across all hetzner products.

for many of us, hcloud is the cli tool for interacting with hetzner, and expanding its capabilities to cover more products (like dns, s3, storage box, robot, etc.) would be fantastic! making your products more accessible to developers will only encourage wider adoption—and ultimately benefit both sides. for instance, integrating storage box with terraform would be amazing!

it’s your "fault" that i even ask about hcloud/terraform support, you created such a great experience with hcloud (good listing, excellent export possibilities, great terraform provider, ...) that working with a different product of hetzner can easily feels like pain.. hetzner/you brought me to terraform, i read a newsletter announcement you made or the cloud documentation (i cannot remember) and read about terraform. since then i started using terraform and choose only providers which have a good api with terraform support. you don't have to wonder developers ask for this, your tool is just too good 😛😀

providing a unified, consistent experience for developers across all hetzner products would be such a win for your customers. we dream of having one tool to rule them all! 😉

edit: developers please help voting!

Where can we open a ticket for requesting API support?

https://github.com/hetznercloud/cli/issues/880#issuecomment-2476863712

You can reach out to us using the Support Center.

https://github.com/hetznercloud/cli/issues/880#issuecomment-2476944337

as stated above we need to vote via hetzners internal ticket system/support system. maybe it helps if we send

We vote for https://github.com/hetznercloud/cli/issues/918

lets help this awesome hetzner developers to get a bigger budget from their bosses!

c33s avatar Nov 15 '24 14:11 c33s

This is totally understandable. But Hetzner is divided in both Hetzner (the Bare-Metal/Robot/StorageBox stuff) and Hetzner Cloud (VMs/Load Balancer/Object Storage stuff). These are even two companies. By conway's law, you're requiring a full reorganisation Hetzner with this ticket.

Still, I'm totally rooting for it!

bebehei avatar Dec 21 '24 21:12 bebehei

Well even object storage is not in their terraform provider. I am an infrastructure consultant and when I float the idea of migrating from US providers to hetzner, friction points like these are still what makes them stay with AWS. From the outside it seems hetzner is still not really taking "that cloud stuff" seriously.

mzhaase avatar Mar 26 '25 10:03 mzhaase

I have to agree. I was planing on migrating parts from AWS to hetzner, but not having a terraform setup that works for both (vms and the object storage) is a big no-go.

tkschmidt avatar Mar 27 '25 20:03 tkschmidt

@tkschmidt While there is no unified one, TF providers for both servers and object storage exist and are documented on the Hetzner website.

pat-s avatar Mar 27 '25 22:03 pat-s

@mzhaase , @tkschmidt I totally agree with @pat-s here: In any reasonably sized TF project you need to mix a multitude of providers. And terraform (or opentofu) provides a nice unified experience across your project where you can e.g. use the output of one resource as input to another regardless of the providers involved. 👍

That said it would be nice to be able to provision bare metal servers with terraform, but I wouldn't mind if that was a separate provider. 😃

rwunderer avatar Mar 28 '25 08:03 rwunderer

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.

github-actions[bot] avatar Jun 26 '25 13:06 github-actions[bot]

unstale

c33s avatar Jul 14 '25 04:07 c33s

Will the hcloud CLI get support for the new storage box API?

taladar avatar Aug 04 '25 08:08 taladar

Will the hcloud CLI get support for the new storage box API?

Yes, see https://github.com/hetznercloud/hcloud-go/issues/675#issuecomment-3053142226 for more details.

jooola avatar Aug 04 '25 08:08 jooola

the DNS API is not Part of the Hetzner Cloud product. Therefore there are no plans to integrate the DNS API into the hcloud CLI.

Since this is about to change, will the cli get DNS support?

ethrgeist avatar Oct 10 '25 18:10 ethrgeist

the DNS API is not Part of the Hetzner Cloud product. Therefore there are no plans to integrate the DNS API into the hcloud CLI.

Since this is about to change, will the cli get DNS support?

Yes, the CLI gained support for the new Cloud DNS API with release v1.54.0.

lbrocke avatar Oct 11 '25 08:10 lbrocke