-
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
factory will always use devfile generateName #14311
factory will always use devfile generateName #14311
Conversation
Signed-off-by: Michal Vala <mvala@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice way of fixing #13683!
It doesn't have to. The devfile naming is "fixed" later in the process. If you think it would be better, I'll modify it. |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
I stared like a few minutes and did not manage to find where it will be fixed later. |
Signed-off-by: Michal Vala <mvala@redhat.com>
you're right, it's not fixed later. I've missed that, twice :) Thanks for the catch. fixed |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
Results of automated E2E tests of Eclipse Che Multiuser on OCP: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ci-test |
Signed-off-by: Michal Vala mvala@redhat.com
What does this PR do?
Fixes possible workspace name collision when using factory with devfile. It takes
generateName
with precedence and convertsname
intogenerateName
, when onlyname
is defined. With this, we should always create uniquely named workspace that will have 5 random characters suffix.name
, it use it as generateName ->nameYYYYY
generateName
, it uses that ->generateNameYYYY
name
andgenerateName
, it usesgenerateName
->generateNameYYYY
(Y is random [0-9a-z] characted)
I've choosen to take
generateName
overname
here, because there is higher chance that it would generate nicer name. If you have other opinion, please comment.What issues does this PR fix or reference?
#13683
Release Notes
Docs PR