2017-03-30 19:35:50 +00:00
|
|
|
package api
|
|
|
|
|
|
|
|
// keyringRequest is used for performing Keyring operations
|
|
|
|
type keyringRequest struct {
|
|
|
|
Key string
|
|
|
|
}
|
|
|
|
|
|
|
|
// KeyringResponse is returned when listing the gossip encryption keys
|
|
|
|
type KeyringResponse struct {
|
|
|
|
// Whether this response is for a WAN ring
|
|
|
|
WAN bool
|
|
|
|
|
|
|
|
// The datacenter name this request corresponds to
|
|
|
|
Datacenter string
|
|
|
|
|
2017-09-07 19:17:39 +00:00
|
|
|
// Segment has the network segment this request corresponds to.
|
|
|
|
Segment string
|
|
|
|
|
2019-01-22 20:08:50 +00:00
|
|
|
// Messages has information or errors from serf
|
|
|
|
Messages map[string]string `json:",omitempty"`
|
|
|
|
|
2017-03-30 19:35:50 +00:00
|
|
|
// A map of the encryption keys to the number of nodes they're installed on
|
|
|
|
Keys map[string]int
|
|
|
|
|
add primary keys to list keyring (#8522)
During gossip encryption key rotation it would be nice to be able to see if all nodes are using the same key. This PR adds another field to the json response from `GET v1/operator/keyring` which lists the primary keys in use per dc. That way an operator can tell when a key was successfully setup as primary key.
Based on https://github.com/hashicorp/serf/pull/611 to add primary key to list keyring output:
```json
[
{
"WAN": true,
"Datacenter": "dc2",
"Segment": "",
"Keys": {
"0OuM4oC3Os18OblWiBbZUaHA7Hk+tNs/6nhNYtaNduM=": 6,
"SINm887hKTzmMWeBNKTJReaTLX3mBEJKriDyt88Ad+g=": 6
},
"PrimaryKeys": {
"SINm887hKTzmMWeBNKTJReaTLX3mBEJKriDyt88Ad+g=": 6
},
"NumNodes": 6
},
{
"WAN": false,
"Datacenter": "dc2",
"Segment": "",
"Keys": {
"0OuM4oC3Os18OblWiBbZUaHA7Hk+tNs/6nhNYtaNduM=": 8,
"SINm887hKTzmMWeBNKTJReaTLX3mBEJKriDyt88Ad+g=": 8
},
"PrimaryKeys": {
"SINm887hKTzmMWeBNKTJReaTLX3mBEJKriDyt88Ad+g=": 8
},
"NumNodes": 8
},
{
"WAN": false,
"Datacenter": "dc1",
"Segment": "",
"Keys": {
"0OuM4oC3Os18OblWiBbZUaHA7Hk+tNs/6nhNYtaNduM=": 3,
"SINm887hKTzmMWeBNKTJReaTLX3mBEJKriDyt88Ad+g=": 8
},
"PrimaryKeys": {
"SINm887hKTzmMWeBNKTJReaTLX3mBEJKriDyt88Ad+g=": 8
},
"NumNodes": 8
}
]
```
I intentionally did not change the CLI output because I didn't find a good way of displaying this information. There are a couple of options that we could implement later:
* add a flag to show the primary keys
* add a flag to show json output
Fixes #3393.
2020-08-18 07:50:24 +00:00
|
|
|
// A map of the encryption primary keys to the number of nodes they're installed on
|
|
|
|
PrimaryKeys map[string]int
|
|
|
|
|
2017-03-30 19:35:50 +00:00
|
|
|
// The total number of nodes in this ring
|
|
|
|
NumNodes int
|
|
|
|
}
|
|
|
|
|
|
|
|
// KeyringInstall is used to install a new gossip encryption key into the cluster
|
|
|
|
func (op *Operator) KeyringInstall(key string, q *WriteOptions) error {
|
|
|
|
r := op.c.newRequest("POST", "/v1/operator/keyring")
|
|
|
|
r.setWriteOptions(q)
|
|
|
|
r.obj = keyringRequest{
|
|
|
|
Key: key,
|
|
|
|
}
|
2021-10-28 16:24:23 +00:00
|
|
|
_, resp, err := op.c.doRequest(r)
|
2017-03-30 19:35:50 +00:00
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
2021-10-28 16:24:23 +00:00
|
|
|
defer closeResponseBody(resp)
|
|
|
|
if err := requireOK(resp); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
2017-03-30 19:35:50 +00:00
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// KeyringList is used to list the gossip keys installed in the cluster
|
|
|
|
func (op *Operator) KeyringList(q *QueryOptions) ([]*KeyringResponse, error) {
|
|
|
|
r := op.c.newRequest("GET", "/v1/operator/keyring")
|
|
|
|
r.setQueryOptions(q)
|
2021-10-28 16:24:23 +00:00
|
|
|
_, resp, err := op.c.doRequest(r)
|
2017-03-30 19:35:50 +00:00
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
2021-06-14 22:49:32 +00:00
|
|
|
defer closeResponseBody(resp)
|
2021-10-28 16:24:23 +00:00
|
|
|
if err := requireOK(resp); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
2017-03-30 19:35:50 +00:00
|
|
|
|
|
|
|
var out []*KeyringResponse
|
|
|
|
if err := decodeBody(resp, &out); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return out, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// KeyringRemove is used to remove a gossip encryption key from the cluster
|
|
|
|
func (op *Operator) KeyringRemove(key string, q *WriteOptions) error {
|
|
|
|
r := op.c.newRequest("DELETE", "/v1/operator/keyring")
|
|
|
|
r.setWriteOptions(q)
|
|
|
|
r.obj = keyringRequest{
|
|
|
|
Key: key,
|
|
|
|
}
|
2021-10-28 16:24:23 +00:00
|
|
|
_, resp, err := op.c.doRequest(r)
|
2017-03-30 19:35:50 +00:00
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
2021-10-28 16:24:23 +00:00
|
|
|
defer closeResponseBody(resp)
|
|
|
|
if err := requireOK(resp); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
2017-03-30 19:35:50 +00:00
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// KeyringUse is used to change the active gossip encryption key
|
|
|
|
func (op *Operator) KeyringUse(key string, q *WriteOptions) error {
|
|
|
|
r := op.c.newRequest("PUT", "/v1/operator/keyring")
|
|
|
|
r.setWriteOptions(q)
|
|
|
|
r.obj = keyringRequest{
|
|
|
|
Key: key,
|
|
|
|
}
|
2021-10-28 16:24:23 +00:00
|
|
|
_, resp, err := op.c.doRequest(r)
|
2017-03-30 19:35:50 +00:00
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
2021-10-28 16:24:23 +00:00
|
|
|
defer closeResponseBody(resp)
|
|
|
|
if err := requireOK(resp); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
2017-03-30 19:35:50 +00:00
|
|
|
return nil
|
|
|
|
}
|