-
Notifications
You must be signed in to change notification settings - Fork 75
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
Create constructs for dealing with soft-deleted workspaces #668
Labels
Comments
Closed
JAORMX
added a commit
that referenced
this issue
Jan 21, 2025
This implements listing, recovering and hard-deleting archived workspaces. Closes: #668 Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com>
JAORMX
added a commit
to JAORMX/codegate
that referenced
this issue
Jan 21, 2025
This implements listing, recovering and hard-deleting archived workspaces. Closes: stacklok#668 Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com>
JAORMX
added a commit
to JAORMX/codegate
that referenced
this issue
Jan 21, 2025
This implements listing, recovering and hard-deleting archived workspaces. Closes: stacklok#668 Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com>
JAORMX
added a commit
that referenced
this issue
Jan 21, 2025
* Implement CRUD actions for dealing with archived workspaces This implements listing, recovering and hard-deleting archived workspaces. Closes: #668 Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com> * Add pragma to enable foreign key support in SQLite Co-Authored-By: Alejandro Ponce de Leon <aponcedeleonch@stacklok.com> Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com> --------- Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com> Co-authored-by: Alejandro Ponce de Leon <aponcedeleonch@stacklok.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A recent pull request introduced the ability to soft-delete workspaces. We now need to deal with this construct.
Let's add the ability to:
This should encompass the REST API and the prompt pseudo-CLI.
The text was updated successfully, but these errors were encountered: