oscerd opened a new pull request, #9317: URL: https://github.com/apache/camel-quarkus/pull/9317
## Description [CAMEL-25564](https://issues.apache.org/jira/browse/CAMEL-25564) apache/camel#27716 makes camel-telegram register the webhook with a secret token (the `secret_token` parameter of `setWebhook`), and verify the `X-Telegram-Bot-Api-Secret-Token` header of webhook requests: a request without it gets HTTP 403. The telegram integration test needs three changes: - the webhook route sets `webhook-secret-token`, from the new `webhook-secret-token` property (`TELEGRAM_WEBHOOK_SECRET_TOKEN`, default `fake-secret-token`); - `TelegramTest#testWebhookEndpoint` sends the same value in the header; - the WireMock mapping of `setWebhook` expects the `secret_token` parameter, as it matches the whole query. Without this, the registration at startup would get no match, and the webhook route would fail to start. This stays a draft until apache/camel#27716 is merged and a Camel snapshot with the new option is published. Until then the route cannot start, as `webhook-secret-token` is not a known option of the telegram endpoint. ## Tests Not run locally: this branch builds camel-quarkus 4.0.0-SNAPSHOT, which I did not have built. CI will check it once the Camel snapshot is available. The same change is verified in camel-telegram (apache/camel#27716) and in camel-spring-boot (apache/camel-spring-boot#2029). _Claude Code on behalf of oscerd_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
