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

Provider success status that is "old" should not be green #8558

Closed
Fryguy opened this issue Dec 5, 2022 · 9 comments
Closed

Provider success status that is "old" should not be green #8558

Fryguy opened this issue Dec 5, 2022 · 9 comments
Assignees
Projects
Milestone

Comments

@Fryguy
Copy link
Member

Fryguy commented Dec 5, 2022

In #7709 (via PR #7719), we added showing the Last Refresh Status. One of the things we did was to show the status if it's "old", that is over some threshhold, even if successful.

Because it's presented as green everything looks ok, but the purpose of showing the old status, is that it's probably not ok. Given that it's not an error, I propose we present this as a warning with a warning icon and yellow/orange status (whichever is the more consistent color).

Here's an example of a provider that actually has a problem:

IA_IM__Cloud_Providers

@agrare @jeffibm Thoughts?

@agrare
Copy link
Member

agrare commented Dec 5, 2022

Agreed I thought we did say if it was "too long ago" it would be red but clearly not

@Fryguy
Copy link
Member Author

Fryguy commented Dec 5, 2022

A red "success" is weird though - that's why I was thinking ⚠️ with yellow.

@agrare
Copy link
Member

agrare commented Dec 5, 2022

Yeah or if it has been over N days we don't display the last status

@Fryguy
Copy link
Member Author

Fryguy commented Dec 5, 2022

@agrare
Copy link
Member

agrare commented Dec 5, 2022

Ah okay so if it is stale we show a notification, but not necessarily a warn/error notification.

@jeffibm
Copy link
Member

jeffibm commented Dec 12, 2022

@agrare, @Fryguy , should we change this to yellow warning?

@agrare
Copy link
Member

agrare commented Dec 12, 2022

@jeffibm yes a warning would be perfect in this scenario, not necessarily and error but something the user should look at

@jeffibm
Copy link
Member

jeffibm commented Dec 13, 2022

Fixes - #8571

@Fryguy
Copy link
Member Author

Fryguy commented Dec 20, 2022

Closed via #8571

@Fryguy Fryguy closed this as completed Dec 20, 2022
@Fryguy Fryguy added this to the Petrosian milestone Sep 14, 2023
@Fryguy Fryguy added this to Petrosian in Roadmap Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Roadmap
  
Petrosian
Development

No branches or pull requests

3 participants