Save Secrets
PUT/secret-svc/secrets
Save secrets if authorized to do so
Request
- application/json
Body
required
Save Secret Request
Array [
]
secrets
object[]
Slugs of services/users who can change the deleters list
Slugs of services/users who can change the readers list
Slugs of services/users who can change the writers list
Slugs of services/users who can delete the secret
Whether the secret is encrypted
All secrets are encrypted before written to the DB.
This really only exists for write requests to know if the secret is already encrypted.
Ie: while most secret save [key] [value]
commands are probably not encrypted,
File based saves, eg. secret save secretA.yaml
are probably encrypted.
Id of the secret
Envar or slug-like key of the secret
Namespace of the secret
Slugs of services/users who can read the secret
Secret Value
Slugs of services/users who can modify the secret
Responses
- 200
- 401
- 500
Save Secret Response
- application/json
- Schema
- Example (from schema)
Schema
object
{}
Unauthorized
- application/json
- Schema
Schema
string
Internal Server Error
- application/json
- Schema
Schema
string