Merged
Conversation
… db to include status of deployment
…f workflow run, persist logs from API executions, removed session validation in favor of API key
…h copy boxes for url, keys, & ex curl
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
waleedlatif1
force-pushed
the
feature/api
branch
from
94930ba to
4290d47
Compare
waleedlatif1
commented
Feb 24, 2025
Collaborator
Author
waleedlatif1
left a comment
waleedlatif1
left a comment
There was a problem hiding this comment.
Helloooooooooo
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR introduces a one-click deploy as an API button in the control bar that allows users to deploy workflows as an API endpoint. As for now, each endpoint has its own corresponding key and we use that for validation, since we will leave the more sophisticated session/user validation for the SDK implementation.
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?
This can be tested by clicking the deploy button, grabbing the API token/the example curl, and running it. So long as the key matches up, we can execute the workflow. Though not currently visible, we store the logs in the workflow_logs table where the user will be able to see the logs from all executions, regardless of how they were triggered (manual, scheduled, API).