-
Notifications
You must be signed in to change notification settings - Fork 230
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
Rework how resources are calculated #3238
Rework how resources are calculated #3238
Conversation
// "Ready" states are currently omitted | ||
if entry.State == "Ready" { | ||
continue | ||
} |
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.
When I mentioned in the description about perClusterState
being opinionated, this is one of the causes: Ready
resources are omitted from this view (and that forces the UI to use BundleDeployments
for displaying GitRepo resources BTW). If we wanted to change that, it would be as simple as removing these lines.
f06827f
to
4f0cde5
Compare
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.
Nice one, thanks! LGTM
Would we need to adapt UI for this ? |
@kkaempf no, no change is needed. It only changes how the info is calculated internally, while still producing the same result |
Refers to #3186
This PR concludes the work started on #3203 and #3209, by refactoring how the
status.resources
(and especiallyperClusterState
) are calculated.The goal of this refactor is to keep all the information accessible, while still producing the same opinionated representation. This will allow to later change the format in an easier way, or adding new fields from the same information (e.g.
PerClusterResources
).