Feature Request: Per-user environment variable settings in Eclipse Che GUI

[mikoto2000]

Is your enhancement related to a problem? Please describe

The devfile.yaml-based environment configuration is convenient, but some configuration values differ for each user.
Example:

• API keys for LLMs or other external APIs

Currently, applying these values to a workspace requires directly editing the devfile.yaml or manually setting them after login.

Describe the solution you'd like

I would like to request support for per-user environment variable settings.

If users could configure these environment variables via the Eclipse Che GUI and have them automatically applied to all workspaces they create, operations would be simplified.

Requested feature:

• Allow users to set and update environment variables via the Eclipse Che GUI. The configured and updated environment variables should be applied to all workspaces created by that user.

Describe alternatives you've considered

No response

Additional context

No response

[tolusha]

@mikoto2000

Hello.
I believe currently it can be achieved by creating a CM by a user and mounting into a user workspace
https://eclipse.dev/che/docs/stable/end-user-guide/mounting-configmaps/

[RomanNikitenko]

I set dashboard area and moved issue to the Team A backlog,
@mikoto2000 please just close the issue if the option from the previous comment works for you
thanks in advance!

[mikoto2000]

@tolusha

Thank you for your comment.

I tried this with Red Hat Dev Spaces, and by creating a ConfigMap in the administration console, I was able to create user-defined environment variables. For my personal use in Red Hat Dev Spaces, this seems sufficient.

However, it would be difficult for regular users to work with the administration console or kubectl, so I would still prefer to configure this through the dashboard GUI.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.