[COST-3814] Azure subs processing start 2 days prior to source creation #4836
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-3814
Description
This change will make Azure subs processing start 2 days prior to source creation instead of 1. Azure processing requires the day of data to be "complete" and when a source is created, yesterdays data is unlikely to be completed as the export for today would have to have run already. Using 2 days will process data upon source creation instead of waiting an extra day.
Testing
Easiest testing is to create an AWS
SUBSDataExtractor()
and an AzureSUBSDataExtractor()
and see the different in time:make create-test-customer
make shell
datetime.datetime(2023, 12, 12, 0, 0, tzinfo=<UTC>)
:datetime.datetime(2023, 12, 13, 0, 0, tzinfo=<UTC>)
:Notes
...