Expose admin commands as REST endpoints #231
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#232 Provide a web interface to administrate Garage}
Deuxfleurs/garage
Reference: Deuxfleurs/garage#231
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
garage layout show
if staged layout is the same as the current #295garage layout show
if staged layout is the same as the current #295In #295 the need was expressed for a machine-readable interface to cluster management commands (
garage status
,garage layout
). We will start by adding these commands to the REST API accessible through the admin endpoint. Ultimately, we would like all of the commands currently available on the Garage CLI to be available from the REST API.Concerning authentification, we will first start by securing the admin API endpoint with simple bearer tokens, e.g. by using the cluster shared secret (
rpc_secret
) as a token for admin APIs. We will consider using a separate bearer token for metrics scraping on/metrics
as we don't want to have to put our cluster administration token in the Prometheus configuration.