Closed oveits closed 8 years ago
Implementation idea: 1) add :synchronize as provision method or 2) generalize the provisioning tasks to general "tasks" or "tickets"
In order to decide between 1) and 2), I need to evaluate, which method is DRYer.
Implemented in https://github.com/oveits/ProvisioningEngine/commit/e697c3d30710b9048b233566d900b1bbf6a561fb (see this diff) like follows:
app/jobs
)provisioning = Provisioning.new(...).save
(otherwise it will be lost, once the job is finished)provisioning.deliver
(as I do it with provision/de-provision/read), I run it via job = GeneralJob.perform_later(self, "synchronizeSynchronously")
in app/models/provisioningobject.rb: synchronize
method. TODO:
Feature is implemented in https://github.com/oveits/ProvisioningEngine/commit/e697c3d30710b9048b233566d900b1bbf6a561fb. I will close the request. Implementation improvements will be handled in other request (e.g. issue #45).
All background jobs including the synchronization jobs should be visible in a tasks list. Today, only provision methods :create and :delete are seen.