[Feature Request] provide dedicated API to get all stored search templates (scripts)

[rursprung]

Is your feature request related to a problem? Please describe

as per the documentation the following is the only way to get a list of all stored search templates (scripts):

GET _cluster/state/metadata?pretty&filter_path=**.stored_scripts

Describe the solution you'd like

it'd be great if there'd be a more canonical path to get this. since you POST /_scripts/[script-id] to create a script it'd be nice if you could GET /_scripts to get a list of all of them and GET /_scripts/[script-id] to get a specific one.

Related component

Other

Describe alternatives you've considered

you can also just keep the current way of retrieving the stored scripts, but it's not an easy-to-remember path. but at least it's documented so you can always copy & paste it (after searching for it) when needed 🙂

Additional context

No response

[msfroh]

As @lukas-vlcek called out in Search Relevance Triage meeting, we do need to consider the security implications of such an API. (How does it differ from access control over cluster metadata as a whole? Can we limit access to some scripts but not others?)

[cwperks]

Can we limit access to some scripts but not others?

The security plugin doesn't have any existing mechanisms for that. This could be authorized similar to index templates where the security plugin treats it like a cluster permission. This would mean that a cluster admin can prevent someone from using the API, but if a user is authorized to use the API then they can see all stored scripts.

I like this feature proposal.