-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot create a factory from repository (without devfile) that has uppercase characters in name #21338
Comments
Suggested behaviour change is that the factory / devworkspace engine will sanitize the input GH repo name to make it compliant with OCP naming rules. |
Also fails in dogfood cluster:
|
Also this bug can be reproduced if customer devfile has ver. 1.0 and metadata with name in uppercase, e.g.
In this case we'll get the same error. |
@SkorikSergey what happens with accented characters? Do we sanitize those already? Or break when French or Spanish or Arabic characters are used? |
@nickboldt It is not possible to create repo with Arabic characters. And also with characters like ä, ö, ü. |
@l0rd wdyt should the fix be part of 3.0 ? |
This is not a blocker because it's a corner case: there is no devfile, the repo name has uppercase letters. But if it's an easy fix and there is no risk to postpone the release let's include that. |
Fixed in eclipse-che/che-dashboard#527 |
Describe the bug
Cannot create a factory from repository(without devfile) that has uppercase characters in name.
There are restrictions:
Unable to create devworkspace: DevWorkspace.workspace.devfile.io "TestRepo" is invalid: metadata.name: Invalid value: "TestRepo": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Che version
other (please specify in additional context)
Steps to reproduce
Expected behavior
Workspace created and started successfully.
Suggested behaviour change is that the factory / devworkspace engine will sanitize the input GH repo name to make it compliant with OCP naming rules.
Runtime
OpenShift
Screenshots
Installation method
OperatorHub
Environment
Linux
Eclipse Che Logs
No response
Additional context
Eclipse Che 7.47.0
The text was updated successfully, but these errors were encountered: