Idea: CLI argument for template and maybe template-specific options.
Current behavior: Template file can be configured in the config.
Expected behavior: Change used template on the fly. This would be especially useful with a collection of templates for simple use cases.
Different templates for different scenarios and use cases could make this tool more powerful. In the end, all templates should keep it simple. But the example of AppSec could be a good case for a specific template.
All templates would have to adhere to the same format though, I guess. Template-specific sets of options would be even more powerful, but I'm not sure if TinyTemplate can even support that.
Idea: CLI argument for template and maybe template-specific options.
Current behavior: Template file can be configured in the config.
Expected behavior: Change used template on the fly. This would be especially useful with a collection of templates for simple use cases.
Different templates for different scenarios and use cases could make this tool more powerful. In the end, all templates should keep it simple. But the example of AppSec could be a good case for a specific template.
All templates would have to adhere to the same format though, I guess. Template-specific sets of options would be even more powerful, but I'm not sure if TinyTemplate can even support that.