Rotate a secret
Adds a new version. Egress proxies cache values for up to 60 seconds.
With allowedHosts, the secret’s allowed hosts are replaced in the
same call; without it they stay as they are. Owners and admins, or
unrestricted API keys (no scopes and no sandbox list).
Authorizations
Body
The hosts this secret may be sent to. Each entry is one of:
an exact host (api.github.com, that host only); *. and a domain
(*.github.com, any host under github.com but not github.com
itself, so list both when you need both); or * on its own, for any
host. Entries are bare host names: no scheme, port or path. A rule
that aims the secret at a host outside the list is refused with 403.
1 - 64 elementsResponse
The secret after the rotation, as the list shows it - the new version, its allowed hosts (the kept list when allowedHosts was left out) and its bindings, which carry on unchanged.
Where the secret is in use: one entry per host and header. A rule in
a sandbox's create request or network update is bound for that
sandbox alone (scope sandbox, scopeID the sandbox ID), so two
sandboxes with the same rule have two bindings. A rule in the team
egress settings or a template's policy is bound once (scope
tenant_default or template) and used by every sandbox under it.
A sandbox's own bindings are revoked when it ends (deleted, timed out
or failed) and drop out of this list; a paused sandbox keeps them.