Inspect a secret

{ "CreatedAt": "2016-11-05T01:20:17.327670065Z", "ID": "ktnbjxoalbkvbvedmg1urrz8h", "Spec": { "Driver": { "Name": "secret-bucket", "Options": { "OptionA": "value for driver option A", "OptionB": "value for driver option B" } }, "Labels": { "foo": "bar" }, "Name": "app-dev.crt" }, "UpdatedAt": "2016-11-05T01:20:17.327670065Z", "Version": { "Index": 11 } }

Responses

🟢200no error

application/json

Body

CreatedAt

string <dateTime>

optional

Example:

2017-07-20T13:55:28.678958722Z

string

optional

Example:

blt1owaxmitz71s9v5zh81zun

Spec

object (SecretSpec)

optional

Data

string

optional

Base64-url-safe-encoded (RFC 4648)
data to store as secret.

This field is only used to create a secret, and is not returned by
other endpoints.

Example:

Driver

object (Driver)

optional

Driver represents a driver (network, logging, secrets).

Labels

object

optional

User-defined key/value metadata.

Example:

{"com.example.some-label":"some-value","com.example.some-other-label":"some-other-value"}

Name

string

optional

User-defined name of the secret.

UpdatedAt

string <dateTime>

optional

Example:

2017-07-20T13:55:28.678958722Z

Version

object (ObjectVersion)

optional

The version number of the object such as node, service, etc. This is needed to avoid conflicting writes.
The client must send the version number along with the modified specification when updating these objects.
This approach ensures safe concurrency and determinism in that the change on the object
may not be applied if the version number has changed from the last read. In other words,
if two update requests specify the same base version, only one of the requests can succeed.
As a result, two separate update requests that happen at the same time will not
unintentionally overwrite each other.

Index

integer <uint64>

optional

Example:

373531

🟠404secret not found

🔴500server error

🔴503node is not part of a swarm

Request

Responses