This PR adds a dropdown menu with all the namespaces in the cluster where user can choose proper namespace to start a pod in. This dropdown menu only displays if the request in default namespace (openshift-terminal). Chosen namespace is then used to initialize environment and is sent to the webterminal-proxy.
Example of form before first request:
When the request fails
*User must be able to read namespaces otherwise the list will be empty
Part of: https://github.com/operate-first/service-catalog/issues/213
Edit added functionality to input default namespace which will be used this configuration is optional and if not specified it uses openshift-terminal Example of usage:
Needs approval from an approver in each of these files:
- ~~[OWNERS](https://github.com/operate-first/service-catalog/blob/main/OWNERS)~~ [tumido]
Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
This PR adds a dropdown menu with all the namespaces in the cluster where user can choose proper namespace to start a pod in. This dropdown menu only displays if the request in default namespace (
openshift-terminal
). Chosen namespace is then used to initialize environment and is sent to thewebterminal-proxy
. Example of form before first request: When the request fails *User must be able to read namespaces otherwise the list will be empty Part of: https://github.com/operate-first/service-catalog/issues/213Edit added functionality to input default namespace which will be used this configuration is optional and if not specified it uses
openshift-terminal
Example of usage:Edit 2 Updated version now displays a modal instead of inlining select
Resolves https://github.com/operate-first/service-catalog/issues/213