Skip to content

Conversation

@rancher-ui-project-bot
Copy link

@rancher-ui-project-bot rancher-ui-project-bot bot commented Dec 8, 2025

This is an automated request to port PR #16113 by @richard-cox

Original PR body:

Summary

Fixes #16114

Occurred changes and/or fixed issues

  • Short term fix
    • Fetch a capped amount of norman users. This is the same approach we use for bindings

Technical notes summary

  • Long term fix pending, which will be either...
    1. use new user resource which contains all of norman user functionality (no longer need to fetch secondary norman user resource). Blocked on backend
    2. use existing user resource and fetch norman user secondary resources per page

Areas or cases that should be tested

Setup

Either create 1001 users OR create at least 10 and apply the following lines to shell/plugins/steve/actions.js request action before const out = await makeRequest(this, opt, rootGetters);

if (!paginatedResult && opt.url === 'https://localhost:8005/v3/users') {
   opt.url += '?limit=5';
}

Validation

  • Users & Auth --> Users list
  • Open dev tools network tab
  • Refresh
    • After the request to /v3/users?me=true and EXCLUDING /v3/users?me=true there should be multiple request to /v3/users (EXCLUDING ). These will ensure all norman users are fetched
    • For every row in the users list (or a decent spread of) ensure the Delete action is visible in the action menu

Areas which could experience regressions

  • User detail page, in particular the action menu delete option

Screenshot/Video

image

Checklist

  • The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
  • The PR has a Milestone
  • The PR template has been filled out
  • The PR has been self reviewed
  • The PR has a reviewer assigned
  • The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
  • The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
  • The PR has been reviewed in terms of Accessibility
  • The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

…fix - Fetch a capped amount of norman users. This is the same approach we use for bindings - Long term fix. Either... 1. use new user resource which contains all of norman user functionality (no longer need to fetch secondary norman user resource). Blocked on backend 2. use existing user resource and fetch norman user secondary resources per page
Copy link
Member

@rak-phillip rak-phillip left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants