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
Bug 1822112: include OpenShift Project as part of deployImage flow #5196
Bug 1822112: include OpenShift Project as part of deployImage flow #5196
Conversation
@invincibleJai: This pull request references Bugzilla bug 1822112, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@invincibleJai: This pull request references Bugzilla bug 1822112, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@@ -22,6 +22,7 @@ export interface ResourceDropdownFieldProps extends DropdownFieldProps { | |||
actionTitle: string; | |||
actionKey: string; | |||
}[]; | |||
appendItems?: object; |
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.
appendItems?: object; | |
appendItems?: { [key: string] : string }; |
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.
Done
@@ -66,6 +66,7 @@ interface ResourceDropdownProps { | |||
onLoad?: (items: { [key: string]: string }) => void; | |||
showBadge?: boolean; | |||
autocompleteFilter?: (strText: string, item: object) => boolean; | |||
appendItems?: object; |
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.
same as above
798c5d4
to
feddd90
Compare
onLoad?: (items: { [key: string]: string }) => void; | ||
showBadge?: boolean; | ||
autocompleteFilter?: (strText: string, item: object) => boolean; | ||
appendItems?: { [key: string]: string | React.ReactElement }; |
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.
can we could extract this as a ResourceDropdownItems
Type and use it in other places like onLoad for consistency
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.
Updated
feddd90
to
031e682
Compare
@karthikjeeyar i don |
Verified locally and it works fine with limited permissions as well |
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
Thanks @karthikjeeyar @sahil143 /assign @christianvogt |
}: ResourceDropdownProps, | ||
updateSelection: boolean, | ||
) => { | ||
const unsortedList = {}; | ||
let unsortedList = {}; |
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.
Can you not simply init the list upfront?
let unsortedList = {}; | |
const unsortedList = { ...appendItems }; |
_.keys(appendItems).forEach((key) => { | ||
if (!_.has(unsortedList, key)) { | ||
unsortedList = { ...unsortedList, ...{ [key]: appendItems[key] } }; | ||
} | ||
}); |
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.
Unnecessary if you init unsortedList
with appendItems
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.
Thanks , have updated
031e682
to
45f52a1
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: christianvogt, invincibleJai, karthikjeeyar, sahil143 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 |
@invincibleJai: All pull requests linked via external trackers have merged: openshift/console#5196. Bugzilla bug 1822112 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.4 |
@invincibleJai: #5196 failed to apply on top of branch "release-4.4":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes:
https://issues.redhat.com/browse/ODC-3523
Analysis / Root cause:
The "openshift" has been always there to provide templates and images, user can use those via CLI but can't fetch images in deploy image flow from DevConsole
Solution Description:
include OpenShift Project as part of deployImage flow irrespective of user-role
Screen shots / Gifs for design review:
Browser conformance: