admin API refactoring (step 1) #939
No reviewers
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 project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#939
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "refactor-admin"
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?
The new API syntax is somewhat inspired by XRPC: we are no longer trying to be RESTful or to guess API endpoints by HTTP verb or query parameters, the name of the API endpoint is directly in the path (ex:
/v2/ListBuckets
).The aim is to add to the HTTP Admin API all necessary verbs to be able to rewrite the CLI code using only these verbs. In a first step, the CLI will proxy these calls within the RPC protocol so as not to disrupt the current way it works. The next step is to make it able to do these calls directly to the HTTP Admin endpoint, using the (an) admin token. Combined with multiple Admin API tokens (also planned for Garage v2.0) this will make the CLI more flexible and powerful.
drafts/admin-api.md
For step 2:
f138630294
to4533b08f85
a67c1262ca
tof81c2333f1
ae755af563
toeeb08e2225
eeb08e2225
to2c95d4816f
e4ab7c60f2
tob2c1d6b045
b2c1d6b045
to7719f6a5b1
50761a51b9
tod15bea9380
WIP: admin API refactoringto WIP: admin API refactoring (step 1)79a81f81cf
to6d4c1ed23a
8515060a08
to1c03941b19
WIP: admin API refactoring (step 1)to admin API refactoring (step 1)