dependabot[bot]
7d4650a91f
Bumps [com.puppycrawl.tools:checkstyle](https://github.com/checkstyle/checkstyle) from 10.12.6 to 14.3.0. - [Release notes](https://github.com/checkstyle/checkstyle/releases) - [Commits](https://github.com/checkstyle/checkstyle/compare/checkstyle-10.12.6...checkstyle-14.3.0) --- updated-dependencies: - dependency-name: com.puppycrawl.tools:checkstyle dependency-version: 14.3.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
QBit Slack
Slack for a QQQ system. Users connect their own Slack accounts, and organization admins install the
app for their own workspace. The qbit registers a core messaging provider (slack) and a delivery
destination, so any process, scheduled job, report or export can send to a Slack DM or channel through
core alone. Every message is authorized as its owning user at send time, so the qbit is safe for
deployments with many tenants. Delivery uses a durable outbox with Slack rate-limit handling, and
classified PHI and PII never reach Slack.
Design: docs/DESIGN.md.
Requirements
- Java 21
- QQQ 4.1 (currently built against 4.1.0-RC.6)
- A Slack app created from docs/slack-app-manifest.yaml
Install
new SlackQBitProducer()
.withQBitConfig(new SlackQBitConfig()
.withBackendName("rdbms")
.withSchedulerName("scheduler"))
.produce(qInstance);
Tables, permissions and configuration
See docs/DESIGN.md, sections 3 to 14. The tables are prefixed slack_ and the
permissions slack.. Secrets are environment-variable names only: SLACK_CLIENT_ID,
SLACK_CLIENT_SECRET, SLACK_SIGNING_SECRET and SLACK_TOKEN_KEY.
Adopting in another app
Send with core SendMessageAction and the provider name slack, or deliver output to the slack
destination. Don't import this qbit's internal packages; com.kingsrook.qbits.slack.api is the only
public surface.
Build
./mvnw verify