Originally Posted by kovidgoyal
No there isn't. recipes are designed to run non interactively. That's not to say that I could not add pre configured settings per recipe, but at the moment the only ones are username and password. You can ofcourse overload them to pass in other data.
I've considered overloading them, but then you have a recipe that the user gets confused about - he has to enter something into user/pass before the recipe will run.
I'd love a third option, like "recipe_data" that will appear when we set:
uses_recipe_data = True
and will populate with a default from the recipe, so the user can see the settings, but will store/overwrite the settings when modified by the user.
A simple dictionary of settings the recipe author wants to allow the user to set should be clear enough. The instructions for use can be provided in the displayed recipe description and the dictionary of settings:values could appear in front of them in a recipe_data window. If no action is taken to change them, they can remain as default set by the recipe author.