-
Notifications
You must be signed in to change notification settings - Fork 515
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
Nik/plugins #2619
Nik/plugins #2619
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Signed-off-by: Nik Willwerth <nwillwerth@kubecost.com>
Signed-off-by: Nik Willwerth <nwillwerth@kubecost.com>
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.
approving, but noting something that needs to be fixed
cc.BilledCost += other.BilledCost | ||
cc.ListCost += other.ListCost | ||
cc.ListUnitPrice += other.ListUnitPrice | ||
cc.UsageQuantity += other.UsageQuantity |
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.
the only major thing I see in this PR is that when adding, we should take the intersection of the string properties. so if one domain != another domain, then the result is the domain is an empty string, that more closely matches our existing logic
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 this goes into the working branch, I will fix this unless @nik-kc hits this before the merge
What does this PR change?
Does this PR relate to any other PRs?
How will this PR impact users?
Does this PR address any GitHub or Zendesk issues?
How was this PR tested?
Does this PR require changes to documentation?
Have you labeled this PR and its corresponding Issue as "next release" if it should be part of the next OpenCost release? If not, why not?