We're doing discovery on API key scopes at the moment, we don't yet have a public ETA for this but rest assured it's being worked on!
Regarding IPv6-only origin support, We brought this in just last week! We now support IPv6-only addresses direct as an origin, as a hostname, as well as dual stack hostname resolution.
Best, Joe
If you had have supported API key scoping then I'd have a ton of businesses/startups running on you. As it stands currently it's difficult for me to recommend you to orgs that are scaling up. Compliance in particular was the biggest issue. For one-man shops it's a no-brainer.
In your defense, Cloudflare has historically also sucked in this area.
Anyways, I'm looking forward to this feature!
It would be awesome if the API would get more robust and documented in general -- right now it seems some params seem to not really work (ex storage zone search), and other endpoints take so many without much clarity over what will be set as the default and what's required. I found that for most calls I needed to check the network requests from the dashboard to see how to use them, would be awesome to have more documentation and examples here showing common flows.
How does the USD1 minimum works? Say I have setup a pull zone and i don't use it for over a month, I get charged anyway?
Thanks.
I’ve been using cloud services in one way or another from different providers (including EU based like Hetzner) and never seen this before. It’s always been pay for what you use and nothing more, which is kind of the whole pitch of cloud services.
So, my scripts on my servers dont have the bunny api key. Its only saved within those edge functions and I authenticate against the edge functions.
A little bit more effort than scoped keys but it works