Skip to content
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

feat: new APIs for traffic pricings #827

Merged
merged 4 commits into from
Jul 25, 2024
Merged

feat: new APIs for traffic pricings #827

merged 4 commits into from
Jul 25, 2024

Conversation

apricote
Copy link
Member

The API has been updated to provide a better insight and more flexibility for displaying the pricing of traffic for servers and load balancers.

In addition to the new fields, the old fields are deprecated and will be set to null in the API on 2024-08-05.

In the CLI this mostly affects the hcloud server-type list command, where we have previously shown a column traffic. This is no longer possible, because there is no single included traffic for a server type, and instead this depends on the location. We have set the field to - and removed it from the default columns. The information is still available in hcloud server-type describe <server-type-name>, now in the "Pricing" section of the output.

This also affects the JSON and YAML output of both hcloud server-type list and hcloud server-type describe as we use the API schema for this.

You can learn more about this change in our changelog.

release-please Info

BEGIN_COMMIT_OVERRIDE
feat(server-type): show traffic details for each location in describe output
feat(load-balancer-type): show traffic details for each location in describe output
fix(server-type): remove deprecated traffic column
END_COMMIT_OVERRIDE

@apricote apricote self-assigned this Jul 25, 2024
@apricote apricote requested a review from a team as a code owner July 25, 2024 11:19
@apricote apricote merged commit 5c9380c into main Jul 25, 2024
5 checks passed
@apricote apricote deleted the traffic branch July 25, 2024 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants