Async mode: synchronization always leads to "not provisioned (verified)", even if it should be provisioned

oveits / ProvisioningEngine

Ruby on Rails based ProvisioningEngine Frontend for provisioning of legacy systems via Apache Camel Backend (SOAP/XML+SPML+File import)

3 stars 6 forks source link

Async mode: synchronization always leads to "not provisioned (verified)", even if it should be provisioned #16

Closed oveits closed 8 years ago

oveits commented 8 years ago

The problem does not occur in sync mode. If we provision a customer and then press the Synchronize button, we receive "not provisioned (verified)". In this case, it should return "provisioned".

oveits commented 8 years ago

The problem seems to be that the static variable @@provisioned is not persistent across Delayed Jobs. If a new job is started, @@provisioned is nil.

oveits commented 8 years ago

Ideas:

save @@provisioned as a application global variable in the database
- :+1: I need a solution for global application variables anyway, e.g. for simulation mode, async mode. This could be the first use case.