Secret Injector plugin
The Secret Injector plugin adds a secret to the request that the upstream receives, as a header or a query parameter. The data plane fetches the secret from a vault on every request, so secret values never appear in the plugin configuration. The plugin can also remove a header or query parameter that the client sent. Secret Injector is a Preview plugin, so the data plane must allow Preview plugins.
Where it runs
On LLM routes, a header that the connection’s own credential writes overwrites an injected header of the same name.
Configuration
The changes to make, in order. Must not be empty.
header or query.
The header or query parameter name.
set replaces any value that the client sent. add keeps the client’s value and adds another. delete removes the header or parameter, and needs no source.
The vault that holds the secret. Required for set and add.
The reference to the secret in the vault. Required for set and add.
The field to read from a structured secret.
The secret version to read.
A template that must contain {{secret}}, for example Bearer {{secret}}.
What to do when the secret can’t be read. fail breaks the plugin. With the default fail_closed, the request ends with 502. skip leaves out this injection and applies the rest.
An injection that contains the secret itself, in a value, secret, or secret_ref field, is rejected. An instance with an invalid configuration never runs, and every request that it applies to gets 502.

