-
Notifications
You must be signed in to change notification settings - Fork 5
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
API for deploying by URL #29
Comments
Suggestion which would work for one use-case I have:
My example does not include the ability to provide a new URL; only to refresh the one provided on the dashboard. I imagine the webhook URL should include a randomized string to prevent unauthorized interruptions, while being more flexible to work with than authorization tokens, just as in Discord's webhook URLs for sending a message. |
Persistent API tokens are being worked on, it's something we've known about for a while, it just hasn't been released yet. The API endpoint you found is indeed the correct one, though you can also use That being said, it should be noted that the GitHub integration is not cloning the entire repository. The webhook is used to send a request to Deploy that there is a new commit on the default branch. From there, the process is very similar to deploying from a URL, we simply take the If you're interested in scripting your updates, you can also check out the unstable Terraform provider which includes a client SDK (written in Go) for the API. |
We have static tokens now (create them via your account page). The API is not documented and subject to change, but for now you can use |
Does It replies with |
Hi deno team!
I really, really love the fact that you've built the ability to deploy through a script hosted on the web!
As much as I love git, I don't think it's necessarily the right primitive for deploying web applications, since git clones take a non-trivial amount of time and serves as a minimum latency floor for our iteration cycles. Static assets, on the other hand, feels like a much better primitive since it is the de-facto primitive of the web, and has minimal latency overhead for propagating updates.
That said, one thing I would love to see is the ability to hook into deno deploy's ability to create deployments using a script, through some kind of unofficial API. I see that right now, this is done through the following API call:
I can already call this API outside of the Deno deploy dashboard, but the fact that there's no way to get issued a persistent authorization token makes the usage rather awkward, as I'd have to deal with the fact that my dashboard token can expire, and manually refresh it from time to time.
Would you please consider the ability to issue an API token from the dashboard to allow other tools to leverage Deno deploy more conveniently? No need to offer any guarantee of API stability, given the early experimental state of the service itself. This could totally stay a use-at-your-own-risk type of thing for the foreseeable future.
Thanks!
The text was updated successfully, but these errors were encountered: