FEATURE ASH-229: Add AWS Data Export COR suport #28
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
kristian-lesko
force-pushed
the
feature/ASH-229_cor_report
branch
from
2d5331b to
b6fde5f
Compare
kristian-lesko
force-pushed
the
feature/ASH-229_cor_report
branch
from
b6fde5f to
42c6a3f
Compare
nuginy
approved these changes
Sep 30, 2024
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.
Add support for AWS Data Exports, which are set to replace the legacy Cost and Usage Reports (CUR). Currently, the
Cost optimization recommendationstable format is supported.Relates to VerticeOne/terraform-aws-vertice-integration#50.