-
Notifications
You must be signed in to change notification settings - Fork 53
add new url to interact with deis/builder #351
Comments
Why this format oppose to gathering keys via app name / user name (we have those endpoints already). I get you are wanting to do a "is valid / not valid" kind of API check but can't we do that already if we are pulling down all the keys for the given user? |
@helgi the problem with #336 is that during the ssh auth phase there's no such thing as user/repo, just a public key (I tried to use the routes from 336 in deis/builder#148) |
Ah I was under the impression we had access to that information at the time since we were parsing out the Were you planning on posting the public key as a base64 in the URL? Wouldn't we be better off with a POST or were you going to add the decoded string into the URL for GET? What were you going to use |
yes but can be after the merge of 148? :)
👍 |
base64 in the URL feels odd but it is simple. I may change the |
The PR for this is ready. Have a look and see if it fits your needs |
@helgi testing |
If Go has it, use the urlsafe base64 encoding |
Request:
GET /v2/hooks/public_key/{ssh_public_key}
(where ssh_public_key is the SSH public key as received by the builder in Base64)
Response:
Where:
fingerprint
is the stored value inapi_key
repositories
an array that contains all the apps where the user can rungit push
Return codes:
The text was updated successfully, but these errors were encountered: