one expiration task per provider type #5432
Draft
+72
−61
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-####
Description
This change will:
cascade_delete
to remove the expiredOCPUsageReportPeriod
instead of the Django delete methodTesting
http://localhost:8000/api/cost-management/v1/reports/aws/costs/?filter[time_scope_value]=-30
(see data for 2 months)
RETAIN_NUM_MONTHS=1
and restart koku-worker(set the
REDIS_HOST
so that the shell can reach Redis)Orchestrator
to trigger a deletion:See that each provider-type only appears once in the result list AND OCP is called last.
http://localhost:8000/api/cost-management/v1/reports/aws/costs/?filter[time_scope_value]=-30
Release Notes