Better and more pricing information

[deliciouslytyped]

It would be nice if there was a subcommand for getting all the pricing information that can be retrieved from the pricing API in a tabular form.

Also, I'm new to Hetzner so maybe I missed something, and I'm not sure if this is possible with the current API (for which I don't see an issue tracker anywhere) - but it would be great if

• it was possible to get the the current cost per hour / per month for a context,
• the same information for all the resources that have costs
  • (I don't think primary-ip has the pricing on it right now like how server describe does)
  • it would be good to have a tabular view of all resource that have a cost associated, in one view, with a column for the resource, the cost, and the pricing type (e.g. assign IDs to prices or something, so you dont have the "confusion" described in Add prices for server list #241 where prices differ by region)
• and just pricing information in general, to help me manage my costs.

This way it wouldn't be necessary to go to the GUI to look for this information, it's easier to set up alerts, etc.

What do you think?

xref #241

[deliciouslytyped]

Another nicety would be (the option of) showing the user a confirmation when they are creating a new resource e.g. a server, whether they would like to create it at the given aggregate (split into items forming the total) price.

This would actually be doing a better job than the GUI currently, because unless I missed something, or it's this way by design, nothing on the GUI actually counts the cost of e.g. IP addresses into displayed values. I've only seen the primary IP cost mentioned in policy statements, or at the bottom of the server creation GUI.

(To be fair the Hetzner pricing model is not that complicated.)

If (calculated-by-hetzner) pricing information (that e.g Hetzner will stand by / or label the interface alpha and unreliable) can be provided that could also enable (better) pricing prediction in provisioning tools. - though I don't know if anything actually does that currently.

[deliciouslytyped]

Ping?

[lfkdev]

I would be a fan of that too

[lfkdev]

Why got this marked as completed? I can't see the feature or similar in the changelog

[deliciouslytyped]

cc @apricote , I also don't see why this was closed?

[apricote]

Well, two problems happened here:

• GitHub changed the message when closing issues to "closed this as completed", and added another one called "closed as not planned". The stale bot still uses the default, so the messaging is a bit weird right now
• Our stale bot is a bit overzealous and we currently have no option to "freeze" an issue

I will add reconfiguring the stale bot to my backlog and reopen the issue for now.

[apricote]

I added the request for a public API for the usage information to our internal feedback tool.

For the other data, its available through GET /pricing, which is not as nice as the included data for servers, but we can work with this.