Skip to content
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

ODC-7720: Add dev perspective nav options to admin perspective #14588

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

vikram-raj
Copy link
Member

Story: https://issues.redhat.com/browse/ODC-7720

Descriptions:

  • Add Software Catalog nav option under the Home section in the Admin perspective
  • Add Helm nav option below Operators option in the Admin perspective
  • Add Functions nav option under the Serverlesssection in the Admin perspective
image
ODC-7720.mov

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 5, 2024

@vikram-raj: This pull request references ODC-7720 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

Story: https://issues.redhat.com/browse/ODC-7720

Descriptions:

  • Add Software Catalog nav option under the Home section in the Admin perspective
  • Add Helm nav option below Operators option in the Admin perspective
  • Add Functions nav option under the Serverlesssection in the Admin perspective
image
ODC-7720.mov

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 5, 2024
@openshift-ci openshift-ci bot added the component/core Related to console core functionality label Dec 5, 2024
Copy link
Contributor

openshift-ci bot commented Dec 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vikram-raj

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added component/dev-console Related to dev-console approved Indicates a PR has been approved by an approver from all required OWNERS files. component/helm Related to helm-plugin component/knative Related to knative-plugin kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated labels Dec 5, 2024
@vikram-raj
Copy link
Member Author

cc: @jhadvig @spadgett

@spadgett
Copy link
Member

spadgett commented Dec 5, 2024

cc @kevinhatchoua @itsptk

"href": "/topology",
"namespaced": true,
"dataAttributes": {
"data-quickstart-id": "qs-nav-topology",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes me realize that we should look at the quick starts to see what changes are needed for the combined perspective. We should track that as a story under the convergence epic.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure I will create a story for a quick start under epic ODC-7716

Copy link
Member

@spadgett spadgett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @vikram-raj 👍

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this isn't a lot of code, is there a reason we can't reuse the dev console list page here and for helm repositories? Are there not corresponding pages on the dev side?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a list page for this and using the same, I need to create this component as in dev perspective Helm page is tabbed view and the list page component does not contain a title, create button and Namespace selector.


const PageContents: React.FC<PageContentsProps> = ({ namespace }) => {
const { t } = useTranslation();
return namespace ? (
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should support showing releases in all namespaces (for users with authority) rather than falling back to the project list in the admin/converged perspective.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, I will update it. As an Admin perspective do support All namespaces.


const PageContents: React.FC<PageContentsProps> = ({ namespace }) => {
const { t } = useTranslation();
return namespace ? (
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Support an all namespaces list?

"id": "software-catalog",
"perspective": "admin",
"section": "home",
"name": "%devconsole~Software Catalog%",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry that this will be confused with OperatorHub, although I know this is in @kevinhatchoua's mock. This is the +Add page on the dev side, correct? I also worry that we'll have different labels in the admin and dev perspectives when they're both enabled.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it is not a +Add page. It is a Catalog page showing all the catalogs of 'Builder Images, DevFiles, Templates, Event Sources`, etc. We should have the same labels in both perspectives, as there is no difference in content. Software Catalog in Admin and Developer Catalog in the Dev perspective.

Copy link
Contributor

@lokanandaprabhu lokanandaprabhu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On creating of serverless function, user is redirected to workloads tab in Project details page.

Screen.Recording.2024-12-09.at.1.53.51.PM.mov

@vikram-raj
Copy link
Member Author

vikram-raj commented Dec 9, 2024

On creating of serverless function, user is redirected to workloads tab in Project details page.

It was an expected behavior as that's a topology page in the admin perspective. But now we have a Topology page in admin perspective we should redirect the user to that page. I will update it.

Copy link
Contributor

@lokanandaprabhu lokanandaprabhu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I am in Helm release or repositories page and onClick of Helm release or repository, select item in the left navigation menu is not proper.

Screen.Recording.2024-12-10.at.11.49.22.AM.mov

Developer catalog is replaced as Software catalog in navigation menu and page title but if I select a catalog type, breadcrumbs is still mentioned as developer catalog and in the highlighted description also. is this fine? or else can we keep in all the places as either Software catalog or Developer catalog?

Screen.Recording.2024-12-10.at.11.53.42.AM.mov

@openshift-ci openshift-ci bot added the component/shared Related to console-shared label Dec 10, 2024
Copy link
Contributor

openshift-ci bot commented Dec 10, 2024

@vikram-raj: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 91705b7 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

Copy link
Contributor

@lokanandaprabhu lokanandaprabhu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For Helm repository details page, if it is Helm chart repository, breadcrumbs is redirecting to Helm Chart Repositories list page and if it is PHCR, breadcrumbs is redirecting to Project Helm Chart Repositories list page unlike the behaviour in existing design where breadcrumbs redirecting to Repositories list page irrespective of whether it is HCR or PHCR.

----New design---

Screen.Recording.2024-12-11.at.11.41.26.AM.mov

---Old design----

Screen.Recording.2024-12-11.at.11.46.03.AM.mov

@vikram-raj
Copy link
Member Author

@lokanandaprabhu I have fixed the breadcrumb link in the dev perspective. And I asked UX whether we can expose the HCR and PHCR directly as nav items instead of combining both in the single list page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. component/core Related to console core functionality component/dev-console Related to dev-console component/helm Related to helm-plugin component/knative Related to knative-plugin component/shared Related to console-shared jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants