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

[backport v2.8.next1] User Retention Admin Interface #11312

Closed
github-actions bot opened this issue Jun 28, 2024 · 1 comment
Closed

[backport v2.8.next1] User Retention Admin Interface #11312

github-actions bot opened this issue Jun 28, 2024 · 1 comment
Assignees
Labels
kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Milestone

Comments

@github-actions
Copy link
Contributor

This is a backport issue for #11303, automatically created via GitHub Actions workflow initiated by @rak-phillip

Original issue body:

As a Rancher Admin, I want to configure global user retention settings so that I can define when a user will get deactivated or deleted from Rancher after a not logging in for a given duration.

Screenshots

Add a new button to the User Retention page

image

User Retention Form

Inputs disable without data

image

Form with data

image
@github-actions github-actions bot added kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None labels Jun 28, 2024
@github-actions github-actions bot added this to the v2.8.next1 milestone Jun 28, 2024
@yonasberhe23 yonasberhe23 self-assigned this Jul 26, 2024
@yonasberhe23
Copy link
Contributor

Tested in

  • v2.8-51052a73adcd6ea40cedcefbedc25e707cdb2f25-head
  • release-2.8 a38998e

Smoke tested in 2.8 as this was fully tested in 2.9.
Note: as noted in the original issue, there's an outstanding backend issue related to this feature rancher/rancher#46063

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Projects
None yet
Development

No branches or pull requests

3 participants