Skip to content

fix: move Slack/Gist API contact tokens to encrypted config storage#3326

Open
deacon-mp wants to merge 1 commit into
masterfrom
fix/encrypt-contact-tokens
Open

fix: move Slack/Gist API contact tokens to encrypted config storage#3326
deacon-mp wants to merge 1 commit into
masterfrom
fix/encrypt-contact-tokens

Conversation

@deacon-mp
Copy link
Copy Markdown
Contributor

Slack and Gist contact tokens stored in plaintext config. Moved to encrypted storage. With tests.

Add get_secret() method to BaseWorld that checks environment variables
before falling back to config, allowing tokens to be stored securely.
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@uruwhy
Copy link
Copy Markdown
Contributor

uruwhy commented Apr 13, 2026

name is misleading - there's no encryption here, only providing the option to configure API token config values via environment variables. Requires a larger discussion of if we should extend such behavior to the crypt salt and key values as well, since those are arguably more important to protect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants