Bugfix/all variables injected when function has no variables

[ohasi]

Fix bug where function decorated as task receives all variables that are available to the task causing an unexpected keyword argument error. Referenced in #337.

The bug originates from the zeebe grpc API for ActivateJobs. If no variables are passed to fetchVariable , it fetches all available variables.

Changes

• Add a include_variables flag to private function _create_job_from_raw_job. If flag is set to False, retrieved variables will be ignored. The function is called in one place, which now calls it with bool(variables_to_fetch) as the flag's value. None or an empty list will cause no variables to be injected to the Job object, so they will never end up getting passed to the function.

API Updates

New Features (required)

• Support for functions with no arguments as task functions

Checklist

• [x] Unit tests
• [x] Documentation

References

ActivateJobs API

Fixes #337

[CLAassistant]

All committers have signed the CLA.

[JonatanMartens]

Looks good, but please add a simple unit test so that this bug doesn't reproduce.

[ohasi]

Looks good, but please add a simple unit test so that this bug doesn't reproduce.

Done. Something to have in mind that someone mentioned to me - this pr will remove the ability to intentionally get all parameters by setting the variables_to_fetch to [] or None. I don't think that's a problem or intended functionality, but just making sure

[ohasi]

Waiting for re-review :)

[dimastbk]

fixed in #404