Story #4553
Updated by bmbouter about 5 years ago
h2. Problem Plugin writers and users want to query tasks by data used as their RQ task parameters. For example, tasks that use base_version as an argument would be useful to query on later. h2. Solution Have RQ tasks store the keyword, value pairs in If you run a separate Table sync with some one time options (eg mirror), that foreign key relate to the Task model. Serialize these for the Task complete serialization. The attribute can be called <code>kwargs</code> that shows a list of <key, value> tuples. h2. Security We should have a decorators available for plugin writers to ensure this feature doesn't leak get recorded anywhere. This information it shouldn't. Specifically make a decorator called <code>no_kwargs_recording</code> that will disable the kwargs recording for a task. Additionally it is lost and probably should take a list of kwarg names that will specifically be not recorded. For example: <pre> no_kwargs_recording('password') def myfunc(username, password): pass </pre> This example would record stored somehow on the 'username' key and its value, but never the 'password' key. Task record.
.