Page MenuHomeSoftware Heritage

Allow to override celery config file name via the SWH_CONFIG_FILENAME env var
ClosedPublic

Authored by douardda on Fri, Feb 1, 5:00 PM.

Details

Summary

this will take precedence over the implicit config file scheme. The expected
config file given via the environment variable is expected to have a
[celery] section which will be used as config for the Celery app created
in swh.scheduler.celery_backend.config.

Related to T1410 and T826.

Diff Detail

Repository
rDSCH Scheduling utilities
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

douardda created this revision.Fri, Feb 1, 5:00 PM
ardumont accepted this revision.Fri, Feb 1, 6:42 PM
ardumont added a subscriber: ardumont.
ardumont added inline comments.
swh/scheduler/celery_backend/config.py
245

i guess we'll see what that changes ;)

This revision is now accepted and ready to land.Fri, Feb 1, 6:42 PM
douardda marked an inline comment as done.Mon, Feb 4, 11:23 AM
douardda added inline comments.
swh/scheduler/celery_backend/config.py
245

In fact, with the recent modifications in config file handling, this is a noop, the 'task_soft_time_limit' from CONFIG is already passed to the celery app.

douardda updated this revision to Diff 3398.Wed, Feb 6, 10:26 AM

rebased ans small fix

This revision was automatically updated to reflect the committed changes.