Repository navigation
docs(integration): document masked secrets in integration responses - #1066
Merged
ysyneu merged 1 commit intoOct 16, 2026
Merged
Conversation
Integration list, detail and update responses return each saved secret in settings as ******. Updates keep a stored secret only while its destination is unchanged. The DingTalk event subscription aes_key and token are shown once when generated and can be generated again from the edit page.
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.
What
Integration API responses no longer carry secret values:
/integration/list,/integration/infoand/integration/updatereturn each saved secret insettings(passwords, app secrets, tokens, encryption keys, webhook endpoints, HTTP pull URL and body, headers, custom bodies) as******; unset values stay empty.integration_keyis unchanged./integration/update: keeping a stored secret while changing where it is sent (endpoint, url, database host/port, IM API base URL) is rejected, and******on a field with no stored value is rejected.Updated in both the per-module and combined specs (
on-call.openapi.*,openapi.*) and the API catalog.Release
Merge when the matching integration service and console changes are live.