Switch to the public tenant when enqueueing

[bfcoder]

At least in the case of Que, jobs will only be worked when on the public tenant.

This makes it so jobs are enqueued on the public tenant, then switched to the current tenant when worked.

[bfcoder]

As this gem appears to be dead, I have released another gem from a fork of this one: https://rubygems.org/gems/apartment-activejob-que

I have only verified this works with Que. I probably works with others as well.

[mikecmpbll]

i could just be being dense but i don't understand what the goal is here? the diff appear to be doing two things which require explanation as to why:

1. recording the current tenant in initialize, as opposed to serialize
2. switching to public tenant during enqueue

in looking at active job while reviewing this it seems like better practice would be to utilise around_perform anyways.

[bfcoder]

I suppose recording the current tenant could be kept in the serialize.

But the switching to public tenant must happen during the enqueue. At least in the case of que, jobs are only worked from the public tenant. So if you don't switch to the public tenant, your jobs will just sit there, never getting worked.

[mikecmpbll]

right, i get it. this is typically achieved by adding the job table to your apartment excluded models. does que use activerecord?

[bfcoder]

It does use activerecord but as far as I can tell it doesn't have a model you can place into the config.excluded_models.

[mikecmpbll]

okay. well, i don't think that forcing jobs to be enqueued on the public tenant will be appropriate for all users of apartment-activejob. there might be people who have per-tenant job queues.

[bfcoder]

Ok, that makes sense. I have the gem for those that use Que then. Thanks for your input!