Repository navigation
Add authenticated Mythic companion bot event transport - #20
Merged
Merged
Conversation
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
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.
Summary
bot-integration/mythic-api.js, a drop-in Node.js receiver for the Discord bot. It validates bearer tokens, bounds request size, validates payloads, sanitizes mentions, and posts accepted events to a configured Discord channel.Still outstanding
The receiver must be imported into the actual running bot entrypoint and configured on the bot host. This repo does not contain the bot's main
index.js, so I cannot safely wire it into the live bot process here. The/mc-linkaccount-link and team-sync approval queue are not connected by this event transport. Missile notifications remain hooks until real missile flight/impact/defence handlers call them.CI is building both regular and Mythic variants.