This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Updating probe ssh pub keys via API PUT/PATCH requests
- Previous message (by thread): [atlas] Updating probe ssh pub keys via API PUT/PATCH requests
- Next message (by thread): [atlas] Thank you :)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Wed Feb 10 10:55:10 CET 2021
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
- Previous message (by thread): [atlas] Updating probe ssh pub keys via API PUT/PATCH requests
- Next message (by thread): [atlas] Thank you :)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]