token mandatory? #490
Labels
Comments
|
ahh, ok. This is my fault. I was not thinking correctly here. I will make it optional and make a new release, sorry for the mistake. |
manast
added a commit
that referenced
this issue
Apr 22, 2021
github-actions bot
pushed a commit
that referenced
this issue
Apr 22, 2021
## [1.20.1](v1.20.0...v1.20.1) (2021-04-22) ### Bug Fixes * **worker:** make token optional in processor function fixes [#490](#490) ([3940bd7](3940bd7))
|
🎉 This issue has been resolved in version 1.20.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
@manast wow, didnt expect this to be fixed. I was more wondering what the use-case for this token is? So one can pass "secret" information to a job? |
|
We are working on a use case where you can move the job to a different state from within the processor, and for that you need the token of that worker. But this is optional and will be explained in the documentation when it is ready. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1.6.0 broke our system as we now need to pass a mandatory token. I saw the discussion in #484 where the token was originally optional but @roggervalf suggested it shall be mandatory.
There is no reference to an issue or any detail for what this token could/shall be used for. It seems totally useless. Anyone care to elaborate what the idea behind it is?
The text was updated successfully, but these errors were encountered: