[COST-5137] Run OCP on Cloud Summary after new processing flow #5276
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.
Jira Ticket
COST-5137
Description
This change will run OCP on Cloud summary after the new processing flow if both the
cost-management.backend.feature-cost-5129-ocp-cloud-processing
andcost-management.backend.feature-cost-5129-ocp-cloud-summary
unleash flags are enabled. It also updates thereport_data
masu endpoint to trigger the new processing/ocp on cloud summary task IF the unleash flags are on.Testing
cost-management.backend.feature-cost-5129-ocp-cloud-processing
in unleash, do not enable the summary flag.managed_aws_openshift_daily
cost-management.backend.feature-cost-5129-ocp-cloud-summary
./api/cost-management/v1/report_data/?schema=org1234567&provider_uuid=58c94173-027e-4ccf-a41e-5f2b169e09b5&start_date=2024-07-01
localhost:8080/ui
and searching forINSERT INTO hive.org1234567.aws_openshift_daily_resource_matched_temp
and select the first query and verify the FROM statement isFROM hive.org1234567.managed_aws_openshift_daily as aws
.Release Notes