SWATCH-1730: Refactor swatch-tally-hourly Job to use curl and internal endpoint #2545
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 issue: SWATCH-1730
Description
For all cronjobs defined in clowdapps, we should migrate to using k8s cronjobs w/ curl against internal endpoints.
Testing
Confirm that the endpoint is executed hourly.
Alternatively, you can deploy the application and overwrite the CAPTURE_HOURLY_SNAPSHOT_SCHEDULE environment property with
CAPTURE_HOURLY_SNAPSHOT_SCHEDULE=*/5 * * * *
(every 5 min).Another option is to directly alter the CronJob resource that is generated when installing the Clowd app. The CronJob to modify is named "swatch-tally-hourly".
Then, in the logs of the job created, you should see:
And in the logs of the swatch tally service:
So, the call was made and we confirmed that the service processed it.