readthedocs instructions outdated #467

New issue

Open

opened 2024-08-16 14:12:41 +02:00 by chrysn · 2 comments

chrysn commented

2024-08-16 14:12:41 +02:00

In early 2024, readthedocs started making a secret mandatory; https://docs.codeberg.org/advanced/using-webhooks/ still describes how to use secret-less webhooks.

I'd update the docs, but I haven't gotten it to run: With the hook and secret readthedocs gave me, I can call it manually as

$ curl https://readthedocs.org/api/v2/webhook/aiocoap/276502/ -X POST -d 'token=hexhexhexthatrtdgaveme'
{"build_triggered":true,"project":"aiocoap","versions":["latest"]}

but I haven't found any set of settings in Forgejo style webhooks that would produce a successful result there. (The token is apparently not sent in a token field, and all test delivieries result in a 403 with {"detail":"Authentication credentials were not provided."})

In early 2024, readthedocs started making a secret mandatory; https://docs.codeberg.org/advanced/using-webhooks/ still describes how to use secret-less webhooks. I'd update the docs, but I haven't gotten it to run: With the hook and secret readthedocs gave me, I can call it manually as ```sh $ curl https://readthedocs.org/api/v2/webhook/aiocoap/276502/ -X POST -d 'token=hexhexhexthatrtdgaveme' {"build_triggered":true,"project":"aiocoap","versions":["latest"]} ``` but I haven't found any set of settings in Forgejo style webhooks that would produce a successful result there. (The token is apparently not sent in a `token` field, and all test delivieries result in a 403 with {"detail":"Authentication credentials were not provided."})

Gusted commented

2024-08-17 03:09:52 +02:00

Owner

Could you try using the Authorization Header field and set it to a value of Token TOKEN_HERE?

Could you try using the `Authorization Header` field and set it to a value of `Token TOKEN_HERE`? ![image](/attachments/ae3a123f-83d0-4252-9ed3-4b4cc2903229)

image.png

17 KiB