-
Bug
-
Resolution: Not a Bug
-
Major
-
3.5.0.GA
-
Team A: Dashboard, devfile and plugin registries, open-vsx, operator + chectl/dsc, devfile-converter, configbump + traefik, image-puller, server, gateway, authentication, try-in-web-ide action, telemetry, Team B: DevWorkspace + Operator, Web Terminal + Operator, editors/IDEs + built-in vscode extensions, Universal Developer Image, machine-exec, dev environment config
-
False
-
None
-
False
-
-
Description of problem:
We have setup Gitlab Oauth token and due to the 2 hr limit, we would like users to be able to use personal access token's which wont expire.
Following this: `https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.5/html/user_guide/using-credentials-and-configurations-in-workspaces#using-a-git-provider-access-token`
in the verification step, states `Start a new workspace by using the URL of a remote Git repository that the Git provider hosts.`
When I attempt to do this with a gitlab URL, it seems to delete the personal access token secret. rather than use it.
Prerequisites (if any, like setup, operators/versions):
- RedHat Openshift dev spaces 3.5
- Devworkspace operator 0.19.1
- Gitlab Oauth setup with devspaces
Steps to Reproduce
- create a new personal-access-token following this `https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.5/html/user_guide/using-credentials-and-configurations-in-workspaces#using-a-git-provider-access-token`
- try to create a new workspace using the git repository from the git provider
Actual results:
- Personal access token secret deleted
- uses the gitlab oauth token
Expected results:
- personal access token initiated and installed
- `devworkspace-merged-git-credentials` are updated and using personal access token