You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the moment, I am running two different approaches for delivering background jobs:
provision, delete/de-provision and read are performed via old style Provisioning.deliver method, which directly calls delayed_jobs.
synchronize is performed via new style GeneralJob.perform_later(...) method. The Provisioning model is used only for persistently saving the job to the database for later reference. Provisioning's deliver method is not called.
I need to find a one method fits all solution. Two possibilities:
A) Migrate old style to new style
B) change new style: e.g. call GeneralJob.perform_later within the Provisioning.deliver method (might be the better choice? This is to be discussed).
TODO:
Find best solution between A) and B) above.
Work on GeneralJob+Provisioning model cleaning topics like follows:
recording of the number of attempts in Provisioning model
link to delayed_job to be replaced by link to GeneralJob in Provisioning model.
The change is non-functional only with no impact on the service, so the prio could be set to low. However, it needs to be done in order to keep the code maintenable. Therefore, I raise it to normal prio.
The text was updated successfully, but these errors were encountered:
In the moment, I am running two different approaches for delivering background jobs:
I need to find a one method fits all solution. Two possibilities:
A) Migrate old style to new style
B) change new style: e.g. call GeneralJob.perform_later within the Provisioning.deliver method (might be the better choice? This is to be discussed).
TODO:
The change is non-functional only with no impact on the service, so the prio could be set to low. However, it needs to be done in order to keep the code maintenable. Therefore, I raise it to normal prio.
The text was updated successfully, but these errors were encountered: