Skip to content

fix(feishu): preserve encryptKey and verifyToken on config save#377

Open
Gucc111 wants to merge 1 commit into
OpenBMB:mainfrom
Gucc111:fix/feishu-save-preserve-fields
Open

fix(feishu): preserve encryptKey and verifyToken on config save#377
Gucc111 wants to merge 1 commit into
OpenBMB:mainfrom
Gucc111:fix/feishu-save-preserve-fields

Conversation

@Gucc111

@Gucc111 Gucc111 commented Jul 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Fix /feishu/save and /feishu/qr-poll routes to preserve existing config fields (e.g. encryptKey, verifyToken) when saving Feishu settings, instead of replacing the entire config object.
  • Follows the same merge-with-previous pattern already used by writeWeComConfig.

Closes #227

Test plan

  • Manually set encryptKey and verifyToken in pilotdeck.yaml, then save Feishu settings from the UI — verify both fields survive.
  • Repeat via QR scan flow — verify fields survive.
  • Verify that explicitly changed fields (appId, appSecret, connectionMode, domainName) are updated correctly.

Made with Cursor

The /feishu/save and /feishu/qr-poll routes replaced the entire
feishu config object, dropping fields like encryptKey and verifyToken
that the runtime reads for callback decryption and verification.

Spread the previous config before applying new values so that
unmanaged fields survive a save, matching the wecom save pattern.

Closes OpenBMB#227

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

bug(feishu): saving settings drops encryptKey and verifyToken

1 participant