-
Notifications
You must be signed in to change notification settings - Fork 23
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
feat(ClusterRules): Add impacted to single Cluster page #366
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Just one note, the field is declared as optional in the API spec (https://github.com/RedHatInsights/insights-results-smart-proxy/blob/master/server/api/v2/openapi.json#L1229). I think it is an error, as it does not make sense to have a rule hit without a timestamp, but if it is possible, we should enhance the test to account for that.
I will try to clarify that.
After discussing, it might be the case for some old archives, so it might be worth to test for that scenario as well |
refactored the code
# [1.6.0](v1.5.5...v1.6.0) (2022-07-21) ### Features * **Single cluster page:** Add a new column Impacted ([#366](#366)) ([2362508](2362508))
🎉 This PR is included in version 1.6.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
# [1.6.0](v1.5.5...v1.6.0) (2022-07-21) ### Features * **Single cluster page:** Add a new column Impacted ([#366](#366)) ([2362508](2362508))
Added the impacted column component + state when the impacted data is not available + tests