docs(runbooks): connector credentials setup (GitHub App, Slack, Discord) - #1738
Merged
Merged
Conversation
… Discord What the 2026-09-17/18 setup taught, written as operational how-to: the ESO one-missing-remoteRef trap and the pod-startTime cutover rule; the GitHub App permission set, webhook-off, repo-scoped install, three SM names and the #1716 chart shape; the Slack manifest-API path with a 12-hour App Configuration Token, the five SM names behind slack.oauth.enabled, why the events request_url waits for the signing secret to be deployed, and the post-deploy socket-mode switch; the Discord verify_key read via GET /applications/@me and its one SM name. No secret values, no project or cluster identifiers. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runbook for what the 2026-09-17/18 connector setup taught, per Sam's pod ask (69418). Docs only: one new file,
docs/runbooks/connector-credentials-setup.md, read against maincda51208.Contents:
api-keysExternalSecret (create SM values → merge mapping → deploy), and the cutover is the new pod'sstartTime, not the workflow tick; checks by presence + length only.api-keys.yamlmaps, the fix(helm): map GitHub App credentials #1716 chart shape and hold rule, out-of-band JWT → installation-token verification, post-deploy acceptance./commonly); the five SM names behindslack.oauth.enabledand thek1:<base64>ring format; chore(helm): enable Slack OAuth secrets on dev #1725 shape; why the eventsrequest_urlmust wait for the signing secret to be deployed (/eventssits behind thesignedmiddleware, so theurl_verificationchallenge 401s before it); socket mode off after the deploy.verify_keyread viaGET /applications/@mewith the bot token from inside the pod, one SM name, fix(helm): wire Discord webhook public key #1685 shape; pointers intodocs/discord/DISCORD_APP_SETUP.mdanddocs/discord/DISCORD_INTEGRATION_ARCHITECTURE.md.No secret values, no project or cluster identifiers, no hostname beyond
api.commonly.me(grep-checked). Pointers intodocs/slack/README.md(legacy ingest path) and the Discord docs where they already say it.Gate: Vera. Merge: Sam.
🤖 Generated with Claude Code