Fix CUR 2.0 query: remove invalid column#119
Closed
Alexanderamiri wants to merge 1 commit into
Closed
Conversation
line_item_resource_id does not exist in the CUR 2.0 schema. In CUR 2.0 resource information is embedded in resource_tags when INCLUDE_RESOURCES is TRUE. This column was causing every CI apply to fail with "ValidationException: Invalid QueryStatement".
Terraform Plan🚧 Changes detected — Plan: 0 to add, 1 to change, 0 to destroy. Plan outputLLM ReviewRisk: 🟢 LOW Routine update to Cost and Usage Report (CUR) export query statement with no resource creation, destruction, or security changes.
|
Member
Author
|
Closing — the CUR export is already in state and working (HEALTHY). The error was from older CI runs. Recent runs on main all pass successfully. |
This file contains hidden or 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
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.
Summary
Removes
line_item_resource_idfrom the CUR 2.0 Data Exports query. This column exists in CUR 1.0 but not in CUR 2.0. In CUR 2.0, resource information is in theresource_tagscolumn whenINCLUDE_RESOURCES=TRUE.This has been causing every CI apply to fail with
ValidationException: Invalid QueryStatementsince the cost-analytics module was added.Test plan
Invalid QueryStatementerror