[AC-144] Worker Cron Process Design Doc #226
Conversation
|
|
||
| These can be exposed either by using the `AppSettingVariable__NestedKey=VALUE` accessor pattern to expose the values to the container. | ||
|
|
||
| The `ClientId` and `ClientSecret` values will need to be retrieved from upon instance creation. |
There was a problem hiding this comment.
Note: there are two different sets of credentials:
- For either worker to access Admin API
- For Health Check to access ODS/API
Thes second set can be retrieved at runtime from Admin API. App settings or env var will need to provide the Admin API credentials to go along with the AccessTokenUrl.
| COPY --from=build /app . | ||
|
|
||
| # Execute the app via chron | ||
| CMD ["cron", "-f"] |
There was a problem hiding this comment.
How will the sys admin adjust the schedule?
There was a problem hiding this comment.
There is a local crontab file that will be included in the docker image when building image from source. This allows you to set the schedule, log file, and command to be executed.
We can further investigate parameterizing this particular part of the string so that users can configure at runtime.
There was a problem hiding this comment.
Since this is a design doc, I'm good with that. Please create a follow-up ticket for implementation, and include a note about needing to parametrize the schedule.
Creates a Worker Cron Process Design Doc from SPIKE AC-144.
This provides the research and recommendations needed to setup the Health Check and Instance workers on a cron schedule using Docker.
Proof of concept:
Ed-Fi-Alliance-OSS/Ed-Fi-Admin-Console-Health-Check-Worker-Process#17