-
Notifications
You must be signed in to change notification settings - Fork 5
Need to add endpoint for cleanup workspaces that have been running for more than fixed period of time #24
Comments
@davidfestal maybe you will be able to provide some guidance about local dev flow for |
Sure.
If the Eclipse Auto-Build is enabled, you would have the various language services (completion, etc ...) Additionally, the Anyway, I should have completed the Readme long ago. Sorry about that. I'll also add a Che Json file, so that the project can be opened directly in Che with appropriate commands. This might also be an alternate solution to do light changes. Since the last releases, Che has basic Ceylon support with syntax coloring. |
@davidfestal I believe it is possible to run locally via |
Local debugging might be hard in the given case, if we use the Che SA token. In this case I assume remote debugging (as in Java) should work. However, in the overall design of the maintainer, there is the ability to pass a given namespace + token + OS token to the request or through environment variables. So in this case, you would be able to run the endpoint locally and point to a remote prod-preview Che / OS namespace. Of course this would require that you would still have edit rights on your Che namespace. |
@davidfestal could you please clarify how exactly the project should be imported ? after installing plugins I do not see dedicated wizard for importing ceylon projects |
the maintainer is already an Eclipse project with the Ceylon nature, so just import it as |
Partial PR here: #26 |
Need to add endpoint for cleanup workspaces that have been running for more than fixed period of time. Basically, endpoint should be able to get all the running workspace pods in the user namespace and delete all openshift resources related to the workspace (
oc delete all -l che.workspace_id
) if workspace pod is running for more than fixed period of time (by default 1 day, but it would be great to make it configurable via parameter). The only obligatory parameter would beidentity_id
passed viaX-Identity-Id
header.oso-proxy
is going to be used asmasterUrl
and with Che SA Token [1] for all openshift related operations.[1] https://github.com/fabric8-services/che-tenant-maintainer/blob/master/source/io/fabric8/tenant/che/migration/namespace/cheServiceAccountToggle.ceylon#L73
The text was updated successfully, but these errors were encountered: