-
Notifications
You must be signed in to change notification settings - Fork 76
Initial CRUD API for workspaces #620
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
Conversation
a180108
to
2cf1dda
Compare
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 wonder if we should also have the dashboard APIs under api (can be done in a different PR).
Do you think we should introduce api version handling while we have the opportunity and set this as api/v1 ?
b73e08e
to
a668d57
Compare
I'm already doing this, we actually have See:
Versioning APIs is a best practice which I like to follow 😄 |
This adds a simple and unimplemented REST API for workspaces. Workspaces will be the base for all other resources in terms of REST resource mapping, so these go first. These are initially left entirely unimplemented as stacklok#600 needs to merge Signed-off-by: Juan Antonio Osorio <[email protected]>
stacklok#633 accidentally deleted some functions that were introduced by stacklok#620 This re-introduces them. Signed-off-by: Juan Antonio Osorio <[email protected]>
#633 accidentally deleted some functions that were introduced by #620 This re-introduces them. Signed-off-by: Juan Antonio Osorio <[email protected]>
This adds a simple and unimplemented REST API for workspaces. Workspaces
will be the base for all other resources in terms of REST resource
mapping, so these go first.
These are initially left entirely unimplemented as
#600 needs to merge
Signed-off-by: Juan Antonio Osorio [email protected]