OpenAPI spec #671
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#671
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?
Hi folks, would like to contribute some updates to the openapi spec so I can update https://git.deuxfleurs.fr/garage-sdk/garage-admin-sdk-generator and in turn my fork of the terraform provider. Before I dive into src/api/admin/{api_server,router}.rs and figure out if I can automate the generation, wanted to ask if there were already plans for this or if creating a new file and manually updating the docs would be most helpful. Let me know, and I'll get started!
+1. I was just looking for a /v1 openapi spec. Will be watching...
Hi all, I was quite busy during Garage 0.9 release and did not have time to update the OpenAPI spec and the SDKs. I will work on it this morning in #672, hope that progress on this issue will be quick!
Can you try one of the following libraries and report potential bugs?
redacted as outdated.
For Python and Javascript, do not forget to change the endpoint from
/v0
to/v1
.You can find the upgraded examples here: https://git.deuxfleurs.fr/garage-sdk/garage-admin-sdk-generator/src/branch/v0.9.x
You can browse the new API spec here: https://garagehq.deuxfleurs.fr/api/garage-admin-v1.html
If you have some questions about the new API iteration, we can discuss them here or on #672 directly.
This SDK is working fine so far after some moderate testing. I will add a comment if any problems appear later.
The testing continue here:
I think I will write examples that cover the full API before merging this new version to be sure that I will not break other people code: these example serve as unit tests.
In the meantime, you can use the commits above: the errors you report will help me shape my tests.
Ran another set of tests and everything looks good to me, thanks again for the quick turnaround!
There is a problem in the golang SDK (at least) regarding updating keys.
It looks like URL parameters are not being created correctly so the update key post is being interpreted as a new key request. I will debug this soon. Just wanted to mention it.
Delete key also doesn't work. It appears to be for the same reason.
Note that key updating and deleting appear to be the only API requests that include an id in the URL parameters
in: path
in the openapi specification.Manually editing the generated go file for UpdateKeyExecute like this:
makes it work. Guessing that changing the openapi file so the parameter name is
id
and placingin: query
will fix these.I am confident it is fixed in the re-generated SDK above, as it was also reported by unrob.
But to be sure, I will write extensive tests for the golang SDK this morning then merge.