-
Notifications
You must be signed in to change notification settings - Fork 61
Finalize workspace -> devWorkspace renaming #322
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
Conversation
Skipping CI for Draft Pull Request. |
// WorkspaceIDLabel is label key to store workspace identifier | ||
WorkspaceIDLabel = "controller.devfile.io/workspace_id" | ||
// DevWorkspaceIDLabel is label key to store workspace identifier | ||
DevWorkspaceIDLabel = "controller.devfile.io/devworkspace_id" |
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.
I think id
would be enough
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.
it's the time to make this label shorter if we wish, but I don't think we win anything with such change, just make things less clearer.
It would be clearer if it would be devworkspace.devfile.io/name
but it's controller.devfile.io/
group, and just name is not clear IMHO
Also this label is propagated to all devworkspace related stuff, pod, service, route.... It may be not clear enough to see controller.devfile.io/name label.
8d23697
to
0ba737b
Compare
332afe2
to
32ce88a
Compare
WorkspaceId string `json:"workspaceId"` | ||
// Class of the routing: this drives which Workspace Routing controller will manage this routing | ||
// Id for the DevWorkspace being routed | ||
DevWorkspaceId string `json:"devWorkspaceId"` |
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.
devworkspaceId vs devWorkspaceId
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.
Agreed on DevWorkspaceId as go field, but json version is devworkspaceId
3a2bc2f
to
6ede7d4
Compare
736908c
to
9ad307d
Compare
9ad307d
to
d690dc5
Compare
/test v5-devworkspaces-operator-e2e |
1 similar comment
/test v5-devworkspaces-operator-e2e |
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. Tested updating from main to this PR (manually) and saw no issues except from some strangeness that I think was my cluster rather than the operator.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amisevsk, sleshchenko The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
d690dc5
to
47dbfb6
Compare
New changes are detected. LGTM label has been removed. |
Tested failed because I forget to rename |
Found a bug. Deployment must be recreated if selector is changed.
|
47dbfb6
to
f84785f
Compare
f84785f
to
a4659ef
Compare
I tested all changed components together: DWO, DWCO, Che Theia, Che Machine Exec, Che Dashboard and it seems to work |
/test v5-devworkspaces-operator-e2e |
What does this PR do?
This PR is supposed to finalize workspace -> devWorkspace renaming but it does not do it fully.
What issues does this PR fix or reference?
It's for #321
Che Machine exec PR eclipse-che/che-machine-exec#138
Is it tested? How?
not yet.