Hi,
This has probably been brought up in previous comments, but I feel like it would be very advantageous for Nuclei if there was support for nested templates.
My idea would be that instead of specifying a request, a user would pass a template/txt file and path (within the requests). As such, our current template would run with the execution requests of the specified template and make life much easier for those with authentication mechanisms, subsequent calls from one API to another, etc.
Nowadays, I feel like I have very duplicated code which, in the event that those credentials change, I'll have to change every single template. Passing those requests via a template, or even a txt file, would make life much simpler.
#Support for nested templates
granite bison
Okay, I've seen that this is allowed via workflows (shared execution context), but is there any way to do so inside the template and not the workflow?
frozen monolith
workflows are meant to be use for this purpose only, for example you can 1 template for login and all other templates for post login checks!
in that way you can keep extending the new checks via template and not to worry about login which is managed via root template.
is there is anything different or specific you wanted to achieve if done via template itself? with workflows it's more manageable / extendable but wanted to understand other reasons if one wanted to do in same template only?
granite bison
Not really. After further consideration, this fits our needs perfectly
May I ask when was this feature implemented, in which version of Nuclei? Or was it supported all along?
And also, when is Nuclei Cloud going public? We'd like to explore it further 😁
frozen monolith
workflows were supported from start, session and context sharing in workflows were added since nuclei v2.7.8 - https://github.com/projectdiscovery/nuclei/releases/tag/v2.7.8