userCreated worker queue was receiving queue elements upon updating a user - this lead to a big bug where everyone who had their role changed from 'member' to 'learner' fired off workers.
We don't want to trigger workers on updates, only on creation / insert.
We don't care about filtering for 'learner' roles only, but rather want to fire off workers for any creation at all.
Solution: By removing the getAll token the filter for old_val now functions properly (is not null when updating, but is null when newly created) allowing us to only trigger workers when creating new users.
Fixes #201, #203
Overview
userCreated worker queue was receiving queue elements upon updating a user - this lead to a big bug where everyone who had their role changed from 'member' to 'learner' fired off workers.
Solution: By removing the
getAlltoken the filter forold_valnow functions properly (is not null when updating, but is null when newly created) allowing us to only trigger workers when creating new users.Data Model / DB Schema Changes
None
Environment / Configuration Changes
None
Notes