oscerd opened a new pull request, #26546:
URL: https://github.com/apache/camel/pull/26546
## Motivation
The "Configuring in Spring XML" sample on the camel-slack component page
used values with the exact shape of live Slack credentials — an incoming
webhook URL with a plausible `T`-prefixed team id, `B`-prefixed bot id and
24-character secret, and an `xoxb-` bot token. The sample dates back to
CAMEL-9541 (2016).
Nothing consumes those values — they are documentation only — but a reader
cannot tell them apart from real credentials at a glance, and secret scanners
flag the page. Docs should not ship strings that look like working secrets.
## Modifications
Replaced the two values with unmistakable placeholders:
```xml
<bean id="slack" class="org.apache.camel.component.slack.SlackComponent">
<property name="webhookUrl"
value="https://hooks.slack.com/services/YOUR_TEAM_ID/YOUR_BOT_ID/YOUR_WEBHOOK_SECRET"/>
<property name="token" value="xoxb-YOUR_SLACK_APP_TOKEN"/>
</bean>
```
This follows the `<YOUR_TOKEN>` convention already used further down the
same page.
The mirrored copy under
`catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/slack-component.adoc`
gets the identical edit, so the two files stay byte-identical and CI's
uncommitted-changes check stays green.
Grepped the rest of the tree for the old values — no other occurrences.
## Result
Documentation-only change: no code, no tests, no behavior change, no
upgrade-guide entry.
Jira: https://issues.apache.org/jira/browse/CAMEL-24791
---
_Claude Code on behalf of @oscerd_
--
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]
