feat: add cron orchestration for argo workflows#1422
Conversation
|
In the When commanding: We where able to know that our code compiled successfully, the DI container initialized ("Invalid or no value was provided for the DEPENDENCY_CONFIG"), the job tried to run. |
|
✅ Created |
Scott-James-Hurley
left a comment
There was a problem hiding this comment.
Is this a proof of concept or something intended to be merged?
| RUN cd apps/backend && npm run build | ||
|
|
||
| # Set working directory to backend | ||
| WORKDIR /app/apps/backend |
There was a problem hiding this comment.
Couldn't this be moved up to when you start running backend scripts?
| ); | ||
|
|
||
| await checkAllCallsEndedJob.functionToRun(callDataSource); | ||
| console.log('Job completed successfully'); |
There was a problem hiding this comment.
I think we probably want to use the user office logger instead of console log.
|
This is a POC. |
|
This is to not be merged in, However there are file that are vital to be able to use Argo-CD for us. Such as the entrypoint scripts that will let argo run jobs based on the cron-wrokflow yamls. The recommendation made by Scott regarding the logging and the |
|
Reopening this pr to test this branch on dev cluster |
Description
This is for this epic with a stfc cron orchestration service: UserOfficeProject/issue-tracker#1540
This will close this sub-issue: UserOfficeProject/issue-tracker#1552
This is to demo the use of argo-workflow with our own services to schedule in CRON the asyncJobs that
Motivation and Context
How Has This Been Tested
Fixes
Changes
Depends on
Tests included/Docs Updated?