Re: [atlas] Updating probe ssh pub keys via API PUT/PATCH requests
Hi RIPE Atlas, Was reading through the documentation yesterday... Is there a specific reason why it is NOT possible to update probe (ssh) pub keys via authenticated API PUT/PATCH requests? https://beta-docs.atlas.ripe.net/apis/metadata-reference/ -- Best regards, Chriztoffer Hansen
On 2021-02-09 18:22, Chriztoffer Hansen wrote:
Hi RIPE Atlas,
Was reading through the documentation yesterday... Is there a specific reason why it is NOT possible to update probe (ssh) pub keys via authenticated API PUT/PATCH requests?
https://beta-docs.atlas.ripe.net/apis/metadata-reference/
-- Best regards, Chriztoffer Hansen
Hello, The main reason is that this is supposed to happen rarely, and when it does it's usually not in an automated fashion. While adding such a feature is surely possible it's unlikely to be a widely used feature. The UI offers this feature and it's likely to be scriptable, so it is in theory possible to make it work. I'll not claim it's as easy as a PATCH request though. I hope this helps / explains. Cheers, Robert
Thank you for birthday 9 year probe credits :) Dear colin johnston, It's your probe's birthday today !! To celebrate that fact, we are giving you 8113213 credits to use for scheduling your own measurements. In the last 9 years your probe was connected for 90% of the time. Happy measuring and thank you on behalf of everyone at the RIPE NCC and the other RIPE Atlas users. The RIPE Atlas Team Col BT techies :)
On Wed, 10 Feb 2021 at 10:55, Robert wrote:
The main reason is that this is supposed to happen rarely, and when it does it's usually not in an automated fashion. While adding such a feature is surely possible it's unlikely to be a widely used feature.
And this applies for e.g. updating a probe description as well? Asking, since the docs mentions the PUT / PATCH requests with GET examples. Tried the below with both PUT and PATCH. Not getting anywhere. :-( curl \ --request ${method} \ --header "Authorization: Key ${api_key}" \ --header "content-type: application/json" \ --header "Accept: application/json" \ --data '{"description": "probe ${probe_id}"}' \ "https://atlas.ripe.net/api/v2/probes/${probe_id}/" Is it treated as a GET request server-side, regardless if I specify the method to either PUT / PATCH method client-side?
The UI offers this feature and it's likely to be scriptable, so it is in theory possible to make it work. I'll not claim it's as easy as a PATCH request though.
-- Chriztoffer
participants (3)
-
Chriztoffer Hansen -
Colin Johnston -
Robert Kisteleki