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

Warn users when creating a harvester cloud credentials that it will expire #11269

Closed
Tracked by #11256
richard-cox opened this issue Jun 20, 2024 · 3 comments · Fixed by #11313
Closed
Tracked by #11256

Warn users when creating a harvester cloud credentials that it will expire #11269

richard-cox opened this issue Jun 20, 2024 · 3 comments · Fixed by #11313
Assignees
Labels
kind/enhancement priority/0 QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@richard-cox
Copy link
Member

richard-cox commented Jun 20, 2024

  • When creating a harvester token warn users that the token will expire
  • Expiration date should be calculated and presented?
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jun 20, 2024
@richard-cox richard-cox added kind/enhancement and removed QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Jun 20, 2024
@richard-cox richard-cox added this to the v2.9.0 milestone Jun 20, 2024
@richard-cox richard-cox added priority/0 QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Jun 20, 2024
@momesgin
Copy link
Member

@richard-cox is this about displaying the warning only on this page?
/dashboard/c/_/manager/cloudCredential/create?type=harvester

Image

@richard-cox
Copy link
Member Author

/backport v2.8.next1

@richard-cox
Copy link
Member Author

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

Successfully merging a pull request may close this issue.

2 participants