Make external URL of exposed endpoints of the workspace available as environment variable of all the containers

Is your enhancement related to a problem? Please describe.

For some applications with multiple containers, sometimes the frontend need to access to the backend from the browser. (For instance a React Native frontend would typically do that. But there is no way to retrieve the external url of a exposed endpoint.

The workaround at the moment is to copy from my workspace root manually and set that to the frontend app (in react native, we change the file .env)

Describe the solution you’d like

For all exposed end point, add a env variable with the name of the end point. For instance, a endpoint

    endpoints:
      - name: 3000/tcp
        port: 3000

could be store as env variable 3000-TCP-EXTERNAL

[sunix]

Hello, This is important to have for cloud native apps that would need the browser components to talk to other components of the application. Setting p1.

[sleshchenko]

the endpoints urls should be already available in devworkspaces in the mount file. See https://github.com/devfile/devworkspace-operator/pull/318

But environment variables are still a valid idea and easier to use by apps.