Give multiple users access to a workspace

[mkyrilov]

Hello everyone,

I am busy integrating @eclipse-theiacloud/common into my own application, and I am using the following API to create a workspace:

TheiaCloud.Workspace.createWorkspace(
  {
    appId: 'APP_ID',
    appDefinition: 'APP_DEFINITION',
    user: '[email protected]',
    label: 'LABEL',
    serviceUrl: 'SERVICE_URL',
  },
  { accessToken: 'ACCESS_TOKEN' },
);

This operation is successful and I am able to launch the workspace by calling the following:

TheiaCloud.Session.startSession(
  {
     appId: 'APP_ID',
     user: '[email protected]',
     appDefinition: 'APP_DEFINITION',
     workspaceName: 'WORKSPACE_NAME', // obtained from the createWorkspace operation above
     serviceUrl: 'SERVICE_URL',
  },
  { accessToken: 'ACCESS_TOKEN' },
);

In the above, [email protected] is able to launch their workspace and everything works fine.

My question is, how would I specify that [email protected] should also have access to that same workspace?

[jfaltermeier]

Hi,

Currently, our focus has been on workspaces that are owned by users, and as such, we do not support sharing at the moment.

Regarding your use case, could you clarify whether you expect both users to be able to work on the workspace simultaneously?
Or are you envisioning a scenario where a workspace can be shared, but only one user can actively use it at any given time?

[mkyrilov]

Hello, we are envisioning something where more than one user can access the workspace simultaneously. It is basically for a team lead to be able to access the workspaces of all their team members, but not necessarily collaborate with them in real time.

We were able to make this work by modifying the *-emailconfig-* configmap which gets created along with the session. All we had to do was add more email addresses, and the proxy lets those users in. The problem is that the configmap is not a persisted object, as it disappears when the session is destroyed.

If it was possible to specify a list of users when creating a workspace, and the operator to write that list in the configmap, then this would fulfill our use case.