This has lead to breaking changes downstream in JS when the return types changed to support a feature in the CLI
This PR
Add /v2/api
Leave the unprefixed paths as-is (but deprecated) as a (long) grace period
» curl https://runfission.net/v2/api/ping
"pong"
Why the version first? Because we're also going to having things like versioned docs (/v2/docs). I have no strong feelings on this; just seemed to make sense.
While I Had the Hood Up 👩🔧
We've had folks try to use 3rd party tools to check if our server is up. We have nothing at the root, so these didn't return a success code and show as failed. For example:
Currently Deployed
Today our API is unversioned:
This has lead to breaking changes downstream in JS when the return types changed to support a feature in the CLI
This PR
/v2/api
Why the version first? Because we're also going to having things like versioned docs (
/v2/docs
). I have no strong feelings on this; just seemed to make sense.While I Had the Hood Up 👩🔧
We've had folks try to use 3rd party tools to check if our server is up. We have nothing at the root, so these didn't return a success code and show as failed. For example:
https://downforeveryoneorjustme.com/runfission.com
...except it's not down; it's just not returning a 200-level code!
So I added an empty path at the root that returns a 200 and no body:
Docs
/v2/docs
Latest
V2
(Currently the latest)