cost insights: make change.ratio optional #5439
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey, I just made a Pull Request!
Makes
ChangeStatistic.ratio
optional.Reasoning: Often an entity can incur costs in one period but not in another - such as when a new service is started or decommissioned. This results in either the first or last sum of a change aggregation being zero and growth being technically infinite.
This PR makes
ChangeStatistic.ratio
optional. Where a ratio is omitted, growth is considered infinite and cost insights will use theChangeStatistic.amount
(which is required) to determine if growth is positive or negative and render the corresponding UI.Cost Overview Chart
Product Insights Card
Cost Growth Indicator omitted
Product Entity Table
Sorts infinite values
Zero percent growth means zero percent growth
✔️ Checklist
Signed-off-by
line in the message. (more info)