Interfaces needed in Kubecost Asset and CloudCost item for mapping monitored to billed resources #1695
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
avrodrigues5
commented
Feb 16, 2023
avrodrigues5
force-pushed
the
avr/functions-for-clusterstatus
branch
2 times, most recently
from
3341764
to
189b24a
Compare
…or matching billed vs monitored resources Signed-off-by: Alan Rodrigues <alanr5691@yahoo.com>
… values Signed-off-by: Alan Rodrigues <alanr5691@yahoo.com>
avrodrigues5
force-pushed
the
avr/functions-for-clusterstatus
branch
from
55155b3
to
3cc7ce4
Compare
…roviders Signed-off-by: Alan Rodrigues <alanr5691@yahoo.com>
nikovacevic
approved these changes
Feb 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR change?
monitoring key with provider/account/providerID in both asset and cloud cost items and accumulate in cloudcostItemset
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?