I remember when I was asked to replace a core router with a more powerful model. The uptime of the Cisco router was ten years - and it was ten years after the datacenter went into service.
This recommendation is currently broken. Even when you pin the full commit SHA for an action, that action may still pull in transitive dependencies (other actions) that aren't pinned.
> Sometimes users will still get errors from PowerDNS directly, but I added some logging of all the errors that users see, so hopefully I can review them and add extra translations if there are other common errors that come up.
I noticed that you are using our Go module to access the API. It is wonderful to see our work helping others build great software, especially for education. Thank you for that.
Please note that the upstream API sometimes changes slightly between minor releases. For example, prior to v4.9, the error response for a non-existent server was "Not Found". Starting with v4.9, it changed to "Method Not Allowed".
Unfortunately, error responses aren't always part of the API specification. I'm thinking about adding the most common cases to the module anyway.
> At the moment there is still a one-time order fee for dedicated servers
For (some) dedicated servers, I think. Last time I checked the lowest tiered dedicated servers didn't have any setup fees. If it's not mentioned, assumed it'll remain.
As diggan said, there's usually at least one of their dedicated server offerings for which setup fees are waived, so I figure my tests would use the API to find out which one and use it :)