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
{{ message }}
This repository has been archived by the owner on Apr 1, 2023. It is now read-only.
When I call perform_async on an encrypted worker it hits the branch in api.rb (379 is a print line I added) that anonymizes things:
This caused the value [encrypted data] to be encrypted and stored in redis. When the job is run, it appropriately decrypts the data and passes that literal string "[encrypted data]" to the method.
This plugin calls display_args which then calls down into the base implementation of display_args.
Making my jobs that need encryption bypass calling include Sidekiq::Status::Worker has fixed the issue for me.
I don't know the middleware stack well enough to know if there is a fix for this or the "solution" is simply not using status workers but I thought I should file something to help others out.
The text was updated successfully, but these errors were encountered:
Have you tried adjusting the order of the middleware? It's not guaranteed, but by flipping the order, they might be able to play nicely with each other.
When I call
perform_async
on an encrypted worker it hits the branch inapi.rb
(379 is a print line I added) that anonymizes things:This caused the value
[encrypted data]
to be encrypted and stored in redis. When the job is run, it appropriately decrypts the data and passes that literal string"[encrypted data]"
to the method.This plugin calls
display_args
which then calls down into the base implementation ofdisplay_args
.Making my jobs that need encryption bypass calling
include Sidekiq::Status::Worker
has fixed the issue for me.I don't know the middleware stack well enough to know if there is a fix for this or the "solution" is simply not using status workers but I thought I should file something to help others out.
The text was updated successfully, but these errors were encountered: