Is your feature request related to a problem? Please describe.
I'm frustrated because while PassariGuard now supports adding multiple custom configuration templates for the same client type, it only allows setting one of them as the default. There is currently no way to expose these multiple configuration variants as separate selectable options on the subscription page for manual requests.
Describe the solution you'd like
I would like the subscription page to fully support these multiple templates. When a client type has multiple custom configurations/templates available, all of them should be displayed as individual options on the subscription generation page. This will allow users to manually select and download the specific configuration variant (e.g., Rule-based or Global) they need.
Describe alternatives you've considered
Currently, I have to constantly change which template is set as the "default" on the backend depending on what the user needs, or users have to manually modify the configuration file after downloading it, both of which are very inconvenient.
Additional context
Since the backend already supports multiple templates, bringing these options to the subscription frontend would complete the workflow and make the multi-template feature truly useful for end users.
Is your feature request related to a problem? Please describe.
I'm frustrated because while PassariGuard now supports adding multiple custom configuration templates for the same client type, it only allows setting one of them as the default. There is currently no way to expose these multiple configuration variants as separate selectable options on the subscription page for manual requests.
Describe the solution you'd like
I would like the subscription page to fully support these multiple templates. When a client type has multiple custom configurations/templates available, all of them should be displayed as individual options on the subscription generation page. This will allow users to manually select and download the specific configuration variant (e.g., Rule-based or Global) they need.
Describe alternatives you've considered
Currently, I have to constantly change which template is set as the "default" on the backend depending on what the user needs, or users have to manually modify the configuration file after downloading it, both of which are very inconvenient.
Additional context
Since the backend already supports multiple templates, bringing these options to the subscription frontend would complete the workflow and make the multi-template feature truly useful for end users.