Mario Loriedo

There is nothing particular to do if you use Eclipse Che definition of VS Code: - [machine-exec binary is copied in a volume](https://github.com/che-incubator/che-code/blob/main/build/scripts/entrypoint-init-container.sh#L17) - and [then executed](https://github.com/che-incubator/che-code/blob/main/build/scripts/entrypoint-volume.sh#L27) at workspace startup...

This is on hold until we start using JetBrians Gateway.

@parvathyvr I would update the table like that: | Type | Details | Action | | --- | --- | :--: | | Git Credential Store | [Secret](url) | :...

@sympatheticmoose agreed. I haven't found anything better though. "Add External Account" doesn't work for tools settings that doesn't involve an external service (settings or git settings for example)

@tolusha after discussion with @amisevsk @ibuziuk and @AObuchow we decided that it's time to remove Che from OperatorHub and leave Dev Spaces only. So both upstream Che and DevWorskpace upstream...

This should be fixed with devworkspace as workspace engine. I beleive that's a check that dashbord should do. Changing the area label accordingly and setting devworkspace STEP 3 as milestone....

After discussion at latest dw cabal we decided to remove this issue from the scope of milestone "DevWorkspace Integration - STEP3".

/remove-lifecycle stale

> If this functionality is no longer required, removing it could simplify the requirements Che has for developer containers. Beyond the simplification, we should avoid providing R/W access to `/etc/passwd`...

> we can expect the cluster to inject an appropriate entry into /etc/passwd on both Kubernetes and OpenShift On clusters where Pods don't run as arbitrary users (vanilla Kubernetes?) there...