-
Notifications
You must be signed in to change notification settings - Fork 9
RFC: API-v2 - Standardized and Fully Documented API #224
base: main
Are you sure you want to change the base?
Conversation
|
|
||
| [Timestamps](#timestamps) | ||
|
|
||
| ## Introduction {#introduction} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need the {#...} part in the headers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll just use this comment thread to make a note about the formatting:
- Table of contents should be re-formatted.
- Code blocks in this file should be properly formatted too.
Tasks and Project Webhooks can be restructured as Project Triggers, including support for external triggers beyond webhooks.
| "result": "STOPPED", | ||
| "state": "FINISHED" | ||
|
|
||
| "timeline": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so we do not have the final decision here wether to put timeline in status or metadata?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for "live" resources timeline will be in status, and we will keep base timestamps in metadata
| }, | ||
| "spec": { | ||
| "agent": { | ||
| "ports": [{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agent ports should be in status -> agent as is the ip address.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
feel free to move it
This PR introduces the initial RFC for API-v2, a project aimed at standardizing our API structure and implementing comprehensive documentation for all endpoints.
Key points:
This RFC outlines the motivation, proposed solutions, and open questions for discussion.