Open 6543 opened 1 year ago
currently the whole workflow config for the backend is stored in the queue.
This includes the secrets!
We should inject them at the server if an agent do pull that workflow out of the queue instead. So we dont have to worry about leaking via e.g. redis.
This also allow to e.g. let an workflow alter secrets before the next workflow fetch it ... and so on
first we have to move the logic that we store the complete backend config of a workflow in queue ... :/
NOTE: also with #3723 we might consider to do so for them too ...
currently the whole workflow config for the backend is stored in the queue.
This includes the secrets!
We should inject them at the server if an agent do pull that workflow out of the queue instead. So we dont have to worry about leaking via e.g. redis.
This also allow to e.g. let an workflow alter secrets before the next workflow fetch it ... and so on