[atlas] Updating probe ssh pub keys via API PUT/PATCH requests

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20210215145248002135.png
Type: image/png
Size: 197603 bytes
Desc: not available
URL: </ripe/mail/archives/ripe-atlas/attachments/20210215/3f427151/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20210215145241002134.png
Type: image/png
Size: 191245 bytes
Desc: not available
URL: </ripe/mail/archives/ripe-atlas/attachments/20210215/3f427151/attachment-0001.png>