Currently, the devchat API allows controlling the visibility of parameters in the supported model list through environment variables, with support only for a 'disable' parameter. For private deployments, an 'enable' parameter would be considerably more convenient.
In the context of private deployments, the requirement often is to expose a limited list of models while keeping the majority disabled. Thus, adopting an 'enable' approach for parameter visibility would greatly enhance usability and control over what is exposed.
Suggestion:
Introduce an 'enable' parameter that functions opposite to the current 'disable' parameter. This change would allow administrators of private deployments to specify exactly which models should be visible, simplifying the configuration process when only a select few models are intended for exposure.
Currently, the devchat API allows controlling the visibility of parameters in the supported model list through environment variables, with support only for a 'disable' parameter. For private deployments, an 'enable' parameter would be considerably more convenient.
In the context of private deployments, the requirement often is to expose a limited list of models while keeping the majority disabled. Thus, adopting an 'enable' approach for parameter visibility would greatly enhance usability and control over what is exposed.
Suggestion: Introduce an 'enable' parameter that functions opposite to the current 'disable' parameter. This change would allow administrators of private deployments to specify exactly which models should be visible, simplifying the configuration process when only a select few models are intended for exposure.